Spring Microservices in Action: Architecture Pattern

[Mohammed Sardar.]

Hi John,

  Warm welcome. As One  who uses Java technology very curious to know about Spring Micro Services in Action.   What specific architectural pattern that we discuss in this book while learning micro services ? Do we have nay hands on practicals in the book? As Architectural concepts discuss more theory, expecting this book would create more interested to think on micro services.

Thanks

[John Carnell]

Hi Mohammed,

Thank your for the question.  I personally tried to keep the book very engineering focused.  Chapter 2 of the books introduces the basic concepts of microservices and how to think about microservices at a basic level.  I then tried to cover topics: like service discovery, service routing, client resiliency, event based services and log aggregation.  What I did not cover is a lot of more of the conceptual architectural topics like data replication, transaction and state management and service orchestration.  I think those are important topics, but fell outside the immediate task of getting developers jump started with Spring, Spring Cloud and Spring Microservices.

If you are looking for a patterns based book, I highly recommend you take a look at Chris Richardson's MEAP from Manning, Microservices Patters in Action.  He covers more of the conceptual topics, but does not get into many of the implementation examples.

   Thanks,
      John

[Paul Anilprem]

John Carnell wrote: What I did not cover is a lot of more of the conceptual architectural topics like data replication, transaction and state management and service orchestration.  I think those are important topics, but fell outside the immediate task of getting developers jump started with Spring, Spring Cloud and Spring Microservices.

May be not data replication, but any non-trivial application would require transaction and state management from the get go. Getting a handle on these two things requires experience and for this reason, it is difficult for tech leads/architects to move away from time tested architectures.
It would be great if you could cover these topics as supplementary content through blogs. Just a thought

[John Carnell]

Hi Paul,

No disagreements there on transaction management.  That is the next step after you have learned the basics of the technologies.  Frankly, one of the challenges I have seen with people learning the microservices approach is that while the act of writing a service is easy, building a full-blown application using truly distributed services is difficult.  Its kinds a like I used to tell people I worked with when Ruby on Rails came out.  Yes, you can build a simple blog in 10 minutes, but real applications require real work.  Thanks for the feedback for blog material.  I just recently relaunched my blog (thoughtmechanix.com) and have been starting a list of material to write about :-).

    Thanks,
       John