Let’s Get Excited About Maintenance

Re:Let’s Get Excited About Maintenance by taude on Monday July 24, 2017 @08:50AM (#14837969)

We're in the same boat as you and our SAAS model involve custom deployment versions for each client. We're looking at trying to keep the databases unique per client, but handling the core requests in a multi-tenant environment, but it's difficult to plan ahead for all the different asks our customers need.

I often wish I worked at one of the SaaS product companies that target small-business.

[ Parent | on HN ]

Re:Let’s Get Excited About Maintenance by icebraining on Monday July 24, 2017 @09:04AM (#14838065)

I've considered that approach, but that means keeping the code fully retrocompatible, and that kinda leads to madness :D

Plus if you have different processes per client, you can provide better security, particularly in terms of leaking customer data to each other. In our case, we just used different Linux and Postgres users for each client, but even just that meant that a few security bugs discovered in the application couldn't be used to read/write data of other customers.

[ Parent | on HN ]