4 ms·

> To avoid this problem in the future, I decided to splurge a bit and go for a cloud solution where I wouldn’t have to worry about reliability, performance, sca

by throw14082020 5y ago

> To avoid this problem in the future, I decided to splurge a bit and go for a cloud solution where I wouldn’t have to worry about reliability, performance, scaling or integrity ever again: Google Firestore. > Google Firebase is nice and convenient, but it is quite expensive. We could investigate some other managed database options in future. I've only seen people get annoyed with Firestore over time, and migrating out of it. People do end up worrying. At first, They seem to choose Firestore because it's strongly marketed and seems suitable for a new project. And then data modeling, high prices or scalability becomes a problem.

MichaelRazum 5y ago
What is a good solution compared to firebase ? I mean for a new project, alone something like user handling, registration, email sending, recovering passwords seem to cost some effort. Also be able to react to events, is kind of trivial in firebase. So is it really a bad choise (for the beginning)? Later you can always try to optimize.
- simonbarker87 5y ago
  SupaBase is a good alternative in my opinion but they are not as feature rich yet - but you do get SQL again which is delightful
- janto 5y ago
  Many use Firebase for auth and user management only.
- mellavora 5y ago
  so the problem here is if you have all of those needs, then really soon in the life of the project you are going to need good tooling to handle them. So choosing something which makes it "one-click" to set up but total madness to manage is a really short-term optimization, only worth it for a pure prototype which you will throw away no matter how successful. If you know you need those things to reach success, then it is better to make the up-front investment to get good tools for those. If you still want to go with a cloud provider, AWS Amplify has some interesting tooling. I've build products both against Amplify and Firestore (and Firebase). Yes, Firebase is a few days to a week faster to set up (integrated user management, as you say), but AWS gives more sophisticated control and is built around scripted deployments. You pay for it, of course, and I'm not arguing AWS vs running your own server. I am saying if the choice is AWS or Firebase, that a few days researching the choice would give you knowledge you could use for launching the next 10 prototypes you have in mind.

MichaelRazum 5y ago

What is a good solution compared to firebase ? I mean for a new project, alone something like user handling, registration, email sending, recovering passwords seem to cost some effort. Also be able to react to events, is kind of trivial in firebase. So is it really a bad choise (for the beginning)? Later you can always try to optimize.

simonbarker87 5y ago
SupaBase is a good alternative in my opinion but they are not as feature rich yet - but you do get SQL again which is delightful
janto 5y ago
Many use Firebase for auth and user management only.
mellavora 5y ago
so the problem here is if you have all of those needs, then really soon in the life of the project you are going to need good tooling to handle them. So choosing something which makes it "one-click" to set up but total madness to manage is a really short-term optimization, only worth it for a pure prototype which you will throw away no matter how successful. If you know you need those things to reach success, then it is better to make the up-front investment to get good tools for those. If you still want to go with a cloud provider, AWS Amplify has some interesting tooling. I've build products both against Amplify and Firestore (and Firebase). Yes, Firebase is a few days to a week faster to set up (integrated user management, as you say), but AWS gives more sophisticated control and is built around scripted deployments. You pay for it, of course, and I'm not arguing AWS vs running your own server. I am saying if the choice is AWS or Firebase, that a few days researching the choice would give you knowledge you could use for launching the next 10 prototypes you have in mind.