Thoughts on distributed databases, open source and cloud native
A lot is happening at YugaByte DB since we announced 1.2, so we thought we’d provide the community with a quick recap of engineering highlights, announcements and shout outs to catch everyone up. Let’s dive in!
Check out our “Roadmap for YugaByte DB 2.0” to get more details on the exciting features shipping in the next big release this Summer!
…
Read MoreThe YugaByte DB community is eagerly looking forward to v2.0, the next major release expected in Summer 2019. Needless to say, we are very excited about the depth and breadth of features in this release. Here’s an overview of the various areas we expect the new release to cover.
YSQL is YugaByte DB’s PostgreSQL wire-compatible distributed SQL API.
…
Read MoreI’m thrilled at the prospect of what lies ahead of me in my new job at YugaByte. I’ve just started in the role of Developer Advocate for YugaByte DB. This is an open source, cloud native, distributed SQL database—in other words, a database for the modern world. There’s an excellent brief description here.
I made this move a couple of weeks ago after almost thirty years at Oracle.
…
Read MoreIf you missed the April 30 webinar with Kyle Kingsbury, the creator of Jepsen and Karthik Ranganathan, CTO at YugaByte, you can check out the playback here and download the slides here.
Kyle did a great deep-dive into his testing approach, research methodology and what he found when applied to YugaByte DB.
…
Read MoreToday’s microservices rely on data with different models and read/write access patterns. Polyglot persistence, first introduced in 2008, states that each such data model should be powered by an independent database that is purpose-built for that model. This post highlights the loss of agility that microservices development and operations suffer when adopting polyglot persistence. We review how distributed SQL serves as an alternative approach that doesn’t compromise this agility.
…
Read MoreYou can join the discussion on HackerNews here.
We crossed the three year mark of developing YugaByte DB in February of this year. It has been a thrilling journey thus far, but not without its fair share of technical challenges. There were times when we had to go back to the drawing board and even sift through academic research to find a better solution than what we had at hand.
…
Read MoreThe glory days of the heavy-weight hypervisor are slowly fading away, and in the last few years, containerization of applications and services is the new reality. With containerization, enterprises can prototype, deploy, and meet scale demands more quickly. To systematically and efficiently manage these large-scale deployments, enterprises have bet on technologies like Kubernetes (aka k8s), a powerful container orchestrator, to get the job done.
…
Read MoreToday’s developers understand that the key requirement to converting and retaining customers is all about delivering fast and responsive experiences, while remaining resilient to failures and compliant with data governance regulations. YugaByte DB is purpose built for geo-distributed applications that require high availability, high performance and regulatory compliance. In this blog, we are going to “look under the hood,” to explore exactly how YugaByte DB distributes data across multiple clouds,
…
Read More
You can join the discussion about the results on HackerNews here.
Last year we published our DIY Jepsen testing results – including the tests and failure modes implemented as well as the bugs found. We recently engaged Kyle Kingsbury, the creator of the Jepsen test suite, for an official analysis and are happy to report that YugaByte DB 1.2 formally passes Jepsen tests using the YCQL API.
…
Read MoreOur previous post dived into the details of the storage layer of YugaByte DB called DocDB, a distributed document store inspired by Google Spanner. This post focuses on YugaByte SQL (YSQL), a distributed, highly resilient, PostgreSQL-compatible SQL API layer powered by DocDB. A follow-up post will highlight the challenges faced and lessons learned when engineering such a database.
…
Read More
