“…An ounce of prevention is worth a pound of cure…” Using customer use cases we’ll review how to identify a healthy cluster and spot issues before they become problems for your application. The talk will cover Couchbase monitoring and explain how to interpret key statistics to identify common problems.
By automating the deployment of application inside software containers, Docker makes life easier for everyone – and by providing an always-on, scalable, flexible NoSQL database, Couchbase Server is enabling you to build applications like never before, with performance that was once unattainable. In this session, Docker’s Patrick Chanezon and Couchbase’s Tim Stephan will discuss how to combine the simplicity of Docker with the power of Couchbase Server to streamline your application development and deployment process. Developers – get the infrastructure out of the way and focus on your app. Architects – be secure in the knowledge that your applications will perform at scale.
Are you new to the world of NoSQL? In this session we’ll take a look at why enterprises are adopting NoSQL technologies, learn about the main flavors of NoSQL databases and the considerations you need to think about when evaluating NoSQL. We’ll also take a look at the common use cases of NoSQL technologies and a quick look into document modeling.
Join this demo-filled session to learn how to deliver continuously available mission critical apps across data centers. For today’s mission critical apps, high availability is no longer a ‘nice to have’ but is essential. Downtime and data loss is unacceptable, resulting in lost revenue. In this session we will cover the wide array of high availability and disaster recovery features available in Couchbase Server.
From operation timeouts to node failures, what happens when things go wrong with your Couchbase Server application? Drawing on experience of real-world customer cases, we’ll share some of our war stories on what can happen to Couchbase Server deployments, the steps we took to troubleshoot them and how they could have been avoided.
Jerry talks about lessons learned taking the second-highest QPS Couchbase Server at LinkedIn from meltdown to awesome. The story of Couchbase at LinkedIn is an insightful and suspense-filled story of making slow progress in tuning a system for performance. Jerry’s team runs one of the fastest (by QPS or latency standards) Couchbase clusters within LinkedIn by making clever use of SSD’s and by tuning the parameters correctly. Achieving this kind of standard in tuning is done primarily by avoiding the use of buckets, and tuning the right number of reader-vs-writer threads. In this session, learn best practices for tuning at scale.
Couchbase Server 4.0 offers new security features that allow administrators to customize security for different users and, above all, protect their deployments. A secure deployment requires defensive, in-depth security controls for authentication, authorization, encryption, auditing and administration. In this session, Solutions Engineer Darin Briskman and Senior Product Manager Don Pinto will show attendees how to leverage the features in Couchbase Server 4.0 and present integration options with third-party partner solutions. This talk will include technical details of the new administrative auditing functions and a demonstration of a centralized auditing solution.
What happens when you combine the industry-leading performance and scalability of Couchbase Server with the horsepower of Google’s Compute Cloud? In this joint talk between Google and Couchbase we’ll provide expert insight into how Google’s Compute Cloud is constructed. We’ll then walk you through how we provisioned and tuned Couchbase Server for this platform before revealing how little it costs to perform 1 million writes to a dataset of 3 billion documents!
With increased adoption of the NoSQL, companies are also increasingly populating Couchbase Server with sensitive information. This information can take the form of such things as personally identifiable information (PII), personal health information (PHI), or sensitive customer/internal information. This information must adhere to regulatory requirements – such as PCI and HIPPA, adhere to state and local privacy laws, adhere to customer and partner service level agreements, and have controls in place to prevent insider abuse of the sensitive information. In this session, learn how Vormetric and Couchbase have partnered together to address the data security needs for protecting sensitive information being stored in Couchbase Server.
In this talk Brian Harrington, Principal Architect at CoreOS will join Traun Leyden from Couchbase to 1) Provide a deep dive on the technology behind Kubernetes, and 2) Walk through the steps required to get Couchbase running on Kubernetes. Kubernetes: One of the most promising products to hit the DevOps world lately is Google’s Kubernetes. Having 10+ years of experience running “internet scale” container clusters based on Borg and other internal projects, Google has decided to re-architect their cluster based on Docker / rkt container technology and release it as Open Source to the world. CoreOS Tectonic: CoreOS recently announced Tectonic: a commercial platform that combines Kubernetes and the CoreOS stack. It is an integrated software platform for Linux containers. This includes a management console for workflows and dashboards, an integrated registry to build and share Linux containers, and additional tools to automate deployment and customize rolling updates. You can run Tectonic in the public cloud such as on Amazon Web Services or Google Container Engine, or you can run it on-premise on bare metal clusters. Couchbase: Couchbase Server is a distributed, always-on, scalable, flexible NoSQL database, that enables you to build applications in an agile way, with great performance. At Couchbase we are constantly on the lookout for technologies which reduce the DevOps effort required by our users. Kubernetes (and therefore, Tectonic) is an ideal deployment platform for Couchbase Server, since it is architected to minimize the amount of work required to scale a cluster up or down. Building on Kubernetes also avoids vendor lock-in, since your cluster will be able to run anywhere that Kubernetes runs — anywhere from cloud providers down to bare metal clusters.