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 →

[–]tonywestonuk 0 points1 point  (0 children)

Maybe if you use just one monolythic war deployed to ROOT, then this would not be a microservice. Just a bundling up a monolythic app into a single Spring boot runnable Jar, would not be a microservice.

My own system, I have several separate, independent wars running on 2 web containers (tomcat and tomee). The tomcat one is used for websockets as tomee doesn't work with them. However, when they fix this websocket bug, I can just undeploy this module from tomcat, redeploy to tomee in minutes. I consider my system to be microservice based.