Which stack should I use?
Unanswered
Chinese Alligator posted this in #help-forum
Chinese AlligatorOP
Hi, if I want to build an app similar to Nextdoor using Next.js, what database would you recommend? I’ve come across solutions like Firebase or Sanity, but I’m not sure what stack to go with. I come from php world and I’m used to ORMs like Doctrine. I also have a some experience with Sequelize and Mongoose
The goal is to keep things simple, develop quickly, and avoid a tech stack that becomes too expensive to scale. The app will include things like nested categories, KYC, document storage, etc.
What do you use in production for apps like this that are reliable and scalable?
Thanks! 🙏
The goal is to keep things simple, develop quickly, and avoid a tech stack that becomes too expensive to scale. The app will include things like nested categories, KYC, document storage, etc.
What do you use in production for apps like this that are reliable and scalable?
Thanks! 🙏
16 Replies
@Chinese Alligator Hi, if I want to build an app similar to Nextdoor using Next.js, what database would you recommend? I’ve come across solutions like Firebase or Sanity, but I’m not sure what stack to go with. I come from php world and I’m used to ORMs like Doctrine. I also have a some experience with Sequelize and Mongoose
The goal is to keep things simple, develop quickly, and avoid a tech stack that becomes too expensive to scale. The app will include things like nested categories, KYC, document storage, etc.
What do you use in production for apps like this that are reliable and scalable?
Thanks! 🙏
Southern rough shrimp
I would always suggest Postgres, hosted yourself either in a managed instance or simply on a VPS.
But it really depends on your data. If you want unstructured document-like data, pick NoSQL, if you need structured data, use Postgres
Chinese AlligatorOP
Thank you for your suggestion. Since I need geolocation for my jobs, do you think it's a good idea to use Elasticsearch? Or should I use multiple databases for different features? Maybe Supabase with PostgreSQL and PostGIS would be better? But what about scaling? Would Elasticsearch make things simpler?
Southern rough shrimp
I would mix the two
Chinese AlligatorOP
I also think NoSQL might be simpler, especially since the app is likely to evolve quickly. On the other hand, I’m afraid it might limit me later on. I'm not really sure, since I’ve never had the chance to compare both in depth
Southern rough shrimp
The app will include things like nested categoriesSounds like NoSQL to me
I really dont know what your data domain looks like, so I can't comment further
Spend some time actually considering both before you pick, otherwise you'll be spending time migrating from one to the other down the line.
Chinese AlligatorOP
Thank you! What do you mean by mixing both?
Southern rough shrimp
Use both Postgres and Elasticsearch
You'd need to ask someone else, but I'm not familiar with elasticsearch being used as the primary database
But I've also never used it so 🤷♂️
@Chinese Alligator I also think NoSQL might be simpler, especially since the app is likely to evolve quickly. On the other hand, I’m afraid it might limit me later on. I'm not really sure, since I’ve never had the chance to compare both in depth
Blanc de Hotot
If you want a nosql alternative checkout the pongo package. Turns postsql into nosql store
You do not use elasticsearch as a primary database imo
Chinese AlligatorOP
Thank you I'll take a look! Ok I understand, so the best way to use elastic is to sync it with another database ?