Microservices are NOT

  1. Your SOA (service-oriented architecture) cut into services

  2. Anything involving a large framework
    What part of "micro" are folks missing?

  3. Development patterns where you deploy things into containers
    You want containers, do containers. Fine with me. Deployment decisions have nothing to do with microservices. If you're coupling your code to the architecture that tightly, re-read #2.

  4. Things with some cool language
    Once again, if you like cool languages, use them. Sounds fun. It's just has nothing to do with microservices.

  5. Systems with thousands of little tiny pieces of code scattered all over the place making it impossible to reason about anything You're loving the idea to death. You've gone too far the other way. Both the "micro" and "service" part are equally important.

Reference