jm + systems + coding   3

The Death of Microservice Madness in 2018
Quite a good set of potential gotchas, which I've run into myself, including:

'Real world systems often have poorly defined boundaries'
'The complexities of state are often ignored'
'The complexitities of communication are often ignored'
'Versioning can be hard'
'Microservices can be monoliths in disguise'
architecture  devops  microservices  services  soa  coding  monoliths  state  systems 
9 weeks ago by jm
Notes on Distributed Systems for Young Bloods
'Below is a list of some lessons I’ve learned as a distributed systems engineer that are worth being told to a new engineer. Some are subtle, and some are surprising, but none are controversial. This list is for the new distributed systems engineer to guide their thinking about the field they are taking on. It’s not comprehensive, but it’s a good beginning.' This is a pretty nice list, a little over-stated, but that's the format. I particularly like the following: 'Exploit data-locality'; 'Learn to estimate your capacity'; 'Metrics are the only way to get your job done'; 'Use percentiles, not averages'; 'Extract services'.
systems  distributed  distcomp  cap  metrics  coding  guidelines  architecture  backpressure  design  twitter 
january 2013 by jm

Copy this bookmark: