• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
Sheriffs:
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
Bartenders:
  • Mike London

springboot project structure for microservices development

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If spring-boot to be used to develop a RESTful microservices project, which has 50+ services. I've gone through other posts, couldn't get final project structure on the same. Please suggest the project structure suitable for development and deployment. I am planning to use maven to build the project and development IDE is Spring Tool Suite.

1. core,api,controller etc... as separate maven multi module. Challenge in this approach is, I can not build separate jar file (for each microservice) to deploy in separate containers
2. Create different project for each microservice(with api,core, controller etc.. in the same project for that microservice). Challenge in this approach is, I need to have 50+ projects for 50+ microservices. This number may be even bigger with utility services.

Please suggest on the above and thanks in advance.
 
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The core purpose of microservices is the ability to develop each service independently and making them work together. Most of the Microservices projects are developed independently and have a common protocol of communications using Object Mapping. We cannot write all our 50 services into one project whereas we have to develop each service as a separate project module.
We can build each service in sequence and consider writing the dependency in pom.xml to build jars required for each service.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic