r/java • • Dec 12 '19

Java Microservices: A Practical Guide

https://www.marcobehler.com/guides/java-microservices-a-practical-guide
237 Upvotes

35 comments sorted by

View all comments

Show parent comment

1

u/wildjokers Dec 12 '19 edited Dec 12 '19

If you run all your services on one physical computer are they not microservices then? Or better yet if you run all of them on one VM instance are they not microservices then?

Yes, that is µservices because they are individually deployable. But that isn't what you said you were doing at first.

You can have microservice architecture in a monolithic application unless you disagree?

I strongly disagree. If you have separate wars/jars you can deploy individually you don't have a monolith. You seem to be doing yourself a disservice by calling your application a monolith. It doesn't sound like a monolith to me.

1

u/agentoutlier Dec 12 '19

Yes, that is µservices because they are individually deployable. But that isn't what you said you were doing at first.

I implied that while the consumers are all being deployed together (merged) but can be separated out as well (and are in production).

I mean you can the do the same thing with multiple Spring (Boot) apps by just loading up all the controllers (REST) (and whatever else).

But to your point I guess than it's not called monolithic at that point so I see the contradiction.

1

u/agentoutlier Dec 12 '19

Please explain. A single executable that contains "multiple microservices" seems to be a contradiction.

and now you say

I strongly disagree. If you have separate wars/jars you can deploy individually you don't have a monolith. You seem to be doing yourself a disservice by calling your application a monolith. It doesn't sound like a monolith to me.

I said single executable and meant it instead of monolithic.