Thank your guys for pitching in. Agree with you guys. I am planning to split these into micro services. Not sure if the application will allow me to do 1 schema per service but i will split them up logically.
A little complexity on top of the volume of services is that it is supposed to be a SaaS application and few customers will like to keep the database on their servers (albeit in the same structure that the services need them). Hence, i will need a way out to have a router somewhere in the services which routes to the correct client database (and then different schemas with in that database depending upon the micro-service). Best, Vaibhav On Thursday, 2 March 2017 04:29:31 UTC+5:30, [email protected] wrote: > > I agree with Phil. This sounds like a logical place to split the > application into micro services. -- You received this message because you are subscribed to the Google Groups "dropwizard-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
