For me the bottom line of this video is: Microservices come with a huge amount of challenges, that you do not have with a monolith. Chris covers a lot of topics, each of which deserve a number of dedicated videos.
Category Archives: Architecture
Gregor Hohpe: Enterprise Architecture = Architecting the Enterprise?
Interesting high-level summary on Enterprise Architecture
Sam Newman & Martin Fowler: When To Use Microservices (And When Not To!)
Sam Newman and Martin Fowler in a conversation-style video that looks at Microservices in a non-bullshit way. Must watch!
Simon Brown: Five Things Every Developer Should Know about Software Architecture
A typical (in the best possible sense) video from Simon Brown. Best part for me was modelling and that a common structure is more important than the notation itself.
Dave Farley: The Problem With Microservices
The definitive video on Microservices, as far as I’m concerned. No marketing bullshit, no misguided “stateless-hello world-crap”, but a concise and applicable set of criteria. It is also worth noting, that overall/in general Dave prefers a service-oriented monolithic architecture. I can’t express how great this video is to describe the real core of the idea of Microservices. Please take the time to watch!
Kevlin Henney: Software Is Details
Brilliant video with lots of references to good stuff for reading.
Saad Ali: Kubernetes Design Principles – Understand the Why
Interesting stuff
Clean Code – Uncle Bob / Lesson 1
For the fans of Uncle Bob (aka Robert C. Martin) here is another interesting video.
“You are not done, when it works”
The title is a quote from Robert C. Martin during a conference talk on clean code. For a long time now (I am getting old) I have followed this approach and it has produced remarkable results. For a bit more than four years I had been responsible for a corporate integration platform. I had built and run it following DevOps principles so that everything was fully automated. No manual maintenance work had been necessary at all, log files were archived, deleted after their retention period etc. This had freed up a lot of time. Time which I used to keep my codebase clean.
Particular focus was put onto the structure. And that had been a really tough job. Much tougher than I anticipated, to be quite frank. But I had paid off. Instead of writing a lot of conventional documentation, the well thought-out structure allowed me to find stuff in a completely intuitive way. Because, believe me, six months after you have written something, you do not remember much about it. But if you need a certain kind of functionality and do not only find the corresponding module immediately, but also from a first look make a correct guess how the parameters are meant to be used, that is truly rewarding.
Having experienced this first hand has greatly influenced my work since then. And I am more convinced then ever, that this is not beautifying for the sake of it. But instead it is a mandatory requirement and a prerequisite for business agility.
Jimmy Bogard – Avoiding Microservice Megadisasters
Microservices are not always helpful, what a surprise 😉