Setting the number of shards/tablets in your YugabyteDB cluster is dependent on your table size and activity, and while it is hard to gauge the exact number, here are some high-level suggestions.
YugabyteDB’s compatibility with Postgres and Cassandra allows seamless integration with popular third-party tools and integrations, such as visualization tools like pgAdmin, DBeaver, and ArcType, as well as Kafka, Spark, Flyway, and drivers and ORMS, due to the decision to reuse the Postgres query layer (YSQL) and recreate Cassandra using C++ (YCQL).
YugabyteDB’s implementation of DocDB, based on RocksDB, has made significant improvements to ensure node density and scalability, allowing hundreds of tablets per tserver without limiting the amount of data per node.
In a recent interview, Amit Patel, Principal Architect at Comcast, discussed the challenges of managing global data distribution with legacy databases, and how the company evaluates new technologies like distributed SQL to support modern workloads that align with their business goals and objectives.
Marc Hansen, a systems engineer at Fiserv, recently sat down to discuss his role at this top global fintech and payments company, where he works with both DBaaS and traditional databases. During the conversation, he discussed how cloud technologies, PostgreSQL compatibility, and automation impact how DBAs approach disaster recovery, observability, and database deployment.
In a distributed database, data is split into multiple tablets which reside on different nodes. So it is not just tables, but indexes, that are distributed across nodes. So let’s examine how to optimally design distributed indexes to get the best query performance.
Jay Duraisamy, the SVP of Technology for Data and Analytics at Fiserv, sat down with us to discuss how Fiserv is unlocking the value of their data and providing new services for both merchants and consumers by bringing together data and analytics on one platform.
Tom Eck, Sr. Vice President of Digital Transformation at Fiserv, sat down with us to discuss all things application development, including how Fiserv is planning to monetize their data and how application development teams need to modernize to best support cloud native applications.
In this excerpt from the recent white paper, Migrating From Monolithic to Cloud Native Operational Databases, we look at three of the challenges faced by companies using the current generation of NoSQL databases and why distributed SQL may be a better choice.
In a previous blog, we developed an application-level sharding layout to avoid hotspots. With that layout in mind, where order is maintained within each shard, let’s discuss how to design a query to return data with pagination while maintaining the global ordering.
