We are developing a middleware platform with Spring-boot and REST and we are NOT going to fully microservice architecture, but creating small services based on functionality. Eg: catalog-service-api is for CRUD operations on the catalog and online-services-api for IoT.
1. Should I go for war or jar?
I feel the disadvantage of jar here is, each jar creates a new process (new tomcat) which I don't want to scale at this moment.
As we are developing a cloud-based enterprise product, Do we need jar OR war? Microservices NOT required.
2. If I go with war, is spring boot admin will work as expected?
We are facing deploying spring-boot admin in one server and the client is another server.
@SpringBootApplication
@EnableAutoConfiguration
@EnableAdminServer
public class SpringBootAdminServerApplication extends
SpringBootServletInitializer{
public static void main(String[] args) {
SpringApplication.run(SpringBootAdminServerApplication.class, args);
}
}
Client:
@SpringBootApplication
public class SpringBootAdminClientApplication extends
SpringBootServletInitializer{
public static void main(String[] args) {
SpringApplication.run(SpringBootAdminClientApplication.class, args);
}
}
client application.properties: spring.boot.admin.client.url=http://localhost:8085 spring.boot.admin.client.service-url=http://localhost:8085/spring-boot-admin-server
Admin server is running but client is not available.
Please suggest.