Post details
The “innovation token” model for selecting technologies is bad, and here’s why.
The “innovation token” model for selecting technologies is bad, and here’s why.
Explore the architectural decisions we made along the journey of building Elastic Cloud Serverless.
GoLang architecture linter (checker) tool. Will check all project import path and compare with arch rules defined in yml file. Useful for hexagonal / onion / ddd / mvc and other architectural patte...
36 comments
Building evolvable software systems is a strategy, not a religion. And revisiting your architectures with an open mind is a must.
<div class="paragraph"> <p>When designing software systems, architects and developers have plenty of architectural options to choose from. Microservice-based systems have become ubiquitous in the last couple of years. However, the idea of monolithic, modular systems has also regained popularity recently. Independent of the architectural style ultimately selected, the individual applications comprising the overall system need their structure to be evolvable and able to follow changes in business requirements.</p> </div> <div class="paragraph"> <p>Traditionally, application frameworks have provided structural guidance by providing abstractions aligned with technical concepts, such as Spring Framework’s stereotype annotations (<code>@Controller</code>, <code>@Service</code>, <code>@Repository</code>, and so on). However, shifting the focus to <a href="https://dannorth.net/2022/02/10/cupid-for-joyful-coding/#domain-based">align code structure with the domain</a> has proven to lead to better structured applications that are ultimately more understandable and maintainable. Until now, the Spring team has given verbal and written guidance on how we recommend structuring your Spring Boot applications. We decided that we can do more than that.</p> </div>
Getting Started with jMolecules and the (Classical) Onion Architecture, with a Spring Boot project (6 mins read).
A guided example of converting a Spring Boot project to the Onion Architecture pattern.
Every time I think/write about hexagonal architecture, I feel like it's an actual silver bullet. It has so many valuable aspects, e.g. focusing on actor intentions, which allow for better test scenarios, decoupling from specific technologies, which leads to increased testability
Matthias Noback (@matthiasnoback)Tue, 18 Jan 2022 09:52 GMT
You're currently viewing page 1 of 1, of 26 posts.