Explore >> Select a destination
|
You are here 
|
microservices.io | ||
| | | | |
aivarsk.com
|
|
| | | | | Many go to Martin Fowler for microservice architecture, distributed systems, micro frontends, event sourcing, and other fancy ideas about architecture, but a few have noticed the advice to do a monolith first: | |
| | | | |
www.martinfowler.com
|
|
| | | | | The microservice architectural style develops an application as a suite of independently deployable services. | |
| | | | |
vladikk.com
|
|
| | | | | Microservices have taken our industry by storm. Teams around the world have ditched their clumsy monoliths in favor of chasing the dream of loosely coupled, manageable, and independently deployable microservices. Unfortunately, many of them ended up worse off than they were before - in the realm of distributed monoliths. Why? "If I had an hour to solve a problem I'd spend 55 minutes thinking about the problem and 5 minutes thinking about solutions" - Albert Einstein In my opinion, this quote is the key to solving most of the issues we have when designing microservices-based systems. We rush into solutions without ensuring we know what exactly a microservice is. In this post, I'd like to take a stab at answering this question. | |
| | | | |
chipnetics.com
|
|
| | | A quick knowledge nugget in regards to programming language options for project analytics on major industrial projects. | ||
