MySQL would require a separate MySQL db server, which means either two servers (one for MySQL, and one to provide your specific services to your client app) or both running on a single server machine. It is different from Firebase and MySQL (and most other databases) in that it is embedded in the product, although it could be embedded in your server itself. It sounds like a server-client relationship (central database) and while SQLite is probably the simplest, note that its performance is probably the worst of the top 20 or so choices you have. Regardless, you'd certainly only keep high-level records, meta data in Database, and the actual files, most-likely in S3, so that you can keep all options open in terms of what you'll do with them.

Other database services exist, I'd recommend you also explore Dynamo DB. I personally would recommend MySQL (latest version available), as the official tooling for it (MySQL Workbench) is great, stable, and moreover free. As far as which database to chose, you'll have the choice between Postgresql, MySQL, Maria DB, SQL Server. Doing this on your own would either be risky, inefficient, or you might just give up. Such managed services easily allow you to apply new security patches and upgrades, set up backups, replication. Aurora would be my preferred choice given the benefits it offers, storage optimizations it comes with. If you are on AWS, thet have different offerings for database services. Don't spin up your own MySQL installation on your own Linux box. Hi Erin! First of all, you'd probably want to go with a managed service.

Let me know if you still need any suggestion's. Use Node.js programing language as that function asynchronously. Also For MongoDB if you can put a layer of REDIS Cache then that will boost your api performance under large loads.ĥ. There is a stored procedure that generated unique keys instead of auto-increment keys and that will help you sharding or clustering database without sync errors.Ĥ. If you using Postgre SQL then i would suggest you to please check this Use UUIDS always for Auto increments for MYSQL. Never or very rarely use Auto-increments.

( the moment you reach 3 join stop there and try to un-normalized database.ģ. Use Mysql only for storage only and for realtime updates we recommend MongoDB.Ģ. When using MySQL, i would recommend doing the following:ġ.

We build our product which is in the same lines as yours but we have used a combination of Mysql and MongoDB. It feels like you have most experience with SQL/RDBMS technologies, so for the simplest learning curve, and if your application fits it, then I'd personally start by looking at AWS Aurora. RDBMS/SQL stores are great for having as many indexes as you want, other than the slow-down in write speed, whereas databases like Amazon DynamoDB provide blisteringly fast read/write performance, but are very limited on key indexing capabilities. MongoDB, with its document-store type solution is a very different model to key-value-pair stores (like AWS DynamoDB), or column stores (like AWS RedShift) or for more complex data relationships, Entity Graph Stores (like AWS Neptune), to stores designed for tokenisation and text search (ElasticSearch) etc.Īlso critical in all this is how many items you believe you need to index by. however please don't fall into the trap of considering 'NoSQL' as being single category. Your question regards 'Relational or not' is obviously key, and you need to consider both your required data structure, as well as the ACID requirements of your application model, as well as the non-functional requirements in terms of scalability, resilience, whether you want security authorisation at the highest application tier, or right down to 'row' level in the database, etc. Particularly if you are planning to host in either AWS or Azure, then your first point of call should be the PaaS (Platform as a Service) databases supplied by these vendors, as you will find yourself requiring a lot less effort to support them, much easier Disaster Recovery options, and also, depending on how PAYG the database is that you use, potentially also much cheaper costs than having a dedicated database server. The most important question is where are you planning to host? On-premise, or in the cloud.

Ms sql vs mysql differences