Seun Kola

Firebase is a great way to work on an MVP very quickly with the ability to work on all your backend functionalities using the #firebase function to connect to features like the Realtime database, Firestore to Firebase notifications and Firebase ML Kit. If you want to work on a new product and get an MVP out immediately or soon, use firebase has your cloud service of choice or AWS if you don't mind cost

Have been working on a side project that focuses on sharing economy, allowing users to pickup and deliver groceries for others. Have already started working on the frontend for the web dashboard using React and plan to use React Native for the mobile app. But am in a dilemma, whether to build the backend myself for the MVP or use firebase for the backend. I need advise, has anyone use Firebase for such project and what are the pros and cons, what issues will i faced.

Note: My proposed stack for the backend is a Prisma database, GraphQL , Apollo and ExpressJS

Thanks in advance to everyone.

Over the debate between Amazon RDS and Amazon DynamoDB i will go for Amazon DynamoDB because i tried using Amazon RDS for handling our database for our mobile app VirtualRobe but on each query request the cost was just getting ridiculously high and our monthly AWS bill increased. Therefore we decided to try out non-relational database Amazon DynamoDB, it was quite cheaper but lead to us handling lots of database relationship and functionality such has linking a user table to clothes he or she wore last by doing all this load in the backend when it could have been a child table to the user table on Amazon DynamoDB In all when it comes to cost, i go for Amazon DynamoDB but when it comes to the best database to use with more query flexibilities for apps that requires complex queries i go for Amazon RDS.

Using GraphQL for queries and mutation on React app and Prisma database is so cool, easy and fast to learn. i often use Apollo client to integrate both ends. Most times working has a frontend developer and trying to build a MVP product quickly requires tools that require less setup on both production and development in order to test functionalities, and using GraphQL for queries surpasses Rest queries for me because of the flexibility in requesting the data you actually need and not requesting the whole dataset everytime.

But in all, Rest is still the king since most public api support its CRUD processes more than GraphQL but lot of top companies are using it and am definitely using it for various project including my recent pet project(Delivery buddy - A platform that allows pair-to-pair delivery service).