Multi-Tenancy
Last updated
Last updated
The original Spoonity concept was launched as a community program, where merchants would exist within the same system and resources would be shared between them (such as users).
As our products and clients have evolved, it has become increasingly clear that this dynamic does not suit our clients, who would prefer isolation and improved brand-awareness.
An additional cost to this decision is resourcing and scaling, which is affected by the scale and volume of our shared datasets.
This process has already begun to some extent with particular clients. Our goal with the next generation of the Spoonity platform will be to continue this work, and have our vendors be isolated by default.
already provides an excellent backbone for this by allowing us to easily and uniformly manage individual API endpoints for each vendor.
Vendors will have the added protection of improved uptime since incidents with one will not affect another.
Vendor data will also need to be "sharded". Each vendor will be insulated from the others, and have a dedicated space among our fleet of database servers.
Isolating data this way will have the added benefit of improving security and performance.
Separating vendors will also allow us to better proxy and provide access to vendor's individual data through our products.