Nakata kokuyo wrote:Good day,
I'm new to Microservice, may i know is there any good guidance on this topic and any sample code on this? I try google but most of the page mentioned on concept only..I'm interest on how service can communicate to another service ..
thanks ahead!
Hi Nakata,
I think
Martin Fowler & James Lewis' article on the subject is a good place to go for a more detailed introduction on the topic. My book also goes into this topic in detail - both talking about how to find the boundaries, and how to pick the right sort of integration approach/technology.
William Brogden wrote:I found this quote:
So I don't think "microservices" are much of a break from the best OOP practices.
Hi William,
You're not the first person to make that observation! There are *some* aspects of good OOP that absolutely do make sense in the world of microservices - seeking high cohesion and low coupling for example. But there are a host of complexities inherent in distributed systems (CAP Theory, distributed transactions, latency, service discovery, fault tolerance, load balancing) on which OOP has nothing much to say. In fact if you just see these architectures as just OOP in the large, and don't take into account all these other forces, you could be in for trouble (see also
Martin Fowler's 1st Rule Of Distributed Systems, and his
Microservice-oriented followup from this year). Arguably, the UNIX
philosophy has more baring on how we think about these architectures, but even then leaves out many things that have to be considered.
Many people also call microservices SOA done right. I have no objections with that. They represent a set of practices/principles which come from our improved understanding of building distributed systems/SOA etc, and take advantage of new technology that makes old ideas more practical.
They very much build on what comes before - I did
a talk on this very topic, where I point out that, amongst other things, Parnas was on to something back in the 70s!