jay kumar:
Actually we wanted to store each customers data separate, also if we get new customer than we can design its separate lportal locally and then push it to production, binding instance with that lportal.
On top of what was written above: This is not how sharding
ever worked. You could
never arbitrarily bind different shards to different portals and move them around. A shard always belonged to a single portal. And it never was guaranteed to have the data of one instance exclusively and completely. In order to restore a portal from backup, you always needed all of the shards to be restored together.
Trust David and me: You don't want shards. If you want to strictly separate customers from each other, separating them in individual databases doesn't grant any security, as they're all accessed from the same JVM anyway. If you want to strictly separate them, run different servers.
