|
You are here |
www.jamesmichaelhickey.com | ||
| | | | |
www.martinfowler.com
|
|
| | | | | The microservice architectural style develops an application as a suite of independently deployable services. | |
| | | | |
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. | |
| | | | |
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... | |
| | | | |
dhariri.com
|
|
| | | The website of David Hariri, a software developer, designer, and entrepreneur. | ||