Re:The Cracking Monolith: Forces That Call for Microservices
by jsudhams on Wednesday March 22, 2017 @09:46AM
(#13930811)
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
What is micro services https://github.com/msjaiswal/book-notes/blob/master/Building...
* copied from stack overflow
Re:The Cracking Monolith: Forces That Call for Microservices
by treehau5 on Wednesday March 22, 2017 @11:06AM
(#13931499)
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.
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.