Please log in to watch this conference skillscast.

In this session you will learn about the architecture of Couchbase and its internals. This session is a good opportunity to understand how Couchbase Server and Clients deals with distribution of the data, caching but also indexing.

After this talk you will see and clearly understand where Couchbase fits in the "CAP Theorem" and see which tradeoffs have been made by the Couchbase development team.

Simplify, then Scale the Data Model: Using a Document-Oriented Database

"Simplify, then add lightness." was Colin Chapman's advice to those seeking performance in auto racing. When deciding where to store the data behind interactive web apps, we developers can now implement such a philosophy through Document-Oriented databases like Couchbase Server. In Couchbase's document-oriented model, the primitive operations operate on data aggregates just like the Java object model behind your application.

Storage and retrieval are done with lightweight operations such as 'get' and 'set'. Indexing and querying is done with Couchbase's views to incrementally map-reduce extract document subelements on demand. Performance in development time, sub-millisecond data access and massive scale come together in this formula.

YOU MAY ALSO LIKE:

• Real World Kotlin Development Workshop (in London on 1st - 2nd July 2019)
• Pivotal's Core Spring (in London on 8th - 11th July 2019)
• Keynote by Markus Eisele on Java in the Age of Containers and Serverless (in London on 20th June 2019)
• London Java Community June (in London on 25th June 2019)
• How To Build a Social Network Entirely on Serverless (SkillsCast recorded in May 2019)
• AdoptOpenJDK - And how it impacts you in 2019 (SkillsCast recorded in May 2019)