Re:How boring should your team be
by P5fRxh5kUvp2th on Saturday October 15, 2022 @10:55PM
(#33220679)
Both approaches are valid for multi-tenancy, with their own pros and cons.
Re:How boring should your team be
by osigurdson on Sunday October 16, 2022 @12:10AM
(#33220960)
Of course, it is hard to say without knowing more about it, but it seems that jiggawatts solution is closer to optimal than the second one. The 50GB database could fit on a USB drive after all and we know empirically that a single SQL server database was able to handle the requests since the old system worked.
Also, the fact that a consulting company was able to turn a part time gig for one person into a $100M+ project at the taxpayer's expense is very frustrating.
Re:How boring should your team be
by P5fRxh5kUvp2th on Monday October 17, 2022 @08:37AM
(#33232660)
typical technical forum, thinking they know the best solution based upon a 1 paragraph description.
Re:How boring should your team be
by osigurdson on Monday October 17, 2022 @03:16PM
(#33238242)
That’s all we have presumably.
This was a multi-tenant centrally hosted application. There were 2000 sites served, each with kiosk PCs and some associated special-purpose hardware.
The actual application code ran in just four virtual machines in two data centres.
No templates, no Terraform, no microservices, etc…
Just vanilla ASP.NET on IIS with SQL Server as the back end.
The efficiency stemmed from having a single consolidated scheme for all tenants with a tenant ID as a prefix to every primary key.
Shared tables (reference data) simply didn’t have a prefix.
The vendor product that replaced this was not multi-tenant in this sense. They deployed a database-per-tenant, and lots of “application servers”. Not one per tenant, but something like one per ten, so two hundred large virtual machines running twenty instances of their app.
Management of the new system took serious automation, disk image building, etc…
The repetition of the reference data bloated the database from 50GB to terabytes!