4 ms·

> early adopters have been tech behemoths such as Amazon Not true. Amazon is heavily service-oriented, but quite wary of micro services. You need the right siz

• treehau5 10y ago
  The term micro was always left up to the implementer to define what exactly constitutes micro. There is no uniform standard, and no official definition of microservice, and indeed in my own short time dabbling in them, I have seen it vary from org to org. The ultimate example I have seen, and used myself, is an AWS lambda function, but even then you talk to some "microservice experts" and they don't consider this to be the case.
  • jsudhams 10y ago
    hmmm i always thought there is clear definition. So microservice is : A smaller problem domain. Built and deployed by itself, running in its own. Runs in its own process. Integrates via well-known interfaces. Owns its own data storage. https://youtu.be/wgdBVIX9ifA?t=13m10s https://youtu.be/wgdBVIX9ifA?t=13m10s What is micro services https://github.com/msjaiswal/book-notes/blob/master/Building%20Microservices.markdown https://github.com/msjaiswal/book-notes/blob/master/Building... * copied from stack overflow
    • treehau5 10y ago
      I have a copy of the book you linked in the book-notes! I am excited to start reading it. It's funny you bring up that book because I arrived at my conclusion that how small "micro" is in microservice is based on my previous viewings of talks and articles by Sam Newman and Fowler. I think a lot of microservices are is just applied distributed versions of Enterprise Integration.
• markoa 10y ago
  > microservices are often too slow and require a lot of work to debug Interesting, can you share some example from your experience?