YugabyteDB Aeon- Pay As You Go

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.

The best features YugabyteDB Aeon offers are that it is a fully managed YugabyteDB service that allows running a YugabyteDB cluster in a multi-cloud environment.

The multi-cloud capability of YugabyteDB Aeon positively impacts my workflow, as we have different subscriptions where we have to work. YugabyteDB Aeon has positively impacted my organization by being an open-source project that helps work on open mobility as well. The main features that stand out are geo-partitioning and applications in a long capability.

I have no comments on how YugabyteDB Aeon can be improved because I have not worked as much on this database. There is no output on this question from my side. From my side, no improvement is required for YugabyteDB Aeon; all is good right now.

I have been using YugabyteDB Aeon for only a year.

In my experience, YugabyteDB Aeon is not as stable as the customer requires.

YugabyteDB Aeon's scalability is dependent upon the subscription over the public cloud.

The customer support for YugabyteDB Aeon is not very good.

I did use a different solution before YugabyteDB Aeon, but it is different from YugabyteDB Aeon.

I find it acceptable to integrate YugabyteDB Aeon with my existing systems and applications.

YugabyteDB Aeon handles failover and disaster recovery in my experience by working for database recovery, and we perform HA, geo-partitioning, and all related functions.

YugabyteDB Aeon is compatible with other tools or databases in my environment and has integrated well, but this information I will not share with you.

The monitoring and alerting capability of YugabyteDB Aeon meets my needs, as it has multiple built-in dashboards and tracks user structure, query performance, intelligent recommendations, and out-of-the-box integrations with third-party applications such as Hill to monitor.

The backup and restore functionality with YugabyteDB Aeon has different facilities available; mainly, there are third-party applications such as Commvault for backup.

I have not seen a return on investment from YugabyteDB Aeon; I cannot share any relevant metrics such as money saved, time saved, or fewer employees.

I do not know about the experience with pricing, setup cost, and licensing for YugabyteDB Aeon because it will be managed by the account department.

Before choosing YugabyteDB Aeon, I evaluated other options; as such, we are not using AI options other than YugabyteDB, and after YugabyteDB Aeon, I will work on multiple AI tools such as Teradata, Cloudera, and all.

I would rate YugabyteDB Aeon an eight out of ten.

I choose eight out of ten because YugabyteDB Aeon does not work on a large scale level database; it works better for small databases or we can say cloud databases.

Regarding YugabyteDB Aeon's AI capabilities, I think that there are no particular built-in features where we can use it for risk governance and security.

Concerning YugabyteDB Aeon's AI capabilities, for cloud-native software applications, it will be reliable, but we cannot say it will be reliable for bare-metal clusters.

In terms of latency and throughput for my workloads, YugabyteDB Aeon has different workload mechanisms to integrate, so it depends on how my workload is required.

The documentation and learning resources for YugabyteDB Aeon are useful, as the knowledge articles provided by YugabyteDB Aeon are useful but need consolidated data on what is required.

My advice for others looking into using YugabyteDB Aeon is that you can use YugabyteDB Aeon if you are using the public cloud, not on the private cloud or private infrastructure. My overall rating for YugabyteDB Aeon is eight out of ten.

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 has a cluster that is easy to start. They provide AWS and Google Cloud Storage for clusters, which is really good.

Setting up a cluster in YugabyteDB Aeon is not difficult. It requires information about data consumption, CPU storage, the number of threads and cores in the cluster, and RAM usage. However, you may not know these details initially. For a free trial, I used it and found it very easy to start by simply clicking on the website and beginning to create a cluster. You do not need to configure CPU usage or any RAM details; it is predefined and ready to use.

I have some knowledge about distributed systems, and YugabyteDB Aeon does have nodes. However, the documentation is not very good. If I were from a different field and wanted to work with a database, I would not find it user-friendly. If the documentation were generalized, it would be easier for all users across all domains.

The easy operation and Python packages from YugabyteDB Aeon have saved my time. YugabyteDB Aeon provides psycopg binary packages specifically for YugabyteDB Aeon, which we can use to make a connection and perform read and write operations. Due to that package available in Python, we can connect and use YugabyteDB Aeon as we would any other database.

The documentation for YugabyteDB Aeon needs to be improved. It does not come across as beginner-friendly documentation. If someone from a different field were to use YugabyteDB Aeon, they would find it difficult to get started. Other than that, it is really good; the system is good, and the architecture and features are really good.

I do not know how large the YugabyteDB Aeon community is because I have not heard of it or come across any community posts. I do not think any other features need to be improved.

An important issue I faced while using YugabyteDB Aeon was that it needs to follow a sequence like one, two, three, four, and so on, but YugabyteDB Aeon does not follow this pattern in a certain aspect.

I have been working for more than one and a half years in my current field.

YugabyteDB Aeon is stable in my experience.

YugabyteDB Aeon's scalability is really good due to the distributed system architecture.

I would recommend that others who want better scaling of their data use the distributed system feature in YugabyteDB Aeon. The cluster setup is not difficult; it is very easy. These are all the things I would recommend to someone if they are going to use YugabyteDB Aeon. I would rate this product highly based on my overall experience.