ah so you have a template of a microservice? In one of my previous jobs we had the same thing. We had a Spring Boot application set up with all the company defaults together with similar things that you describe. It proved as a really good start when someone was developing a microservice
@marcingrzejszczak Yup. Well the way I have it is, the framework comes into 2 sections, one is the template which is a normal spring layering (Persistence DOs and Repos, Services, and Clients like API that has DTOs, Adaptors and Validators) and the other section is called the starter which is a dependency to the template that has all the nice cool hooks for config service, logging, swagger, resource server, hystrix and etc
and via a CLI, our developers can create a sample microservice (using the template) and start putting in their code
and not have everyone coding in different styles
we set the tone on how the style and technique should be, which is to follow Spring best practices and also any new feature we introduce to our base starter, we send out an email and that feature is availabe for use by everyone
There are primary services in play here such as Auth Service, Config Service, Dashboard Service in which they have to be up in order for other services to come up successfully...
those services are maintained by myself and is also levaraging the template :-)