Building multi-tenant applications
Hello folks. I need some help with tech decision I'm about to make. I'm less experienced, so inputs from the more experienced folks will be invaluable.
I lead a very small team and we're in the very very early stage of the product we're building. It's meant to be a multi-tenant SaaS app, related to healthcare. We expect our customers to have their own users, activity logs and so on (multi-tenant). The tech decision I'm trying to make right now is which database to go with. I already setup postgres with our backend, so we isolate each org's data by postgres schema. But lately I've been thinking about the scalability of the system and after doing a little research, I'm finding that traditional sql databases are not that easy to scale, especially horizontally. I'd have to look at efficiently implementing sharding at that point. I'm tempted to forgo it for now as we literally have no users yet, but I also don't want to do something that would come back and cause the product harm in the future. I don't want to let my team down or incur unnecessary tech debt for everyone. This is the first time I am building such a service, that is, a multi-tenant application like this, so I'd like to know how best to approach this.
How are these types handled in the industry nowadays? I hear nosql dbs, like mongodb, are easier to scale horizontally, but I don't know.
Any insight will be deeply appreciated!
I lead a very small team and we're in the very very early stage of the product we're building. It's meant to be a multi-tenant SaaS app, related to healthcare. We expect our customers to have their own users, activity logs and so on (multi-tenant). The tech decision I'm trying to make right now is which database to go with. I already setup postgres with our backend, so we isolate each org's data by postgres schema. But lately I've been thinking about the scalability of the system and after doing a little research, I'm finding that traditional sql databases are not that easy to scale, especially horizontally. I'd have to look at efficiently implementing sharding at that point. I'm tempted to forgo it for now as we literally have no users yet, but I also don't want to do something that would come back and cause the product harm in the future. I don't want to let my team down or incur unnecessary tech debt for everyone. This is the first time I am building such a service, that is, a multi-tenant application like this, so I'd like to know how best to approach this.
How are these types handled in the industry nowadays? I hear nosql dbs, like mongodb, are easier to scale horizontally, but I don't know.
Any insight will be deeply appreciated!
