/explore
|
You are here 
|
www.code4it.dev | ||
| | | | |
sookocheff.com
Microservices have become part of the software engineering cultural zeitgeist to the extent that alternative approaches to architecture and development are treated as somehow inferior. Given the challenges that running microservices present, I usually recommend beginning development of new projects and systems as a single deployable unit - the monolith. Sam Newman, in the book "Building Microservices", agrees with this approach. He recommends leveraging microservices only if you can become convinced of the benefits for your system, not as a default for every project. |
|
| | | | | ||
| | | | |
wahibhaq.com
[AI summary] The author shares their interview response detailing a Clean Architecture design for a mobile financial app, emphasizing its benefits for scalability, testability, and agile team structures. |
|
| | | | | ||
| | | | |
herbertograca.com
Documenting Software Architecture When we need to explain to someone else (new developer, product owner, investor, ...) how the application works, we need documentation. But what documentation options do we have that can express the whole application building blocks and how it works?! In this post I'm going to write about: - UML - 4+1... |
|
| | | | | ||
| | | | |
williamdurand.fr
Domain Driven Design also known as DDD is an approach to develop software for complex needs by connecting the implementation to an evolving model. It is a way of thinking and a set of priorities, aimed at accelerating software projects that have to deal with complicated domains. |
|
| | | |||
