Explore >> Select a destination
|
You are here 
|
blog.cleancoder.com | ||
| | | | |
www.milanjovanovic.tech
|
|
| | | | | If you were to glance at the folder structure of your system, could you tell what the system is about? Your architecture should communicate what problems it solves. This approach is called sreaming architecture. | |
| | | | |
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. | |
| | | | |
blog.8thlight.com
|
|
| | | | | ||
| | | | |
blog.jayfields.com
|
|
| | | The default architecture for Ruby on Rails, Model View Controller, can begin to break down as Controllers become bloated and logic begins to... | ||
