I, Jetelina, handle multiple databases at once, you know? PostgreSQL, MySQL, and Redis are available so far, and MongoDB will be added to the lineup.

What is it suitable for?
Well, first of all, you do not need to decide what database you will use in your system in the early stage. Because Me provides you with JSON I/F WebAPIs to access these databases, you can set your data order using these WebAPIs to take and store in any databases. Then, this JSON can be used in series if the database is changed in a later stage.
The second, a fron side can progress its programing without waiting a server side working.
The third, a server-side approach, can also progress its development independently, meaning it only needs to take care of designing the data mapping with the front end.
You know, as long as you keep the JSON I/F(WebAPI I/F), both sides can progress their programming by themselves, and bind to each other later. Say again, as far as your database is concerned, you do not worry about mismatching each other.

By the way, which database do you use in your system? How was it decided?
In my experience, the main reason for hiring a database was ‘because I was familiar with it’ or ‘a person who knows it was in our team’. Some people insist we traded off among them, okay, but think and remember it carefully: were there any biases in choosing it among your team?

Database is unbindable on a web system anymore. You can choose one, regardless of whether it’s an on-premises or cloud environment, and each database is continually developing to catch up with the others. In terms of RDBMS, it’s challenging to find significant differences among them. Of course, you may say they are perfectly different; well, well, well, you are correct if you look at them from the inside. However, how is the view from a front system? Every front-end programmer must wait to be prepared for DBI by a so-called database engineer or a server-side engineer. A front sometimes mutters, ‘I just wanna one additional data, why can they not make it quickly?’. I know because a frontman does not have a role in making it, even though the time asks you to rush more and more.

Say again, from the server side, each database system is different, but whichever is okay from the view of the front end. Anyway, I want to push and pop data into something.

Me, Jetelina, indeed, stands on the side of a front man. I mean you start your developing with using PostgreSQL at the first, you access to ‘my’ WebAPIs that are connect to PostgreSQL and proceed data as insert/update/select/delete, this ‘WebAPI’ is simply JSON I/F, therefore you do not need to change your front coading if the database switched from PostgreSQL to MySQL, or Redis, or MongoDB.