O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a navegar o site, você aceita o uso de cookies. Leia nosso Contrato do Usuário e nossa Política de Privacidade.
O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a utilizar o site, você aceita o uso de cookies. Leia nossa Política de Privacidade e nosso Contrato do Usuário para obter mais detalhes.
A Scribd passará a dirigir o SlideShare em 1 de dezembro de 2020A partir desta data, a Scribd passará a gerenciar sua conta do SlideShare e qualquer conteúdo que você possa ter na plataforma. Além disso, serão aplicados os Termos gerais de uso e a Política de Privacidade da Scribd. Se prefira sair da plataforma, por favor, encerre sua conta do SlideShare. Saiba mais.
New to Couchbase or NoSQL in general? Wondering how to get started? Join this session to get up to speed quickly with the essential concepts. Learn how Couchbase’s data platform builds on top of the NoSQL basics and provides powerful services for developers to tap into for accelerated application development. Learn how you can start to use these services and APIs right away, with minimal coding and targeting many of the common application programming patterns.
Hear from Brant Burnett, systems architect at CenterEdge Software and recognized Couchbase Expert, on how to use LINQ and .NET to seamlessly transition your existing SQL and application development skills and knowledge to Couchbase Server. Learn how easy NoSQL can be with the help of Couchbase, N1QL, and LINQ.
Note that our updates always go directly to the data nodes, not through queries, because it’s faster. Avoids query generation on the client and query parsing on the server normally used by RDBMS solutions.
Cover how different jobs require different tools. As developers, we can use a screwdriver to turn a nut, but it won’t be fun or efficient. ** Advance Animation ** Instead, it’s much better to use a screwdriver for some jobs, and a wrench for others ** Advance Animation** Microservices allow you to develop using this paradigm. Each service can use the toolset that’s best for the job. Couchbase melds very well with this paradigm.
We started with a traditional .Net monolith accessing a Couchbase cluster ** Advance Animation ** Since then, we’ve transitioned to developing microservices using .Net Core on Docker (Linux for cost savings!) ** Advance Animation ** We’ve also implemented some serverless functions using AWS Lambda and NodeJS
All of these implementations were supported using official Couchbase SDKs provided by the SDK team Moving between them is easy due to consistency of naming conventions, API surface, etc
Discuss how learning new tools can slow down a development team ** Advance Animation** Cover how N1QL = SQL + JSON, so most developers already have 80% of the knowledge they need Discuss how we had a developer successfully start developing using N1QL on his first day on the job
LINQ2Couchbase is one example of extensions to the common SDK paradigm that is specific to a development platform While the SDKs try to keep as much in common as they can, they also don’t introduce artificial limitations where the platforms differ
Note that this is my example of a good practice for building a .NET POCO for LINQ
Make note of how the DocumentFilter attribute pairs well with type filters on indexes ** Advance Animation ** Reduce number of indexes when you have multiple types that share the same property ** Advance Animation ** Speak to efficient indexing and the pitfalls of the primary key scan for Couchbase
Queries are great, but that’s only ½ of what you do with a database. What about changes? ** Advance Animation ** Now we’re going to add the change equivalent of the easy button
Cover how proxies reduce memory utilization when dealing with large documents
*** 3 Arrows *** Key attribute should be used on the property that contains the document key, used on save Properties are virtual so they can be overridden by Linq2Couchbase to track changes Lists should be IList<T> so that collections can be replaced with observables
Properties on sub-documents should be virtual as well
ACID = Atomicity, Consistency, Isolation, and Durability Under CAP theorem, adding 2PC reduces availability Note that a Couchbase Document often represents a Domain Aggregate very well
Developer power-up: essential Couchbase SDK patterns for getting started quickly – Couchbase Connect New York 2017