The following text is an excerpt from the new white paper, Migrating From Monolithic to Cloud Native Operational Databases
In this section, we walk through the three challenges of using current generation NoSQL databases: operational complexity, frustrating application development, and inconsistent customer experiences.
1. NoSQL operational complexity
As noted in the previous section, databases have evolved to become cloud hosted but are far from cloud native.
We are excited to announce that registration is now open for our fourth annual Distributed SQL Summit (DSS) 2022 on September 14th.
This virtual event will be our biggest global event to date. Additionally, a series of in-person DSS days around the world will follow this event.
The Distributed SQL Summit 2022 brings together the Distributed SQL community, customers, partners, and industry thought leaders. The goal of the event is to explore the challenges and opportunities of database modernization and transformation.
As organizations continue to embrace the public cloud for their applications, migrating business-critical data to cloud native databases remains one of the biggest barriers to accelerating cloud adoption. Organizations also want the freedom and confidence to move key applications and the underlying data to their choice of public, private or hybrid clouds.
Developed in response to customers who are struggling with migration from single node Postgres and similar environments, YugabyteDB Voyager is available today to remove many of these barriers.
Reports show that 89% of companies with above average customer experiences perform better financially than their competitors. A lot of factors influence customer experience. However, in today’s world where more and more of your customers interact with you and your company mainly through applications, online services or automated systems, the performance of those applications can make or break your business.
Database performance has a significant impact on that application’s overall performance. But performance is impacted by a wide range of variables,
As a developer, your time is extremely valuable. We try to remember that every day as developers power Yugabyte. That means we deliver the most developer-friendly database to make your job easier and your career more successful. And YugabyteDB 2.15, our latest preview release, continues that commitment
This release contains several new enhancements to help you onboard rapidly and leverage familiar, proven capabilities and tools. With the new release, you can reduce your time-to-market for new innovations by eliminating those time-consuming projects to fix nagging issues in your legacy database.
Several of the key innovations released in YugabyteDB 2.15 help you not just survive, but thrive, in the face of changes. New YugabyteDB features support a diverse set of applications and their inherent unpredictability with greater ease. By leveraging a flexible, unified database you can avoid re-architecting applications or augmenting your environment with new databases.
Predicting how your applications and their requirements will change and morph over time is almost impossible. We live in a world where old customers disappear,
Welcome to YugabyteDB Product Week! We are thrilled to announce one of the most extensive updates to YugabyteDB since its initial launch. YugabyteDB 2.15 and our new YugabyteDB Voyager are available now!
Our latest database release introduces a suite of features focused on dynamic workload optimization, developer productivity features, and improved performance.
YugabyteDB Voyager, our new open source data migration engine, simplifies the movement of traditional and cloud-based databases to YugabyteDB.
Summer is finally here and there’s no better time to sit back and enjoy a nice, refreshing scoop! June’s monthly scoop for YugabyteDB Managed is loaded with cool new features that we are sure will get your summer started right.
Check out these latest features (and for previous posts, check out our archive):
Fast cluster creation
No more twiddling thumbs while your cluster is getting created.
The first answer to this question is the usual “it depends“. The second answer, thanks to YugabyteDB’s auto-splitting feature and distributed SQL sharding principles, is “don’t worry, this is managed automatically.”
However, it’s still important to understand how sharding works, how to handle corner cases correctly, and how to split tablets to save resources. In this post, we’ll explore how sharding works in YugabyteDB by defining the initial quantity and size of tablets.