Couchbase's chief techie on squaring the schema-less circle
(2023/03/31)
- Reference: 1680258846
- News link: https://www.theregister.co.uk/2023/03/31/interview_squaring_the_schemaless_circle/
- Source link:
Interview Couchbase is a JSON document database with global users including PayPal, eBay, and travel distribution system Amadeus, companies with a combined revenue of nearly $40 billion. Its total annual income was $154.8 million, so why is such a small database outfit trusted by big biz?
We caught up with CTO Ravi Mayuram to find out about the history of the system which became a leader in the NoSQL movement. You can view the video below.
Mayuram argued that since relational systems were first designed in the 1970s, the IT landscape has changed. “Networks are faster, memory is cheaper, and there is a cloud-based consumption model. These were not available when the relational systems were built, so they are showing their age. We wanted to build something that would stand the test of time, just like relational systems did,” he said.
One of the significant departures Couchbase took from the relational approach to databases was to avoid designing the data schema up front. This move has attracted criticism from some database experts.
“Having the schema is when you really pay the price. If you have a schema, data is in a solid brick form. Whenever you want to move that, you have to sort of re-cast that into a new schema when you go from system to system,” he said.
[1]
Instead, Couchbase employs something called a late-binding schema, which are not tied to the underlying database objects that it references.
[2]Microsoft adds silicon muscle into latest Azure SQL database configs
[3]MotherDuck scores $47.5m to prove scale-up databases are not quackers
[4]Redis swallows RESP.app biz that made its database easier on developers
[5]Rows, columns, and the search for a database that can do everything
“You always need a schema — without that there is no structure — but a schemaless database removes that friction between front end and back end. There is no separate application schema and database schema; there is only one schema which is what the application defines,” he said.
But from [6]Couchbase 7.0 it began to look a bit more like a relational database by offering multi-statement SQL transactions which cover what relational systems can offer from the standpoint of OLTP guarantees but also preserves performance, scale and flexibility, the company argued.
[7]
In the video, Mayuram talks listeners through these design choices and elaborates on how they change the role of developers and DBAs within tech teams. ®
Get our [8]Tech Resources
[1] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_specialfeatures/spotlightondatabases&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZCcDo@-VyW-hP7UfIwLYegAAAEc&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[2] https://www.theregister.com/2022/12/01/microsoft_azure_database_chips/
[3] https://www.theregister.com/2022/11/17/475_million_says_scaleup_databases/
[4] https://www.theregister.com/2022/11/03/redis_resp_app/
[5] https://www.theregister.com/2022/06/22/snowflake_unistore_analysis/
[6] https://www.theregister.com/2021/07/29/couchbase_7/
[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_specialfeatures/spotlightondatabases&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZCcDo@-VyW-hP7UfIwLYegAAAEc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[8] https://whitepapers.theregister.com/
We caught up with CTO Ravi Mayuram to find out about the history of the system which became a leader in the NoSQL movement. You can view the video below.
Mayuram argued that since relational systems were first designed in the 1970s, the IT landscape has changed. “Networks are faster, memory is cheaper, and there is a cloud-based consumption model. These were not available when the relational systems were built, so they are showing their age. We wanted to build something that would stand the test of time, just like relational systems did,” he said.
One of the significant departures Couchbase took from the relational approach to databases was to avoid designing the data schema up front. This move has attracted criticism from some database experts.
“Having the schema is when you really pay the price. If you have a schema, data is in a solid brick form. Whenever you want to move that, you have to sort of re-cast that into a new schema when you go from system to system,” he said.
[1]
Instead, Couchbase employs something called a late-binding schema, which are not tied to the underlying database objects that it references.
[2]Microsoft adds silicon muscle into latest Azure SQL database configs
[3]MotherDuck scores $47.5m to prove scale-up databases are not quackers
[4]Redis swallows RESP.app biz that made its database easier on developers
[5]Rows, columns, and the search for a database that can do everything
“You always need a schema — without that there is no structure — but a schemaless database removes that friction between front end and back end. There is no separate application schema and database schema; there is only one schema which is what the application defines,” he said.
But from [6]Couchbase 7.0 it began to look a bit more like a relational database by offering multi-statement SQL transactions which cover what relational systems can offer from the standpoint of OLTP guarantees but also preserves performance, scale and flexibility, the company argued.
[7]
In the video, Mayuram talks listeners through these design choices and elaborates on how they change the role of developers and DBAs within tech teams. ®
Get our [8]Tech Resources
[1] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_specialfeatures/spotlightondatabases&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZCcDo@-VyW-hP7UfIwLYegAAAEc&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[2] https://www.theregister.com/2022/12/01/microsoft_azure_database_chips/
[3] https://www.theregister.com/2022/11/17/475_million_says_scaleup_databases/
[4] https://www.theregister.com/2022/11/03/redis_resp_app/
[5] https://www.theregister.com/2022/06/22/snowflake_unistore_analysis/
[6] https://www.theregister.com/2021/07/29/couchbase_7/
[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_specialfeatures/spotlightondatabases&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZCcDo@-VyW-hP7UfIwLYegAAAEc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[8] https://whitepapers.theregister.com/
Self-contradictory
These were not available when the relational systems were built, so they are showing their age. We wanted to build something that would stand the test of time, just like relational systems did .
If something is "showing its age", it can't also be "standing the test of time".
Schemas are a must but the problem isn't with schemas per se but making changes to them over time. This is perfectly possible with the transrelational approach but the industry has found more money can be made with others…