...
a Java app built with Spring Boot provides a structured set of Spring services versus the standard Spring framework that offers modules to use as needed: Core, JPA, Security, WebflowMVC etc. It is similar in concept to Grails which came out earlier.
a Containerized app or service runs in a container with it's dependencies locallocalized. The container provides another layer of security and isolation from the runtime platform. It's common to run a single service in 1 container but it's possible to package more than 1 in a container if there was a use case for it. For a Spring Boot app, the ports need to be mapped and exposed through the container to clients to receive REST requests.
...
I have not containerized a Spring Boot app. I have containerized simple Java web services, Node.js microservices, MySQL database, Hyperledger blockchains with CouchDB, Node.js, GO using Docker and Docker Compose. I also completed a lab on running blockchain Microservices in a Kubernetes network ( PODS running Docker containers ). There is nothing that makes Spring Boot fundamentally different in containers than other Java apps. On the other hand, I have no idea how complex the client's Spring Boot apps are or the work needed to containerize them in Docker. The concepts are the same but the work depends on their inventory.
...
At Fidelity we used Spring frameworks but Spring boot did not exist then. At PTP we did create simple Spring boot applications to load data to the ODS. I was able to improve loader performance 300% by removing Spring / Hibernate and creating simplified batch JDBC loaders. That was a better solution for that specific use case.
...
I'm not asking for anything unreasonable, right?
Top questions for this project:
1> do we have a clear definition of priorities for current and future requirements from TSA?
2> are we doing a tactical migration ( quick and cheap ) or a strategic migration ( designed to meet / exceed future TSA requirements )?
Potential Value Opportunities
...