Yes! Finally! People keep making the assumption that going for Services/Microservices is merely technical. It’s almost all about people and organization. Point

Yes! Finally! People keep making the assumption that going for Services/Microservices is merely technical. It’s almost all about people and organization. Point 7 is the most important of the technical considerations: just make your services big enough to make sense as a separate unit and small enough to not be another unchangeable monolith. Yes, it’s not sane to have 300 Lambdas that add one number to another talking to each other over network, so just don’t do it. Microservices the “Netflix way”, with the huge graph of services, gives a bad name to the idea of factoring out modules into independently deployable parts, which always made sense. Kubernetes just helps with deployment, but how coarse or fine you factor is on you.