Most of your Firebase logic will live in your client(s). If you have multiple clients (web, iOS, Android, etc) you will have to write and maintain the same logic multiple times in different languages. And since the DBs are so barebones you will need a lot of logic to read and write. Pretty much all the business logic you'd have in a server will be in your client(s).
You also have cloud functions which have the worst dev experience I've seen with serverless. Deploying takes forever, sometimes as high as 2-3 mins, and you will need to deploy very often as most of your functions won't run locally [2]. Debugging is done via the Firebase console which is a painfully slow Angular 1 app.
For websites the complete Firebase SDK is 215kB gzipped and you will need most of it [3].
You can define database rules using a JSON-like language for permissions and schema but it will get super messy as your project grows and become unmaintainable.
Unless you are doing a small project or a prototype get as far away as you can from Firebase.
If you do need a serverless DB look into Fauna DB which gives you everything you expect from a serious DB. Or if you're looking for a zero-config backend look at Hasura like I've mentioned earlier.
[1] https://medium.com/joolsoftware/extending-firebase-with-clou...
[2] https://firebase.google.com/docs/functions/local-emulator
Disclaimer: I'm a dev advocate there so I'm obviously biased
Once you learn how it works, Firebase will get you from 0 to 10 really fast but will slow you down as you struggle to go from 10 to 100. By then your app/product will have so much Firebase specific code that you will need to rewrite a significant portion of code to move out of it. Let me know if you want me to expand with specifics on why Firebase is bad.
If you need something easy to start fast I'd say go with Hasura. It will give you one-click GraphQL API over Postgres. Your front end will simply use standard GraphQL so you can change your backend without touching the front end. And Postgres is still Postgres. Even if you decide to completely rewrite your product you could keep using the same database.