Building monolith applications that could scale to microservices (only if they need to)
Join us for the developer community event.
The demands of software changed dramatically in the last 20 years. Yet, the dominant architectural styles are still based on patterns from the 70’s. Although new architectural patterns have emerged, the benefits are often brushed aside with the excuse of being ‘too complex’ or ‘not necessary.’
The demands of software changed dramatically in the last 20 years. Yet, the dominant architectural styles are still based on patterns from the 70’s. Although new architectural patterns have emerged, the benefits are often brushed aside with the excuse of being ‘too complex’ or ‘not necessary.’
How can we take advantage of these benefits without getting distracted by the technical details that threaten the simplicity of our solution?
How can we take advantage of these benefits without getting distracted by the technical details that threaten the simplicity of our solution?