The Death of Microservice Madness in 2018


162 bookmarks. First posted by vitriolix january 2018.


"The fundamental challenge of understanding the shape of your data, and how it evolves, cannot be eliminated."
microservices  architecture 
february 2018 by dmartinez
There are cases where great efforts have been made to adopt microservice patterns without understanding the specifics of the problem at hand...
microservices  architecture  devops 
february 2018 by vipom
There are many cases where great efforts have been made to adopt microservice patterns without necessarily understanding how the costs and benefits will apply to the specifics of the problem at hand.

I'm going to describe in detail what microservices are, why the pattern is so appealing, and also some of the key challenges that they present.
software-architecture  share 
january 2018 by pietvanzoen
There is no microservice architecture. Microservices are just another pattern or implementation of components, nothing more, nothing less. Whether they are present in a system or not does not mean that the architecture of the system is solved.

Microservices relate in many ways more to the technical processes around packaging and operations rather than the intrinsic design of the system. Appropriate boundaries for components continues to be one of the most important challenges in engineering systems.

Regardless of the size of your services, whether they are in Docker containers or not, you will always need to think carefully about how to put a system together. There are no right answers, and there are a lot of options.
microservices  Architecture 
january 2018 by janpeuker
Nice article on what to be aware of if you're looking at using microservices: https://t.co/pCRzoGGCiW
– Adrian Mouat (adrianmouat) http://twitter.com/adrianmouat/status/958439329042452483
via:packrati.us  toread 
january 2018 by eeichinger
Lots of potential pitfalls to consider before jumping down the microservices route (and lots of times when it's a great idea too) http://bit.ly/2nrsRiH
Tweeted 
january 2018 by michaelmartin
There are cases where great efforts have been made to adopt microservice patterns without understanding the specifics of the problem at hand...
programming  architecture 
january 2018 by nfultz
Good discussion of benefits
microservices  SOA 
january 2018 by weston
There are cases where great efforts have been made to adopt microservice patterns without understanding the specifics of the problem at hand...
january 2018 by ekepes
There are cases where great efforts have been made to adopt microservice patterns without understanding the specifics of the problem at hand...
programming  microservices 
january 2018 by arobinski
RT : Blogged: The Death of Microservice Madness in 2018
from twitter
january 2018 by jukkan
When done by experts, the results can be wonderful. But imagine an organisation where perhaps things are not running smoothly with a single monolithic system. What possible reason would there be that things would be any better by increasing the number of systems, which increases the operational complexity?
software  development  programming  architecture 
january 2018 by imaginaryfriend
There are many cases where great efforts have been made to adopt microservice patterns without necessarily understanding how the costs and benefits will apply to the specifics of the problem at hand.

I'm going to describe in detail what microservices are, why the pattern is so appealing, and also some of the key challenges that they present.

I'll finish with a set of simple questions might be valuable to ask yourself when you are considering whether microservices are the right pattern for you.
architecture  devops  microservices  programming 
january 2018 by dagh
Microservices became a very popular topic in over the last couple of years1. 'Microservice madness' goes something like this: Netflix are great at devops. Netfix do microservices. Therefore: If I do microservices, I am great at devops.
january 2018 by marshallk
The Death of Microservice Madness in 2018
from twitter
january 2018 by jackysee
These techniques mitigate a large number of the challenges if the services are stateless. But stateless services are quite frankly, easy to deal with. In fact, if you have stateless services, then I'd be inclined to consider skipping microservices altogether and consider using a serverless model.
january 2018 by ptsteadman
Indeed microservices are hard. Don't even think about it unless you have experience. WAIT! That's a Catch-22!
from twitter_favs
january 2018 by windley
RT : The Death of Microservice Madness in 2018
from twitter_favs
january 2018 by dkincaid
When done by experts, the results can be wonderful. But imagine an organisation where perhaps things are not running smoothly with a single monolithic system. What possible reason would there be that things would be any better by increasing the number of systems, which increases the operational complexity?
january 2018 by Chronologos
The Death of Microservice Madness in 2018
from twitter
january 2018 by avesse
The Death of Microservice Madness in 2018
from twitter_favs
january 2018 by rukku
The Death of Microservice Madness in 2018
from twitter_favs
january 2018 by aikoven
The Death of Microservice Madness in 2018
from twitter
january 2018 by brandizzi