4 ms·
> This is a bad idea. Not really. It all depends on what are your needs. > It defeats a major feature of the jvm. You're confusing things. Just because Java
by chipdart 2y ago
> This is a bad idea.
Not really. It all depends on what are your needs.
> It defeats a major feature of the jvm.
You're confusing things. Just because Java addressed the deployability problem for Java applications before containerization was even a word, this does not mean that deploying a JVM per service is a bad idea. Just think about it for a second. Why do you need to deploy and scale services independently? Do you mention the JVM in your response? No.
- liveoneggs 2y agoWe were talking about dev enviroments on desktops, not independently scalable components. I did mention the jvm in my response. You quoted me doing so, in fact.
- chipdart 2y ago> We were talking about dev enviroments on desktops, not independently scalable components. Your dev environment is expected to mimick your production environment, not the other way around.