What is your primary use case for Microsoft Azure HorizonDB?

My main use case for Microsoft Azure HorizonDB is that we were experiencing performance issues in Azure PostgreSQL flexible server, so we wanted to eliminate those issues and started using Microsoft Azure HorizonDB. A specific example of how I used Microsoft Azure HorizonDB to address those performance issues is that we were experiencing disk IO errors in Azure PostgreSQL. Microsoft Azure HorizonDB has a separate storage layer, so when we started using it, we did not encounter those disk IO errors. Regarding my main use case and how it has helped with those disk IO issues, we did not perform any special configuration in Microsoft Azure HorizonDB. The underlying architecture itself has a separate storage layer, whereas Azure PostgreSQL shares CPU, memory, and storage layers together. We believe this different architecture may have helped resolve the performance issues. Because our application is very disk IO intensive with heavy read and write operations, this is one of our critical databases.

Microsoft Azure HorizonDB serves as my main use case because it is fundamentally a PostgreSQL database, and our company manages financial data with this type of database. It functions as an OLTP system, and with workflows involving massive data, we manage it using Microsoft Azure HorizonDB. A specific example of how I use Microsoft Azure HorizonDB with our financial data is that it contains multiple datasets and is a huge database. It operates as an OLTP, and when multiple users connect simultaneously, we found that it manages the transaction volume very easily and very smoothly. The application users are not facing any deadlock or locks in this scenario, and it is also used for real-time analytics very smoothly. It has outstanding performance compared to other relational databases, which is why we are using it. Microsoft Azure HorizonDB is better than other relational databases.