2.2.a-Networking--Service APIs--Turning a monolith into a microservice

This video discusses what it takes to turn a method call into a network call and many of the issues related to this effort.

[@nosh3019]

This course is really informative

[@KDOERAK]

Again, an excellent overview.

[@mazenezzeddine8319]

Should the call to the method service block the client? Futures and callbacks are handled especially when a microservice call another microservice?

[@JeffreyRichter]

This question is about an implementation detail and not about the big concepts. I'm a huge fan of making non-blocking asynchronous network requests because this allows a service's implementation to be resource efficient and therefore scale better and run more cheaply. But, many services do make blocking, synchronous network requests and if the load on the service is small enough, the resource consumption stays low and this service meets the desired needs.

[@mazenezzeddine8319]

Can increasing throughput in terms of number of concurrent users be identified as a reason to go to microservices? how would microservice architectural style compare to monolith in terms of latency?

[@JeffreyRichter]

No, you can always scale a monolithic service up by running more instances to meet high concurrent user demand. If you can identify different parts of the monolith that have different resource consumption and/or different usages (like some users only look at photos while others frequently upload photos), then you have identified good candidates for splitting into separate microservices.

[@mazenezzeddine8319]

Can it happen that the Method Itself be shipped into the microservice e.g. class job { Method(), arg1, arg2 } using serialization and dynamic class loading, does that fall also in the context of microservices?

[@JeffreyRichter]

Yes, microservices don't mandate any particular way for the code to get onto a machine. But, I wouldn't get too caught up in the "microservices" terminology. It is just a word. The main idea is that it privately owns a set of behaviors and its data store just like a object-oriented class owns a set of behaviors and its private fields.

[@mazenezzeddine8319]

The main idea is that it privately owns a set of behaviors and its data store just like a object-oriented class owns a set of behaviors and its private fields. Thanks great definition: perfectly fits to an actor definition, maybe!