Developer Advocate at Yugabyte
Franck is a Developer Advocate for YugabyteDB, an open-source distributed SQL database compatible with Postgres. With 25 years of experience in database consulting for development and operations teams, Franck actively engages with conferences, writes articles, and participates in social media to continuously learn and share his knowledge. He is recognized as an Oracle Certified Master and an AWS Data Hero.
Area of Expertise
In the world of PostgreSQL-compatible databases, a newcomer is YugabyteDB. Same protocol, similar open-source license, re-using Postgres query layer but on a distributed storage plugged in place of heap tables and btree indexes. We will explain the reason for it, why it cannot be just an extension, and why it re-uses PostgreSQL. Similarities and differences, with an overview of the underlying technology: LSM Trees, distributed storage, logical clock, consensus protocols.
The goal is to answer the questions like:
- why another database instead of an extension?
- when can it can substitute to standard PostgreSQL, and why?
- when it is not a good choice and PostgreSQL is the best fit?
- what is distributed vs. sharding when it comes to scale-out?
In a world where the development stack flourishes with unmatched scalability and microservices thrive in the embrace of private or public clouds, a quest for the ultimate scaling solution continues. While NoSQL databases have emerged as a solution, they come at the cost of sacrificing certain features crucial for consistent and reliable databases. Traditional SQL databases rely on supplementary layers, augmenting their recovery solutions with eventually consistent read replicas. However, the landscape has transformed, allowing this final piece to scale out effortlessly without compromising efficiency and performance with Distributed SQL. Let us embark on this captivating quest and delve into the world of the new SQL databases, with a focus on Distributed PostgreSQL with YugabyteDB
Your database administrator has raised concerns about inefficient queries generated by Hibernate without providing any explanation? This can be challenging because ORMs abstract away the complexities of what is executed in the database, and every database has a unique implementation. The communication gap between developers and operations further complicates the issue.
In this session, we will explore some Hibernate mapping strategies and analyze the SQL queries generated by them. We will also discuss the impact of these strategies on database performance and provide insights for Java developers to optimize code execution or improve their indexing strategy. Developers can improve application efficiency by understanding how their queries work on the database.
Unlike traditional SQL databases, with their monolithic architecture, YugabyteDB brings horizontal scalability and resilience to the table. Our demo on Amazon EKS will delve into the core motivations behind adopting this cloud-native DB: elasticity and resilience, all while remaining PostgreSQL compatible and open-source.
I use pg_hint_plan to learn about the optimizer, to understand the query planner choices, and sometimes, workaround a problem in production. But hinting is not easy. Fixing the exact plan needs more than one hint. Here are some tips and examples to use pg_hint_plan without surprises.
This session will delve into the benefits of using Distributed SQL for microservices. We will discuss the challenges of managing multiple databases in a microservices environment, such as complexity, inefficiency, and cost. Our focus will be on YugabyteDB, an Open Source and PostgreSQL-compatible distributed SQL database, which offers a potential solution to these challenges. Modern SQL databases are multi-model, including relational, document, text search, timeseries and more and YugabyteDB is multi-API. Combined with horizontal scalability, Distributed SQL offers a single database solution for microservices.
Porting all the features of PostgreSQL to a distributed database that “scales” horizontally is a challenge. But also the opportunity to modernize the underlying technologies of the DB, which becomes “cloud-native”: consensus protocols, logical clocks, automatic sharding. And to replace B-Tree indexes with LSM Tree and SSTables, more suited to SSD and distributed storage.
YugabyteDB is open-source, and we will go into the details of the architecture, at the crossroads of PostgreSQL, Spanner, Cassandra, RocksDB… to better understand the reasons for a new database, and its underlying technology. We will discuss the advantages and the challenges of this unique architecture design: re-using the PostgreSQL query layer, plugged on top of a distributed storage and transaction layer
Developer Advocate at Yugabyte