Ask HN: Main things to consider when building an app for business/enterprise?

Post by mooreds » Sun, Jan 08, 2023, 7:38 PM UTC

mooreds wrote: post #60

fullstackchris wrote: post #19

Earlier quoted context omitted.

As an alternative, if you containerize everything in the stack, you can simply spool up another seperate and isolated stack of containers for each given customer. Then it's also trivial if they want it 'on premise' somewhere or 'in the cloud'. No need to try and add complexity at the schema level and make a monolith support multiple tenants. Also, this list is quite literally supabase ( https://supabase.com/ ) - I ca…

You can do this with containers, or, if the price point is right, with VMs for even more isolation. There are levels of multi-tenancy: * logical multi-tenancy, where isolation is enforced in code and the database (every table has a 'tenant id' key) * container level multi-tenancy, where you run separate containers and possibly in different namespaces * virtual machine multi-tenancy, where there are different VMs for…

I ended up expanding this comment on my blog: https://www.mooreds.com/wordpress/archives/3578

Post by rst » Sun, Jan 08, 2023, 11:11 PM UTC

vulcan01 wrote: post #69

spapas82 wrote: post #42

Earlier quoted context omitted.

Yes that's true. But please consider that some orgs prefer self hosting their software. In this case using their database would be preferable.

In that case, only using ANSI SQL will help (i.e. no vendor-specific queries).

Unfortunately, you can't count on the enterprise's pre-existing DB to support all of ANSI SQL well. Oracle in particular deviates from ANSI in a whole bunch of well-known ways (messed-up date types, treating the empty string, '', as the same thing as NULL, etc., etc.), which are almost certain to trip up SQL which hasn't been tested against it.

Re: Ask HN: Main things to consider when building an app for business/enterprise?

Re: Ask HN: Main things to consider when building an app for business/enterprise?