What do you like best about the product?

As someone new to software, I found YugabyteDB very approachable compared to other distributed databases. It supports both SQL (like PostgreSQL) and NoSQL-style access, which made it easy for me to learn and experiment with. The documentation is clear, and the community is helpful when you’re stuck. I like that it scales horizontally, which means you can handle more users just by adding more servers. It’s also open-source, which is great for students or beginners who want to learn hands-on without worrying about costs.

What do you dislike about the product?

Some of the advanced features, like setting up a multi-region deployment or understanding consistency models, were a bit overwhelming at first. It took me some time to understand how YugabyteDB differs from traditional databases like MySQL or PostgreSQL in terms of architecture and operations. Also, there are fewer tutorials and videos compared to more established databases, so it sometimes felt hard to find beginner-friendly help.

What problems is the product solving and how is that benefiting you?

YugabyteDB is solving the problem of needing a database that can handle large amounts of data and many users without slowing down. It gives the power of traditional SQL databases with the scalability of NoSQL systems. For me, as someone new to the software field, it helped me understand how modern applications manage data across different regions and servers while staying fast and reliable. It’s also helping me learn how real-world systems are built — like how companies make sure their apps don’t go down even if one part of the system fails. It’s been a great learning tool and has given me confidence to explore more advanced database concepts.

What do you like best about the product?

Mostly PostgreSQL compatible, global distribution, and horizontal scalability. Built-in resilience and support for distributed ACID transactions allowed us to handle millions of daily orders with zero downtime.

What do you dislike about the product?

Operational overhead. Managing a distributed system added complexity we didn’t face with traditional databases. Some PostgreSQL features weren’t fully supported, which required workarounds.

What problems is the product solving and how is that benefiting you?

Solves the problem of scaling a relational database without giving up consistency or SQL features

What do you like best about the product?

YugabyteDB provides high availability and consistency as powerful distributed SQL database, its familiarity with other developer friendly databases like Postgresql helps us in easy to integrate and easy to use additionally it has a robust community support which helps us to resolve issues faster.

What do you dislike about the product?

With multiple nodes implementation its sometimes become difficult to manage.

What problems is the product solving and how is that benefiting you?

We were facing issues of scalability but with YugabyteDB horizontal scaling our business need get fulfilled, also with its low latency and high availability YugabyteDB becomes our first choice

What do you like best about the product?

PostgreSQL Compatibility: Allows quick onboarding and minimizes refactoring efforts.
Distributed SQL Engine: Provides horizontal scalability, HA, and geo-distribution out of the box.
Fault Tolerance: Handles individual node failures well, ensuring minimal disruption.
Developer Enablement: SQL-native access with good documentation and active community.
Good OLTP Performance: For high-throughput transactional workloads, YugabyteDB performs reliably under optimal conditions.

What do you dislike about the product?

Current Challenges and Limitations
We list below the most critical issues and limitations currently impacting our YugabyteDB deployment for the Iris application:
1. DDL Atomicity and Concurrency
Concurrent DDL on different objects often fails or causes schema mismatch errors.
2. Truncate Behavior
Truncate operations retain old tablets, causing resource sprawl (CPU, disk).
3. Slow Aggregations / Analytical Queries
Aggregate functions (e.g., COUNT, SUM, GROUP BY) perform poorly on large tables.
4. Large Query Errors
Queries fail with RPC message size errors; workarounds require non-trivial gflag tuning.
5. Index Creation Challenges
Index creation on large tables is slow (can take hours) and unstable if DMLs are running.
Failure of concurrent DDLs can result in application downtime or stale views.
6. Intermittent Application Slowness
During high-ingestion windows (e.g., Spark + C# clients), CPU spikes to 80–85%.
7. Slow Queries Despite Indexing
Poor performance even with correctly designed indexes.
8. DR Limitations
DR requires symmetrical 3-node cluster and does not replicate DDL—this increases manual effort.
9. Node Crashes
Occasional crashes due to pg_client_use_shared_memory bug.
10. Resource Utilization
Max 1800 concurrent connections across 6 nodes (300/node).
High CPU usage (80%+) under 5500 OPS and 1500+ connections.
11. PITR Disk Usage
PITR with 2-day retention consumes 1–2 TB of disk.
Expected behavior, but storage overhead is significant.
12. Audit Logging
pgaudit causes crashes and lacks centralized log management.
Prefer audit logs to be stored as queryable tables.
13. Tablet Rebalancing
Rebalancing takes 2–3 hours post node failures.
14. Schema Name Change Not Reflected in UI

15. Query Performance Monitoring
No centralized query metrics dashboard across nodes.
pg_stat_statements is per-node; requires custom data aggregation.
16. Lack of ORM Support
Prisma ORM lacks native Yugabyte support.
Clear timeline for a smart driver integration is still needed.
17. Other Issues
Dead tuples causing transaction failures .
Clock skew-related tserver crashes .
Incorrect health checks leading to table drop incidents.
Backup to S3 failed due to endpoint misconfig .
Recommendations & Expectations
Top Priorities for Upcoming Releases:
Full concurrent DDL/DML support
Improved join and aggregation performance
Central query dashboard across universe
Audit log offloading and centralization
Smart tablet rebalancing and table-level recovery
Simplified backup/restore UX (especially for S3)
Documentation and Usability:
Better defaults for performance-related gflags.
Clear guidance on best practices for DDL coordination and high-throughput ingestion.
Support & Training:
More structured training on query optimization and resource tuning
Roadmap visibility for critical features (e.g., Prisma ORM support)
Final Thoughts
We appreciate Yugabyte’s continued partnership and responsiveness to issues. The platform shows strong promise for OLTP workloads and mission-critical deployments, but there are clear gaps—especially around operational tooling, analytical query support, and DDL concurrency—that we hope to see addressed in the near-term roadmap.
Our team remains committed to collaborating with Yugabyte to improve the product and looks forward to further performance and reliability enhancement

What problems is the product solving and how is that benefiting you?

YugabyteDB is helping us reduce our MS SQL Server licensing costs by allowing us to re-architect our application on a scalable, open-source distributed SQL platform. This shift not only cuts licensing expenses but also enables us to design for horizontal scalability, which is a major advantage as our data and user base grow.

Additionally, YugabyteDB’s automated sharding and replication improve operational efficiency by reducing the need for manual intervention in scaling and fault tolerance. Overall, it’s helping us build a more cost-effective, cloud-ready, and resilient infrastructure.

What do you like best about the product?

1. PostgreSQL Compatibility
Benefit: Developers can use familiar SQL syntax, PostgreSQL drivers, and tools. This eases adoption for teams already using PostgreSQL but needing distributed capabilities.

2. High Availability & Fault Tolerance
Benefit: YugabyteDB uses the Raft protocol for consensus, ensuring consistency and fault tolerance even in multi-region deployments. Automatic failover, replication, and distributed consensus protect against node failures without sacrificing performance.

What do you dislike about the product?

1. Operational Complexity
Running a distributed SQL database isn't as simple as a single-node Postgres instance. Cluster management, tuning, and monitoring require more expertise, especially for production environments.

2. Maturity of Features
While rapidly evolving, some PostgreSQL features are still not fully supported, and some edge cases may behave differently.

What problems is the product solving and how is that benefiting you?

YugabyteDB is designed to solve several major challenges that modern, cloud-native, and high-scale applications face with traditional databases.

What do you like best about the product?

You can pause and start anytime.
The team is very helpful

What do you dislike about the product?

Nothing as of now. They may try to do the service in microservice

What problems is the product solving and how is that benefiting you?

Helped me to gain experience in database

What do you like best about the product?

YugabyteDB is an excellent database for anyone needing a powerful distributed system. It works like PostgreSQL, so you can use the same familiar queries, but it also takes care of all the tricky parts of distributed design for you. This makes it easy to use, even for complex applications.

The best part is their support team—they're quick to respond and really helpful, making sure everything runs smoothly. If you're looking for a database that's reliable, easy to work with, and backed by a great team, YugabyteDB is a great choice.

What do you dislike about the product?

YugabyteDB is powerful but has a few downsides. It has a learning curve for distributed systems and a smaller community ecosystem compared to established databases. Some advanced features may also feel less mature, requiring extra effort during implementation.

What problems is the product solving and how is that benefiting you?

YugabyteDB solves the challenge of building scalable, highly available databases that can handle global distribution without sacrificing the ease of using familiar SQL queries. It manages the complexity of distributed systems behind the scenes, including spreading data clusters across regions and maintaining data replication. This means that if any node goes down, the data is still accessible from other nodes, ensuring zero downtime.

For me, this means faster development with fewer headaches, reliable performance even as my applications grow, and confidence that data is safe and accessible anywhere. It helps deliver a better user experience and reduces operational overhead.

What do you like best about the product?

The ability of Yugabyte to transparently provide the Postgresql wire compatibility is amazing for existing applications along with it's horizontal scalability make Yugabyte an amazing data store choice.
Support team was great in helping us overcome some of the performance challenges we encountered.

What do you dislike about the product?

When we evaluated it, it still had some performance challenges that we had to overcome with their support team.

What problems is the product solving and how is that benefiting you?

Horizontal scalability with standard relational database capabilities.

What do you like best about the product?

I like most the distributed nature of YugabyteDB and its high data storage capabilites. DBaaS - Database as a Service.
Another great thing is yugabyteDB is open source.

What do you dislike about the product?

Nothing. ACID compliance and maintaining distributed database is really a great thing.
It requires deep analysis to find any issues.
In my opinion, it is getting better everyday.

What problems is the product solving and how is that benefiting you?

I am a indirect user of YugabyteDB. I experienced the limits in normal SQL DB.
NoSQL DB solves specific issues. But the YugabyteDB potenial is way beyond NoSQL and normal SQL.

What do you like best about the product?

YugabyteDB is 100% compatible with PostgreSQL. It was easy to migrate our PostgreSQL workloads to YugabyteDB. Our main issues with PostgreSQL was the ability to scale, YugabyteDB helped us overcome these obsticales.
YugabyteDB also works great in the cloud and is cloud vendor agnostic, so we don't have to be tied to a single cloud provider.

What do you dislike about the product?

YugabyteDB is a relatively new software and industry adaptation is low, so it is hard to find system administrators who have the knowledge and expertise with YugabyteDB.

What problems is the product solving and how is that benefiting you?

YugabyteDB has helped us overcome the performance and reliability issues we previously had with services that used PostgreSQL as their database. Now we can scale these workloads much more easily.