MonetDB is great when you are performing adhoc queries on a large set of data. For example, if you store data in a typical RDBMS such as MySQL or Postgres and want to join large tables for analytics but the query runs unacceptably slow then MonetDB can act as a second database to offload complex queries. Based on my experience, it may not be a production-ready database since there aren't many DBAs familiar with it and due to lack of documentation, maintenance can become a little tricky.
Your upcoming app can be built faster on a fully managed SQL database and can be moved into Azure with a few to no application code changes. Flexible and responsive server less computing and Hyperscale storage can cope with your changing requirements and one of the main benefits is the reduction in costs, which is noticeable.
Maintenance is always an issue, so using a cloud solution saves a lot of trouble.
On premise solutions always suffer from fragmented implementations here and there, where several "dba's" keep track of security and maintenance. With a cloud database it's much easier to keep a central overview.
Security options in SQL database are next level... data masking, hiding sensitive data where always neglected on premise, whereas you'll get this automatically in the cloud.
This is an open source software so there are obvious drawbacks, the biggest of which is a lack of documentation.
MonetDB does not seem to be well known outside of the academic environment so there is less information when you are searching for answers of any type.
I'd like to see more use cases and/or best practices so that commercial companies like ours can optimally use all of its highly performant features.
The code is written in C/C++ and this can be negative if you are a mainly java-shop and need UDF - User Defined Function.
One needs to be aware that some T-SQL features are simply not available.
The programmatic access to server, trace flags, hardware from within Azure SQL Database is taken away (for a good reason).
No SQL Agent so your jobs need to be orchestrated differently.
The maximum concurrent logins maybe an unexpected problem.
Sudden disconnects.
The developers and admin must study the capacity and tier usage limits https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits otherwise some errors or even transaction aborts never seen before can occur.
Only one Latin Collation choice.
There is no way to debug T-SQL ( a big drawback in my point of view).
We give the support a high rating simply because every time we've had issues or questions, representatives were in contact with us quickly. Without fail, our issues/questions were handled in a timely matter. That kind of response is integral when client data integrity and availability is in question. There is also a wealth of documentation for resolving issues on your own.
We have used Five9 in my previous company but on a much smaller scale. It was more expensive, however we were using it for a max of 50 employees, now we need a much bigger platform. We also used Five9 for other things, like phone dialers etc. so it was a little different.
We moved away from Oracle and NoSQL because we had been so reliant on them for the last 25 years, the pricing was too much and we were looking for a way to cut the cord. Snowflake is just too up in the air, feels like it is soon to be just another line item to add to your Azure subscription. Azure was just priced right, easy to migrate to and plenty of resources to hire to support/maintain it. Very easy to learn, too.
If you are familiar with a general database concept and played with open source products before then MonetDB will give you immediate return in terms of productivity since developers can quickly develop and verify their test cases involving back-end database with a large sample data set.
There is a stiff learning curve due to lack of documentation and sparse information available on the internet.
Overall experience has been positive since MonetDB gives you another option when it comes to building out a data warehouse.
