QA Machine Engineer at a insurance company with 1,001-5,000 employees
Real User
Top 20
Jul 2, 2026
My main use case for YugabyteDB Aeon revolves around problems we face with traditional databases like MSSQL, MySQL, and PostgreSQL because YugabyteDB Aeon gives us the flexibility when we need multiple nodes, facilitating the distributed architecture where if one node is having significant load and crashes, the other nodes can take on that load and work in a distributed way. That is the major part of YugabyteDB Aeon, and it also works in my current project, helping us alleviate the issues we face regarding the single node we are currently using without backup for different nodes to route our traffic. Although I do not have extensive expertise on YugabyteDB Aeon and did not explore it thoroughly, that is the key takeaway from YugabyteDB Aeon. A specific example of how I used YugabyteDB Aeon in my project involves our usage of MSSQL, which is a traditional SQL architecture-based database, and I find that YugabyteDB Aeon's distributed architecture really helps in our production case where we are experiencing a single node that goes down when the traffic is too much and without backup or pre-production environment. If I were using YugabyteDB Aeon, I would implement my database to YugabyteDB Aeon itself, which would solve the issues we encounter.
My main use case for YugabyteDB Aeon is that it is a multi-cloud PostgreSQL database, and I work as a DBA to record data, including unstructured data, and maintain storage. For a specific example of how I use YugabyteDB Aeon in my daily work, I can say this is a database that is really useful. For instance, it enables medical-specific data to be spread globally without compromising local data residency. YugabyteDB Aeon has geo-partitioning capabilities, so we can have our DBA oversee this. By utilizing a single global table instead of a standard regional database, it works on a cluster as well.
Software Engineer at a consultancy with 11-50 employees
Real User
Top 20
Jul 1, 2026
I use YugabyteDB Aeon intermittently rather than regularly. I used it during the first month of my internship, and then two months ago, I built a RAG system using it. I built a RAG system with YugabyteDB Aeon where users ask questions and relevant data from YugabyteDB Aeon tables is retrieved to provide a response. We store user details in a YugabyteDB Aeon table for the implementation of that RAG system. Since I have not used YugabyteDB Aeon in my work, I have used it for my personal use cases. It is good and was easy to operate due to Python packages that make it straightforward to use.
YugabyteDB Aeon is a globally distributed SQL database designed for cloud-native applications, offering transactional consistency, high availability, and scalability. Its geo-distributed architecture ensures data is always accessible, providing seamless enterprise integration.
YugabyteDB Aeon enhances database infrastructure with features that ensure application uptime and performance. It supports multi-region deployments, offering transactional integrity without compromising latency. The...
My main use case for YugabyteDB Aeon revolves around problems we face with traditional databases like MSSQL, MySQL, and PostgreSQL because YugabyteDB Aeon gives us the flexibility when we need multiple nodes, facilitating the distributed architecture where if one node is having significant load and crashes, the other nodes can take on that load and work in a distributed way. That is the major part of YugabyteDB Aeon, and it also works in my current project, helping us alleviate the issues we face regarding the single node we are currently using without backup for different nodes to route our traffic. Although I do not have extensive expertise on YugabyteDB Aeon and did not explore it thoroughly, that is the key takeaway from YugabyteDB Aeon. A specific example of how I used YugabyteDB Aeon in my project involves our usage of MSSQL, which is a traditional SQL architecture-based database, and I find that YugabyteDB Aeon's distributed architecture really helps in our production case where we are experiencing a single node that goes down when the traffic is too much and without backup or pre-production environment. If I were using YugabyteDB Aeon, I would implement my database to YugabyteDB Aeon itself, which would solve the issues we encounter.
My main use case for YugabyteDB Aeon is that it is a multi-cloud PostgreSQL database, and I work as a DBA to record data, including unstructured data, and maintain storage. For a specific example of how I use YugabyteDB Aeon in my daily work, I can say this is a database that is really useful. For instance, it enables medical-specific data to be spread globally without compromising local data residency. YugabyteDB Aeon has geo-partitioning capabilities, so we can have our DBA oversee this. By utilizing a single global table instead of a standard regional database, it works on a cluster as well.
I use YugabyteDB Aeon intermittently rather than regularly. I used it during the first month of my internship, and then two months ago, I built a RAG system using it. I built a RAG system with YugabyteDB Aeon where users ask questions and relevant data from YugabyteDB Aeon tables is retrieved to provide a response. We store user details in a YugabyteDB Aeon table for the implementation of that RAG system. Since I have not used YugabyteDB Aeon in my work, I have used it for my personal use cases. It is good and was easy to operate due to Python packages that make it straightforward to use.