Microservices are all the rage now.
But, many are (finally) realizing that it’s not for everyone. Most of us aren’t at the scale of Netflix, LinkedIn, etc. and therefore don’t have the organizational manpower to offset the overhead of a full-blown microservices architecture.
An alternative to a full-blown microservices architecture that’s been getting a lot of press lately is called “modular monoliths.”
Years ago, I lead the web development of a new platform for selling life insurance online (which provided white-label abilities).
This was one of my biggest professional accomplishments given the many technical and political constraints. But that’s a whole other topic for another day.
This was before I understood domain-driven design. Since then, I’ve wondered: what this might have looked like using a domain-driven approach?
Did you know that the inventor of the concept of “null” has called this his “Billion Dollar Mistake!”
As simple as it seems, once you get into larger projects and codebases you’ll inevitably find some code that goes “off the deep end” in its use of nulls.
One of the classic “code smells” is called Primitive Overuse.
It’s deceptively simple.
Refactoring is just a fancy term that means improving your code without changing how it behaves.
Let’s look at some reasons for why you should learn about when and how to refactor effectively.
The .NET Core CLI comes with tons of pre-built project templates! One of the new templates that will be included with .NET Core 3 will be for building worker services.
Combining .NET Core worker services with Coravel can help you build lightweight background job scheduling applications very quickly. Let’s take a look at how you can do this in just a few minutes!
Ever find yourself scratching your head while wondering what you should name that new class?
Design patterns are necessary (in my opinion) for you to start gaining an advanced understanding and ability to design and refactor software.
These patterns also give developers a common language to speak about certain code structures.
Have you ever heard of guard clauses? Steve Smith discusses them in one of his Weekly Dev Tips here.
Today I want to show you a technique that I’ve been using which is similar to the guard clause pattern but is used in more advanced scenarios. These scenarios include when you have problems due to external dependencies or complex logic that is required in your guard clauses.
I started my career working for an organization that was building a platform for vehicle manufacturers to consolidate and run analytics on their sales.
I started off having to use technologies and frameworks I had no experience with yet (ASP.NET, T-SQL, etc.)
For the first few months, I felt overwhelmed.
I took forever to do simple things like adding a checkbox to a web page that would get stored in the database!
Maybe you’ve been there too!