When your application updates a column of a record in PostgreSQL, the database creates a new version of the entire record for the MVCC needs. However, that's not the case in YugabyteDB which works at a more granular level. When you update the column in YugabyteDB, the database creates only a new version of the column and not the whole record.
In this episode, see how the @DynamicUpdate annotation of the Hibernate framework helps YugabyteDB avoid the storage size amplification by storing only the versions of the columns that were actually updated by the application logic.
Curious to learn more? Check out our previous episode—Distributed SQL Tips for Java: @DynamicUpdate Annotation
• Distributed SQL Tips for Java: @Dynam...
0:00 Introduction
0:51 Test Overview
1:51 Disabling @DynamicaUpdate, checking the side effects
4:18 Enabling @DynamicUpdate, checking column version
5:46 Summary
About Yugabyte: YugabyteDB is an open source, high-performance distributed SQL database built for your mission-critical applications. It is PostgreSQL compatible, cloud native, and runs on any public or hybrid cloud.
Learn more: https://www.yugabyte.com/
Learn more about distributed SQL at https://www.yugabyte.com/distributed-...
DISCOVER MORE IN OUR DISTRIBUTED SQL TIPS FOR JAVA SERIES:
• Distributed SQL Tips for Java
RESOURCES:
-YugabyteDB / Start Now: https://cloud.yugabyte.com
-Site: https://www.yugabyte.com
-GitHub: https://github.com/yugabyte
COMMUNITY:
-Slack: https://communityinviter.com/apps/yug...
-YouTube: / yugabyte
-Instagram: / yugabytedb
-Twitter: / yugabyte
-LinkedIn: / yugabyte
You can connect to all our community channels here: https://linktr.ee/yugabyte