Daniel, thanks for your response! I appreciate constructive criticism. Could you clarify one point. When you refer to one jar file, do you mean that a microservice can be deployed individually in a jar, to a container, and be deployed and executed without any other software (except perhaps a small container sidecar)? I understand that the server can register, at runtime, individual services that have been appropriately annotated. I do not think of them as being independently deployable or scalable in the context of a cloud-native microservice. I will certainly change .war to .jar in my article. I have no wish to malign Spring Boot, but you need to convince me that Spring Boot services are truly independently deployable and executable.

It is the ability to deploy microservices individually that was my point. For years, using JAX-RS 2, I’ve been dropping jar files into running Tomcat servers and having them load and execute. Today, I use actor model microservices that are loaded and register themselves with message brokers so that they are reachable and responsive to messages — -without requiring a conventional JAX-RS or Spring Boot server.

I would also appreciate it if you could direct me to the appropriate Spring Boot documentation to help me better understand inter-service communication and how Spring Boot dispenses with a conventional Web server. I do not want to propagate any false information through inaccurate assumptions on my part.