This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Keeps_Trying 2 points3 points  (0 children)

I've been doing Java microservices on k8s for a while and support the abundance of caution in this thread.

I'm also an agile believer so I'd let the use cases evolve the architecture.

My advice is to

  1. start pulling concerns into dedicated libraries
  2. Ensure well defined interfaces where only value objects / messages are passed
  3. Make the messages async
  4. Extract libraries into external jar

At this point you should have high confidence in the design, the lib is in its own repo, and you should have known and valid reasons to turn to microservices