Whether you have been using Couchbase with .NET for a couple of years or you are a .NET developer who is new to Couchbase, you will benefit from this session on strategies for data access with the current 2.1 and upcoming 2.2 .NET SDKs. Martin and Jeff will cover the API and interfaces provided by the SDK, including a couple of different strategies and patterns for mapping and querying data. The session will show in demos and code the mapping to POCOs from the repository pattern, how to use asynchronous operations, and even how LINQ fits in with current and future SDKs.
When you’re running 600 Couchbase nodes on 6 datacenters worldwide, happily servicing peaks of 10M QPS and all you have is a .NET client, things start getting interesting in ten millions ways. This is the story of how we embraced other technologies to improve our solution, rewrote an open source .NET Couchbase client from scratch, and how to tackle the head-warping problems that arise at scale.
Several new services in Couchbase Server 4.0 have been written in Go. As one of the original ‘go-nuts’ at Couchbase, Marty Schoch will articulate some of the lessons Couchbase has learned in building these new services – from memory management to native library integration – and how Go figures into new Couchbase services in the pipeline. Couchbase goes further with a Go SDK as well. Currently in Developer Preview, the Go SDK, go-cb, is designed to have a similar interface to all of the other Couchbase SDKs. Matt Ingenthron will 1) review the API provided by the Go SDK, 2) highlight some of the internal tricks and 3) show how it figures into Couchbase applications.
N1QL extends the power of SQL to JSON, enabling full query capabilities on Couchbase Server and removes one of the final hurdles to migration from MySQL to the flexible, scalable Couchbase Server. But in order to migrate seamlessly from MySQL to Couchbase, it is imperative to know the language and implementation differences between MySQL and N1QL. This talk will discuss various aspects of how to approach migration including: document key design, data modeling, migration options, and the language. This session will also give attendees an understanding of the different steps involved in making the decision to migrate from MySQL to Couchbase via N1QL.
Reliably delivering data to applications in a high performance way is where Couchbase shines, but maintaining a high-performance application is not just a job for Couchbase Server. Couchbase Server meets very stringent performance and availability needs, but to successfully deliver data at scale, all application components need to work together as a single system. For example, you need to be prepared for various edge conditions like expected “TMPFAIL”s, handling failovers, and dealing with higher latencies under load. Good thing you have the tools you need from the Couchbase SDK. In this session, Michael and Matt will show patterns for handling these kinds of scenarios and talk about some of the great failures from years of experience, how they can be prevented and demonstrate some techniques for making the entire system more reliable and able to recover faster.
We’re all familiar with modeling data the relational way. When we move to a document database we need to think about things a little differently. In this talk we’ll look how best to plan, model and maintain your data using a document database. By diving into real world case studies of Couchbase users, we’ll look at the three main things you need to know about modeling your data in a document database: document design, key design and querying.
MongoDB has been the default database choice in the Node.js world for too long. That’s largely been thanks to the Mongoose ODM, which makes it simple to create an MVC pattern application with some of the same abstraction you’d get from a full framework such as Rails. Now that we have the Ottoman ODM for Couchbase, it’s far easier to build Node.js apps backed by Couchbase. In this talk, I’ll show how to build a simple Node.js application that follows the MVC pattern. At first I’ll start out using the Node.js client directly, both through key-value access and with N1QL, and then I’ll switch to using Ottoman to show just how effortless it can be to use Couchbase Server in your Node.js applications.
Old application? Ugly or outdated designs? High cost of maintenance? An in-depth look into our experience in using Couchbase as a catalyst to modernize a standalone software appliance into cloud-based horizontally-scalable services.