The SDLC Story
The SDLC process should offer reassuring guardrails, not roadblocks
The SDLC process should offer reassuring guardrails, not roadblocks
How do we know we have done enough on our move from Monolith to Microservice? It is obvious (to me at least) that we do not need to rewrite the entire legacy system into microservices. There will be pieces that do not fit into a microservice realm. They are larger, need special treatment, or any … Read more
The final part of the SOLID design principles. Today is a quick one, as we just take a look at the Dependency Inversion principle.
Eventually, after chipping away at the edges, we will finally reach the core. The real guts of the monolith. The important bits. Tread Carefully This will be where any missteps have very hard ramifications. When a problem is introduced in the core, it will be very noticeable. Luckily, by now we have quite a bit … Read more
Today is the second part of digging into the SOLID design principles. Today are the hard ones, Open/Closed and Liskov Substitution.
Today we start part 1 of taking a look at the SOLID design principles. Single Responsibility and Interface Segregation are the topics of the day.
Many small and medium-sized companies have adopted a microservice architecture. The adaptability, scalability, and agility that the microservice patterns unlock are very appealing to these companies. These attributes are also appealing to larger companies too. But other attributes also tend to temper some of these benefits. Adaptability Polyglot is the name of the game. Teams … Read more
Last time, I brought up the concept of template services. Today I want to share more details on what we do with this concept. Reference Architecture Sometimes you will hear architects talk about a reference architecture. This is the concept of having an established pattern out in the wild with real examples. An architecture that … Read more
When an organization moves away from a centralized monolith to more decentralized and distributed architectures, such as microservices, the development culture, and therefore, the culture around the system’s architecture also changes. It too must become more distributed and less centralized. Development teams, because they are ideally autonomous in a microservices environment, require more freedom than … Read more
Or, Partial Microservices There has been much discussion lately around how microservices may not actually be the appropriate architecture for many teams and companies, especially those working on legacy applications. The idea behind this is that while microservices may perhaps be ideal in some circumstances, they most definitely have their limitations, and really are not … Read more