Podcasts about couchbase

In this episode of HR Heretics, Nolan Church and Kelli Dragovich interview Fidelma Butler, Chief People Officer at Couchbase, a NoSQL cloud database platform company. They talk about how to build effective L&D programs by defining clear leadership standards, focusing resources on senior leaders, and integrating learning into daily work instead of traditional training sessions.Fidelma emphasizes that L&D needs to be agile, continuously evolving, and solve actual business problems rather than existing as a separate "nice-to-have" function.*Email us your questions or topics for Kelli & Nolan: hrheretics@turpentine.coFor coaching and advising inquire at https://kellidragovich.com/HR Heretics is a podcast from Turpentine.Support HR Heretics Sponsors:Planful empowers teams just like yours to unlock the secrets of successful workforce planning. Use data-driven insights to develop accurate forecasts, close hiring gaps, and adjust talent acquisition plans collaboratively based on costs today and into the future. ✍️ Go to https://planful.com/heretics to see how you can transform your HR strategy.Metaview is the AI assistant for interviewing. Metaview completely removes the need for recruiters and hiring managers to take notes during interviews—because their AI is designed to take world-class interview notes for you. Team builders at companies like Brex, Hellofresh, and Quora say Metaview has changed the game—see the magic for yourself: https://www.metaview.ai/hereticsKEEP UP WITH Fidelma, NOLAN + KELLI ON LINKEDINFidelma: https://www.linkedin.com/in/fidelmabutler/Nolan: https://www.linkedin.com/in/nolan-church/Kelli: https://www.linkedin.com/in/kellidragovich/—LINK/S:Couchbase: https://www.couchbase.com/—TIMESTAMPS:(00:00) Intro(00:39) The L&D Challenge at Scale(01:19) Tailoring L&D to Your Organization(03:00) Defining Good Leadership(06:00) Creating Leadership Language and Framework(08:00) Why L&D Struggles - Making Squishy Things Tangible(10:00) Meeting People Where They Are(12:00) Optimizing L&D for Top Performers(16:32) Sponsor: Planful | Metaview(19:30) Engagement Surveys Done Right(25:00) When Surveys Conflict with Leadership Vision(28:00) Leaders Teaching Leaders(31:30) Coaching Strategy and Deployment(35:30) The Future of L&D Roles(39:30) Getting Career Development Wrong(42:30) The Promotion Obsession Problem(46:00) Wrap This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit hrheretics.substack.com

Here's the thing: we all heard Sundar Pichai say that the easy wins in AI have faded and that we may see fewer headline‑grabbing releases from the big players over the next year. That comment feels like a red flag for momentum, but I see it as a green light for action.  In this episode, I chatted with Rahul Pradhan, VP of Product and Strategy at Couchbase, about how teams can take advantage of this pause to move projects from simple experiments into solid, production‑ready services. I ask why many organizations hesitate to send their data to public AI endpoints. Rahul explains that when you've invested years building data platforms, handing over your proprietary information—even in encrypted form—can feel like handing over the keys to your kingdom. He walks us through how running models inside your security perimeter keeps private data safe and brings up model accuracy since you can tailor inputs and scrub out noise before it ever reaches the inference engine. Next, we tackle the question of stability. Companies often assume that the path to a live service is straightforward once a pilot works. Rahul warns that managing GPUs, orchestrating models, and serving them at low latency all require skill sets that live at the crossroads of ML engineering and traditional software development. We round out our conversation by shifting focus from tools to teams. Technology alone cannot carry an AI initiative. We need leaders who set a clear vision, data stewards who govern every data flow, and developers who feel as comfortable writing database queries as they define training pipelines. Rahul offers thoughtful advice on building that culture and shares examples of industries—healthcare, financial services, and retail—where the most far‑reaching uses of AI are taking root. If you're wondering how to push your proof of concept into a robust service that customers depend on, this episode is for you. I promise you'll come away with ideas you can apply tomorrow and a fresh view of why a little breathing room in AI releases can become the launch pad for your subsequent big success.    

Hoje o papo é sobre GraphQL no mobile. Neste episódio, conversamos sobre o histórico do GraphQL, desde os problemas que ele veio para resolver, até ecossistema, o que é (e o que não é) responsabilidade do GraphQL, vantagens e desvantagens do uso de GraphQL versus REST, e muito mais. Vem ver quem participou desse papo: André David, o host que já é o tradicional co-host Vinny Neves, Líder de Front-End na Alura Yago Oliveira, Coordenador de Conteúdo Técnico na Alura William Bezerra, Instrutor na Alura e Engenheiro Sênior no QuintoAndar

Fredrik talks to Dejan Milicic about software development - understanding, methods, and stories. We start by talking about encapsulation of knowledge and the essential software in organizations. Almost every organization should - it can be argued - be developing software that solves their unique problems, and yet so many outsource so much of their knowledge encapsulation. Oh, and we can never completely encapsulate our knowledge in code either, so all the more reason to keep people who actually know what the code does and why around. Dejan tells us about his way to Ravendb and a developer relations role - and how you can craft your own job, stepping suitably outside of your comfort zone along the way. We also talk about shortening attention spans, daring to dig down a bit and find out about the context of things. Like the second sentence of some oft-repeated quote. Prohibit bad things, but help automate doing good things and avoid doing the bad things completely. Dejan shares some database backstories - why would someone want to build one more database? Specifically, what lead to the creation of Ravendb? And the very strong opinions which have been built into it. Avoiding falling into marketing-driven development. After that, we drift into talking about processes and how we work. Every organization is unique - which strongly speaks against adapting the “best practices” and methodologies of others. Or keeping things completely the same for too long. Innovation is also about doing what other people are not doing. Why is concurrency still hard? The free lunch has been over for twenty years! Functional programming and immutability offer ways forward, why aren’t these concepts spreading even more and faster? We get right back to understanding more context when Dejan discusses how few of us seem to have understood, just for example, the L in SOLID. Dive deeper, read more, and you will find new things and come up with new ideas. Finally, Dejan would like to see software development becoming just a little bit more mathematical. So that things can be established, verified and built on in a different way. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We a re @kodsnack, @tobiashieta, @oferlund and @bjoreman on Twitter, have a page on Facebook and can be emailed at info@kodsnack.se if you want to write longer. We read everything we receive. If you enjoy Kodsnack we would love a review in iTunes! You can also support the podcast by buying us a coffee (or two!) through Ko-fi. Links Dejan Ravendb Informatics Domain-driven design Event sourcing Data is worthless - said in episode 601 Developer relations Nosql databases Jack of all trades Jimmy - who introduced Fredrik to Dejan at Øredev 2024 Hibernate Relational databases Oren Eini - creator of Ravendb Antipatterns n+1 Couchbase Scrum Agile software development The Toyota approach The Scrum guide Unison programming language - VC funded Dr. Dobb’s journal The free lunch is over Concurrency SOLID Liskov substitution principle Repositories on top Unitofwork are not a good idea - by Rob Conery Elm Titles A mathematician turned software developer Coding, but without deadline Saturated with software development Encapsulation of knowledge A bit surreal Accept people as they are There’s a second line Professional depression Prevented, not diagnosed The pipeline kind of thinking Frustration-driven development (You shouldn’t be) Punished for being successful The largest company of his or her life so far Optimized for maintaining the status quo Wash away all the context Manager of one The proverbial Jira Substantial content Methods of moving forward

In the modern tech landscape, AI is a constant topic of discussion. It's crucial to understand how applications are evolving alongside AI, especially considering the real-world challenges businesses face, such as the recent banking issues here in Malaysia.We speak with Chris Harris, Vice President of Global Field Engineering at Couchbase and our conversation will focus on several key areas:- The hurdles businesses encounter when adapting and integrating AI into their mobile applications.- The importance of data quality in these adaptive systems- The necessary safeguards to protect user privacy.Throughout our discussion, we'll also look at real-world use cases and examples of adaptive apps that have made a positive impact. Finally, we'll look ahead to the future of these technologies in the APAC region.

In der heutigen Folge von „Alles auf Aktien“ sprechen die Finanzjournalisten Laurin Meyer und Holger Zschäpitz über einen Grusel-Monat für Bitcoin, Blockbuster-Potenzial für Sanofi und einen Teufelskreislauf beim IT-Dienstleister Atos. Außerdem geht es um Rheinmetall, Hensoldt, BAE Systems, Porsche Holding SE, BYD, Nio, Tesla, Ford, General Motors, Accolade, ACV Auction, Affirm, Weave Communications, Western Digital, Wolfspeed, Liberty Media, Teladoc Health, Roku, Roblox, Grab, Anterix, Everquote, Asana, Couchbase, Sentinel One, Global Star, Indie Smeiconductor und Navitas Semiconductor. Hier findet Ihr den Link zur Stellenausschreibung: https://career.axelspringer.com/de/job/werkstudent-bei-alles-auf-aktien-social-media-community-management-1 Wir freuen uns an Feedback über aaa@welt.de. Ab sofort gibt es noch mehr "Alles auf Aktien" bei WELTplus und Apple Podcasts – inklusive aller Artikel der Hosts und AAA-Newsletter. Hier bei WELT: https://www.welt.de/podcasts/alles-auf-aktien/plus247399208/Boersen-Podcast-AAA-Bonus-Folgen-Jede-Woche-noch-mehr-Antworten-auf-Eure-Boersen-Fragen.html. Disclaimer: Die im Podcast besprochenen Aktien und Fonds stellen keine spezifischen Kauf- oder Anlage-Empfehlungen dar. Die Moderatoren und der Verlag haften nicht für etwaige Verluste, die aufgrund der Umsetzung der Gedanken oder Ideen entstehen. Hörtipps: Für alle, die noch mehr wissen wollen: Holger Zschäpitz können Sie jede Woche im Finanz- und Wirtschaftspodcast "Deffner&Zschäpitz" hören. Außerdem bei WELT: Im werktäglichen Podcast „Das bringt der Tag“ geben wir Ihnen im Gespräch mit WELT-Experten die wichtigsten Hintergrundinformationen zu einem politischen Top-Thema des Tages. +++ Werbung +++ Du möchtest mehr über unsere Werbepartner erfahren? Hier findest du alle Infos & Rabatte! https://linktr.ee/alles_auf_aktien Impressum: https://www.welt.de/services/article7893735/Impressum.html Datenschutz: https://www.welt.de/services/article157550705/Datenschutzerklaerung-WELT-DIGITAL.html

In this episode of Let's talk ABM, we speak to Lindsay Baggett, who heads up Account-based Marketing at Tanium. Now 24 months into her role at this leading security and system management company, she's built a formidable ABM engine. Previously, Lindsay led the Field Marketing and ABM efforts at companies including Couchbase and Gong. Watch this episode and learn about: Why ABM shouldn't be ‘random acts of marketing'! A focus on progress versus perfection Why defining ABM is so important What makes great Sales and Marketing alignment And much more… !

It was great to chat with Dipti Borkar, VP & GM at Microsoft at the Microsoft office in Mountain View. Here are the key points we discussed -- -- Dipti shared her impressive journey, from working with DB2 at IBM to NoSQL databases like Couchbase, and moving to the disaggregated stack with Presto and Spark -- She explained what Fabric is and how it is transforming the landscape of cloud databases, making them simpler and smarter -- We talked about the exciting announcements from this year's Microsoft Build, especially in the realm of Azure Data -- She shared insights from customers about the integration of Generative AI and data, and how Microsoft Azure Data is positioning itself to meet these evolving demands -- Dipti spoke about her initiatives to empower and mentor women in tech and open source, and how the industry can better support and uplift women in these fields -- Dipti shared key lessons from her leadership positions across various companies, and how she fosters innovation and collaboration within her teams at Microsoft -- We discussed her contributions to open source, particularly as Chairperson of the Linux Foundation / Presto Foundation community, and her vision for the future of open source in data technologies -- Dipti shared her predictions for the future of cloud databases and data management, and how she envisions Microsoft's role in shaping this future #data #ai #microsoft #theravitshow

Having listened to a number of Couchbase's earning calls, the company's CFO Greg Henry sits down with CJ to answer some in-depth questions, starting with the rationale behind Couchbase's non-standard fiscal year and the advantages of it. He then delves into his experience of transforming a traditional enterprise subscription model into a managed service consumption business. The conversation covers Couchbase's focus on Annual Recurring Revenue (ARR) as their North Star metric and the art and science of multi-year deals. They discuss how best to interact with sell-side analysts, how callbacks after earnings calls work, and how to manage relationships on the buy side. Greg also reflects on his time at General Electric during its heyday, offering insights into the culture and frameworks that shaped his approach to business today before talking about Matt Cain's framework for Couchbase and how it enables function. Tune in to hear all this and the story of how Greg lost $1 million of operating profit.If you're looking for an ERP head to NetSuite: https://netsuite.com/metrics and get a customized KPI checklist.—SPONSORS:Mercury is the fintech ambitious companies use for banking and all their financial workflows. With a powerful bank account at the center of their operations, companies can make better financial decisions and ensure that every dollar spent aligns with company priorities. That's why over 100K startups choose Mercury to confidently run all their financial operations with the precision, control, and focus they need to operate at their best. Learn more at mercury.com.Mercury is a financial technology company, not a bank. Banking services provided by Choice Financial Group and Evolve Bank & Trust®; Members FDIC.NetSuite provides financial software for all your business needs. More than 37,000 thousand companies have already upgraded to NetSuite, gaining visibility and control over their financials, inventory, HR, eCommerce, and more. If you're looking for an ERP platform ✅ NetSuite: https://netsuite.com/metrics and get a customized KPI checklist. Maxio is the only billing and financial operations platform that was purpose built for B2B SaaS. They're helping SaaS finance teams automate billing and revenue recognition, manage collections and payments, and put together investor grade reporting packages.

Design Documents und Request for Comments (RFCs): Die Engineering Art der PlanungsphaseWir alle haben schon mal von einer Planungsphase gehört, um ein neues Projekt zu starten, und denken dabei an aufgeblasene Prozesse und lange Wasserfall-Diagramme. Und das Engineering-Team fragt sich oft: Wann kommen wir endlich mal zu den Details?Da kommen die Begriffe Design Documents und Request for Comments (RFCs) ins Spiel.Das doofe nur … Jemand muss diese Dokumente auch schreiben.Und da sind wir bei gleich zwei von Andy's Lieblingsthemen: Schreiben und Design Docs.Wir klären, wozu Design Documents eigentlich gut sind, worauf es ankommt, wo der Unterschied zu RFCs ist, ob das ganze nicht ein riesiger Wasserkopf ist, um einfach Dinge auf die Straße zu bringen und welche Kultur das ganze benötigt.Viel Spaß.Bonus: Wer schreibt, der bleibt.Das schnelle Feedback zur Episode:

Are AI hallucinations undermining trust in machine learning, and can Retrieval-Augmented Generation (RAG) offer a solution? As we invite Rahul Pradhan, VP of Product and Strategy at Couchbase, to our podcast, we delve into the fascinating yet challenging issue of AI hallucinations—situations where AI systems generate plausible but factually incorrect content. This phenomenon poses risks to AI's reliability and threatens its adoption across critical sectors like healthcare and legal industries, where precision is paramount. In this episode, Rahul will explain how these hallucinations occur in AI models that operate on probability, often simulating understanding without genuine comprehension. The consequences? A potential erosion of trust in automated systems is a barrier that is particularly significant in domains where the stakes are high, and errors can have profound implications. But fear not, there's a beacon of hope on the horizon—Retrieval-Augmented Generation (RAG).  Rahul will discuss how RAG integrates a retrieval component that pulls real-time, relevant data before generating responses, thereby grounding AI outputs in reality and significantly mitigating the risk of hallucinations. He will also show how Couchbase's innovative data management capabilities enable this technology by combining operational and training data to enhance accuracy and relevance. Moreover, Rahul will explore RAG's broader implications. From enhancing personalization in content generation to facilitating sophisticated decision-making across various industries, RAG stands out as a pivotal innovation in promoting more transparent, accountable, and responsible AI applications. Join us as we navigate the labyrinth of AI hallucinations and the transformative power of the Retrieval-Augmented Generation. How might this technology reshape the landscape of AI deployment across different sectors? After listening, we eagerly await your thoughts on whether RAG could be the key to building more trustworthy AI systems.  

This episode of the Generative AI podcast features Mark from Couchbase, a company with a long history in database technology, focusing on its latest advancements in edge computing capabilities. Mark, the director of product marketing, discusses the significance of Couchbase's move into on-device vector storage. This development represents a significant leap in enabling AI applications directly on mobile and IoT devices without compromising on performance or resource efficiency. Throughout the conversation, Mark highlights how this technology is set to change the landscape of data processing by allowing for more personalized and context-aware applications across various sectors, including gaming and healthcare. The discussion also covers the technical aspects of Couchbase's approach to embedding databases in devices, synchronization techniques, and the potential use cases enabled by this innovation. Listen to this episode for a detailed exploration of Couchbase's contributions to edge computing and the broader implications of on-device vector storage for the future of AI and database technology. Whether you're involved in software development, interested in the technicalities of edge computing, or looking into the future of AI applications, this episode provides a clear understanding of Couchbase's latest technological breakthroughs.

It's easy to jump onto a existing tech community, it's challenging to build a new community. Tommy Berry is joining us to talk about the challenges and success for strategies when building a new community. Tommy went to Couchbase and won Marketer of the year while building a new community and brand presence !

Este es mi primer episodio de "The Startupeable Show" y no podría estar más agradecido de empezar con un invitado tan increíble.  Hoy conversé con Kevin Efrusy en el programa. Kevin se unió a Accel Partners en 2003 y fue el principal inversionista en empresas como Groupon, Couchbase y Facebook, que es probablemente una de las mejores inversiones  de todos los tiempos. La historia de cómo aprovechó una “mente preparada” para buscar y convencer a Mark Zuckerberg en 2005 de que aceptara el acuerdo de Accel le valió una seccion en el libro de Sebastian Mallaby 'The Power Law'.Kevin también puso en marcha las iniciativas de Accel en América Latina, que dieron lugar a inversiones en Despegar, Gympass, Nuvemshop y Quinto Andar. Ha sido un importante defensor del ecosistema de startups de Latinoamérica desde sus inicios, invirtiendo personalmente en dos de los principales fondos de riesgo de la región, Kaszek y Monashees, y ayudando a muchos otros fundadores.Para obtener lo mejor de las entrevistas:

Amazon announced that they will be using Nvidia's NVSwitch to create new rackscale AI platforms. This allows customers to use Nvidia technology like Grace Hopper or build something using AWS Nitro DPUs and Elastic Fabric Adapaters. That last combination doesn't use InfiniBand and moves to Ethernet. Two new chips are coming out from the Amazon labs. The first is Graviton4, the latest generation of Arm processor. Graviton4 has 50% more cores and 75% more memory bandwidth. This version of Graviton is based on the Demeter Neoverse V2 core. On the AI front Amazon also announced the next revision of their AI acceleration chip, Trainium2. This update has a 4x performance increase from the first generation and allows for liquid cooling. Trainium2 is designed to be deployed in clusters of 16 chips. In the data space, AWS made news with the GA of Bedrock, which enables customers to run foundational ML models from companies like Anthropic, Meta, and of course AWS itself. But many companies are worried about hallucination and want to include their own data in these models. That's what AWS is delivering with Guardrails, and what AWS partners are leaning into as well. This and more on this week's Gestalt IT Rundown. 0:00 - Welcome to the Rundown 1:18 - DAOS Foundation Launched for Object Storage 4:57 - Autonomous Purple Team annouced by Skyhawk at AWS re:Invent 8:26 - Couchbase's Capella Columnar Service Revealed 10:59 - Hackers Were Inside NXP For Two Years Before Detection 14:47 - AWS re:Invent Announcements 15:26 - NVSwitch For AI Nodes 20:46 - ARM V2 for Graviton4 and Trainium2 25:22 - AWS Guardrails for Bedrock 30:10 - The Weeks Ahead 33:10 - Thanks for Watching Follow our Hosts on Social Media Tom Hollingsworth: ⁠⁠https://www.twitter.com/NetworkingNerd⁠⁠ Stephen Foskett: ⁠⁠https://www.twitter.com/SFoskett⁠⁠  Follow Gestalt IT Website: ⁠⁠https://www.GestaltIT.com/⁠⁠ Twitter: ⁠⁠https://www.twitter.com/GestaltIT⁠⁠ LinkedIn: ⁠⁠https://www.linkedin.com/company/Gestalt-IT Tags: #Rundown, AI, #AWSreinvent, #AWS, #Storage, @SkyhawkCloudSec, @Couchbase, #Capella, #Data, #Security, #NXP, #China, @AWS, @NVIDIA, #GraceHopper, @Arm, #Graviton4, #Bedrock, @NetworkingNerd, @SFoskett, @GestaltIT,

Jeff Morris, VP of Product & Solutions Marketing at Couchbase, joins Corey on Screaming in the Cloud to discuss Couchbase's new columnar data store functionality, specific use cases for columnar data stores, and why AI gets better when it communicates with a cleaner pool of data. Jeff shares how more responsive databases could allow businesses like Dominos and United Airlines to create hyper-personalized experiences for their customers by utilizing more responsive databases. Jeff dives into the linked future of AI and data, and Corey learns about Couchbase's plans for the re:Invent conference. If you're attending re:Invent, you can visit Couchbase at booth 1095.About JeffJeff Morris is VP Product & Solutions Marketing at Couchbase (NASDAQ: BASE), a cloud database platform company that 30% of the Fortune 100 depend on.Links Referenced:Couchbase: https://www.couchbase.com/TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. This promoted guest episode of Screaming in the Cloud is brought to us by our friends at Couchbase. Also brought to us by Couchbase is today's victim, for lack of a better term. Jeff Morris is their VP of Product and Solutions Marketing. Jeff, thank you for joining me.Jeff: Thanks for having me, Corey, even though I guess I paid for it.Corey: Exactly. It's always great to say thank you when people give you things. I learned this from a very early age, and the only people who didn't were rude children and turned into worse adults.Jeff: Exactly.Corey: So, you are effectively announcing something new today, and I always get worried when a database company says that because sometimes it's a license that is going to upset people, sometimes it's dyed so deep in the wool of generative AI that, “Oh, we're now supporting vectors or whatnot.” Well, most of us don't know what that means.Jeff: Right.Corey: Fortunately, I don't believe that's what you're doing today. What have you got for us?Jeff: So, you're right. It's—well, what I'm doing is, we're announcing new stuff inside of Couchbase and helping Couchbase expand its market footprint, but we're not really moving away from our sweet spot, either, right? We like building—or being the database platform underneath applications. So, push us on the operational side of the operational versus analytic, kind of, database divide. But we are announcing a columnar data store inside of the Couchbase platform so that we can build bigger, better, stronger analytic functionality to feed the applications that we're supporting with our customers.Corey: Now, I feel like I should ask a question around what a columnar data store is because my first encounter with the term was when I had a very early client for AWS bill optimization when I was doing this independently, and I was asking them the… polite question of, “Why do you have 283 billion objects in a single S3 bucket? That is atypical and kind of terrifying.” And their answer was, “Oh, we built our own columnar data store on top of S3. This might not have been the best approach.” It's like, “I'm going to stop you there. With no further information, I can almost guarantee you that it was not.” But what is a columnar data store?Jeff: Well, let's start with the, everybody loves more data and everybody loves to count more things, right, but a columnar data store allows you to expedite the kind of question that you ask of the data itself by not having to look at every single row of the data while you go through it. You can say, if you know you're only looking for data that's inside of California, you just look at the column value of find me everything in California and then I'll pick all of those records to analyze. So, it gives you a faster way to go through the data while you're trying to gather it up and perform aggregations against it.Corey: It seems like it's one of those, “Well, that doesn't sound hard,” type of things, when you're thinking about it the way that I do, in terms of a database being more or less a medium to large size Excel spreadsheet. But I have it on good faith from all the customer environments. I've worked with that no, no, there are data stores that span even larger than that, which is, you know, one of those sad realities of the world. And everything at scale begins to be a heck of a lot harder. I've seen some of the value that this stuff offers and I can definitely understand a few different workloads in which case that's going to be super handy. What are you targeting specifically? Or is this one of those areas where you're going to learn from your customers?Jeff: Well, we've had analytic functionality inside the platform. It just, at the size and scale customers actually wanted to roam through the data, we weren't supporting that that much. So, we'll expand that particular footprint, it'll give us better integration capabilities with external systems, or better access to things in your bucket. But the use case problem is, I think, going to be driven by what new modern application requirements are going to be. You're going to need, we call it hyper-personalization because we tend to cater to B2C-style applications, things with a lot of account profiles built into them.So, you look at account profile, and you're like, “Oh, well Jeff likes blue, so sell him blue stuff.” And that's a great current level personalization, but with a new analytic engine against this, you can maybe start aggregating all the inventory information that you might have of all the blue stuff that you want to sell me and do that in real-time, so I'm getting better recommendations, better offers as I'm shopping on your site or looking at my phone and, you know, looking for the next thing I want to buy.Corey: I'm sure there's massive amounts of work that goes into these hyper-personalization stories. The problem is that the only time they really rise to our notice is when they fail hilariously. Like, you just bought a TV, would you like to buy another? Now statistically, you are likelier to buy a second TV right after you buy one, but for someone who just, “Well, I'm replacing my living room TV after ten years,” it feels ridiculous. Or when you buy a whole bunch of nails and they don't suggest, “Would you like to also perhaps buy a hammer?”It's one of those areas where it just seems like a human putting thought into this could make some sense. But I've seen some of the stuff that can come out of systems like this and it can be incredible. I also personally tend to bias towards use cases that are less, here's how to convince you to buy more things and start aiming in a bunch of other different directions where it starts meeting emerging use cases or changing situations rapidly, more rapidly than a human can in some cases. The world has, for better or worse, gotten an awful lot faster over the last few decades.Jeff: Yeah. And think of it in terms of how responsive can I be at any given moment. And so, let's pick on one of the more recent interesting failures that has popped up. I'm a Giants fan, San Francisco Giants fan, so I'll pick on the Dodgers. The Dodgers during the baseball playoffs, Clayton Kershaw—three-time MVP, Cy Young Award winner, great, great pitcher—had a first-inning meltdown of colossal magnitude: gave up 11 runs in the first inning to the Diamondbacks.Well, my customer Domino's Pizza could end up—well, let's shift the focus of our marketing. We—you know, the Dodgers are the best team in baseball this year in the National League—let's focus our attention there, but with that meltdown, let's pivot to Arizona and focus on our market in Phoenix. And they could do that within minutes or seconds, even, with the kinds of capabilities that we're coming up with here so that they can make better offers to that new environment and also do the decision intelligence behind it. Like, do I have enough dough to make a bigger offer in that big market? Do I have enough drivers or do I have to go and spin out and get one of the other food delivery folks—UberEats, or something like that—to jump on board with me and partner up on this kind of system?It's that responsiveness in real, real-time, right, that's always been kind of the conundrum between applications and analytics. You get an analytic insight, but it takes you an hour or a day to incorporate that into what the application is doing. This is intended to make all of that stuff go faster. And of course, when we start to talk about things in AI, right, AI is going to expect real-time responsiveness as best you can make it.Corey: I figure we have to talk about AI. That is a technology that has absolutely sprung to the absolute peak of the hype curve over the past year. OpenAI released Chat-Gippity, either late last year or early this year and suddenly every company seems to be falling all over itself to rebrand itself as an AI company, where, “We've been working on this for decades,” they say, right before they announce something that very clearly was crash-developed in six months. And every company is trying to drape themselves in the mantle of AI. And I don't want to sound like I'm a doubter here. I'm like most fans; I see an awful lot of value here. But I am curious to get your take on what do you think is real and what do you think is not in the current hype environment.Jeff: So yeah, I love that. I think there's a number of things that are, you know, are real is, it's not going away. It is going to continue to evolve and get better and better and better. One of my analyst friends came up with the notion that the exercise of generative AI, it's imprecise, so it gives you similarity things, and that's actually an improvement, in many cases, over the precision of a database. Databases, a transaction either works or it doesn't. It has failover or it doesn't, when—Corey: It's ideally deterministic when you ask it a question—Jeff: Yes.Corey: —the same question a second time, assuming it's not time-bound—Jeff: Gives you the right answer.Corey: Yeah, the sa—or at least the same answer.Jeff: The same answer. And your gen AI may not. So, that's a part of the oddity of the hype. But then it also helps me kind of feed our storyline of if you're going to try and make Gen AI closer and more accurate, you need a clean pool of data that you're dealing with, even though you've got probably—your previous design was such that you would use a relational database for transactions, a document database for your user profiles, you'd probably attach your website to a caching database because you needed speed and a lot of concurrency. Well, now you got three different databases there that you're operating.And if you're feeding data from each of those databases back to AI, one of them might be wrong or one of them might confuse the AI, yet how are you going to know? The complexity level is going to become, like, exponential. So, our premise is, because we're a multi-modal database that incorporates in-memory speed and documents and search and transactions and the like, if you start with a cleaner pool of data, you'll have less complexity that you're offering to your AI system and therefore you can steer it into becoming more accurate in its response. And then, of course, all the data that we're dealing with is on mobile, right? Data is created there for, let's say, your account profile, and then it's also consumed there because that's what people are using as their application interface of choice.So, you also want to have mobile interactivity and synchronization and local storage, kind of, capabilities built in there. So, those are kind of, you know, a couple of the principles that we're looking at of, you know, JSON is going to be a great format for it regardless of what happens; complexity is kind of the enemy of AI, so you don't want to go there; and mobility is going to be an absolute requirement. And then related to this particular announcement, large-scale aggregation is going to be a requirement to help feed the application. There's always going to be some other bigger calculation that you're going to want to do relatively in real time and feed it back to your users or the AI system that's helping them out.Corey: I think that that is a much more nuanced use case than a lot of the stuff that's grabbing customer attentions where you effectively have the Chat-Gippity story of it being an incredible parrot. Where I have run into trouble with the generative story has been people putting the thing that the robot that's magic and from the future has come up with off the cuff and just hurling that out into the universe under their own name without any human review, and that's fine sometimes sure, but it does get it hilariously wrong at some points. And the idea of sending something out under my name that has not been at least reviewed by me if not actually authored by me, is abhorrent. I mean, I review even the transactional, “Yes, you have successfully subscribed,” or, “Sorry to see you go,” email confirmations on stuff because there's an implicit, “Hugs and puppies, love Corey,” at the end of everything that goes out under my name.Jeff: Right.Corey: But I've gotten a barrage of terrible sales emails and companies that are trying to put the cart before the horse where either the, “Support rep,” quote-unquote, that I'm speaking to in the chat is an AI system or else needs immediate medical attention because there's something going on that needs assistance.Jeff: Yeah, they just don't understand.Corey: Right. And most big enterprise stories that I've heard so far that have come to light have been around the form of, “We get to fire most of our customer service staff,” an outcome that basically no one sensible wants. That is less compelling than a lot of the individualized consumer use cases. I love asking it, “Here's a blog post I wrote. Give me ten title options.” And I'll usually take one of them—one of them is usually not half bad and then I can modify it slightly.Jeff: And you'll change four words in it. Yeah.Corey: Yeah, exactly. That's a bit of a different use case.Jeff: It's been an interesting—even as we've all become familiar—or at least junior prompt engineers, right—is, your information is only going to be as good as you feed the AI system—the return is only going to be as good—so you're going to want to refine that kind of conversation. Now, we're not trying to end up replacing the content that gets produced or the writing of all kinds of pros, other than we do have a code generator that works inside of our environment called Capella iQ that talks to ChatGPT, but we try and put guardrails on that too, right, as always make sure that it's talking in terms of the context of Couchbase rather than, “Where's Taylor Swift this week,” which I don't want it to answer because I don't want to spend GPT money to answer that question for you.Corey: And it might not know the right answer, but it might very well spit out something that sounds plausible.Jeff: Exactly. But I think the kinds of applications that we're steering ourselves toward can be helped along by the Gen AI systems, but I don't expect all my customers are going to be writing automatic blog post generation kinds of applications. I think what we're ultimately trying to do is facilitate interactions in a way that we haven't dreamt of yet, right? One of them might be if I've opted into to loyalty programs, like my United account and my American Express account—Corey: That feels very targeted at my lifestyle as well, so please, continue.Jeff: Exactly, right? And so, what I really want the system to do is for Amex to reward me when I hit 1k status on United while I'm on the flight and you know, have the flight attendant come up and be like, “Hey, you did it. Either, here's a free upgrade from American Express”—that would be hyper-personalization because you booked your plane ticket with it, but they also happen to know or they cross-consumed information that I've opted into.Corey: I've seen them congratulate people for hitting a million miles flown mid-flight, but that's clearly something that they've been tracking and happens a heck of a lot less frequently. This is how you start scaling that experience.Jeff: Yes. But that happened because American Airlines was always watching because that was an American Airlines ad ages ago, right, but the same principle holds true. But I think there's going to be a lot more of these: how much information am I actually allowing to be shared amongst the, call it loyalty programs, but the data sources that I've opted into. And my God, there's hundreds of them that I've personally opted into, whether I like it or not because everybody needs my email address, kind of like what you were describing earlier.Corey: A point that I have that I think agrees largely with your point is that few things to me are more frustrating than what I'm signing up, for example, oh, I don't know, an AWS even—gee, I can't imagine there's anything like that going on this week—and I have to fill out an entire form that always asked me the same questions: how big my company is, whether we have multiple workloads on, what industry we're in. And no matter what I put into that, first, it never remembers me for the next time, which is frustrating in its own right, but two, no matter what I put in to fill that thing out, the email I get does not change as a result. At one point, I said, all right—I'm picking randomly—“I am a venture capitalist based in Sweden,” and I got nothing that is differentiated from the other normal stuff I get tied to my account because I use a special email address for those things, sometimes just to see what happens. And no, if you're going to make me jump through the hoops to give you the data, at least use it to make my experience better. It feels like I'm asking for the moon here, but I shouldn't be.Jeff: Yes. [we need 00:16:19] to make your experience better and say, you know, “Here's four companies in Malmo that you ought to be talking to. And they happen to be here at the AWS event and you can go find them because their booth is here, here, and here.” That kind of immediate responsiveness could be facilitated, and to our point, ought to be facilitated. It's exactly like that kind of thing is, use the data in real-time.I was talking to somebody else today that was discussing that most data, right, becomes stale and unvaluable, like, 50% of the data, its value goes to zero after about a day. And some of it is stale after about an hour. So, if you can end up closing that responsiveness gap that we were describing—and this is kind of what this columnar service inside of Capella is going to be like—is react in real-time with real-time calculation and real-time look-up and real-time—find out how you might apply that new piece of information right now and then give it back to the consumer or the user right now.Corey: So, Couchbase takes a few different forms. I should probably, at least for those who are not steeped in the world of exotic forms of database, I always like making these conversations more accessible to folks who are not necessarily up to speed. Personally, I tend to misuse anything as a database, if I can hold it just the wrong way.Jeff: The wrong way. I've caught that about you.Corey: Yeah, it's—everything is a database if you hold it wrong. But you folks have a few different options: you have a self-managed commercial offering; you're an open-source project, so I can go ahead and run it on my own infrastructure however I want; and you have Capella, which is Couchbase as a service. And all of those are useful and have their points, and I'm sure I'm missing at least one or two along the way. But do you find that the columnar use case is going to disproportionately benefit folks using Capella in ways that the self-hosted version would not be as useful for, or is this functionality already available in other expressions of Couchbase?Jeff: It's not already available in other expressions, although there is analytic functionality in the self-managed version of Couchbase. But it's, as I've mentioned I think earlier, it's just not as scalable or as really real-time as far as we're thinking. So, it's going to—yes, it's going to benefit the database as a service deployments of Couchbase available on your favorite three clouds, and still interoperable with environments that you might self-manage and self-host. So, there could be even use cases where our development team or your development team builds in AWS using the cloud-oriented features, but is still ultimately deploying and hosting and managing a self-managed environment. You could still do all of that. So, there's still a great interplay and interoperability amongst our different deployment options.But the fun part, I think, about this is not only is it going to help the Capella user, there's a lot of other things inside Couchbase that help address the developers' penchant for trading zero-cost for degrees of complexity that you're willing to accept because you want everything to be free and open-source. And Couchbase is my fifth open-source company in my background, so I'm well, well versed in the nuances of what open-source developers are seeking. But what makes Couchbase—you know, its origin story really cool too, though, is it's the peanut butter and chocolate marriage of memcached and the people behind that and membase and CouchDB from [Couch One 00:19:54]. So, I can't think of that many—maybe Red Hat—project and companies that formed up by merging two complementary open-source projects. So, we took the scale and—Corey: You have OpenTelemetry, I think, that did that once, but that—you see occasional mergers, but it's very far from common.Jeff: But it's very, very infrequent. But what that made the Couchbase people end up doing is make a platform that will scale, make a data design that you can auto partition anywhere, anytime, and then build independently scalable services on top of that, one for SQL++, the query language. Anyone who knows SQL will be able to write something in Couchbase immediately. And I've got this AI Automator, iQ, that makes it even easier; you just say, “Write me a SQL++ query that does this,” and it'll do that. But then we added full-text search, we added eventing so you can stream data, we added the analytics capability originally and now we're enhancing it, and use JSON as our kind of universal data format so that we can trade data with applications really easily.So, it's a cool design to start with, and then in the cloud, we're steering towards things like making your entry point and using our database as a service—Capella—really, really, really inexpensive so that you get that same robustness of functionality, as well as the easy cost of entry that today's developers want. And it's my analyst friends that keep telling me the cloud is where the markets going to go, so we're steering ourselves towards that hockey puck location.Corey: I frequently remark that the role of the DBA might not be vanishing, but it's definitely changing, especially since the last time I counted, if you hold them and use as directed, AWS has something on the order of 14 distinct managed database offerings. Some are general purpose, some are purpose-built, and if this trend keeps up, in a decade, the DBA role is going to be determining which of its 40 databases is going to be the right fit for a given workload. That seems to be the counter-approach to a general-purpose database that works across the board. Clearly you folks have opinions on this. Where do you land?Jeff: Oh, so absolutely. There's the product that is a suite of capabilities—or that are individual capabilities—and then there's ones that are, in my case, kind of multi-model and do lots of things at once. I think historically, you'll recognize—because this is—let's pick on your phone—the same holds true for, you know, your phone used to be a watch, used to be a Palm Pilot, used to be a StarTAC telephone, and your calendar application, your day planner all at the same time. Well, it's not anymore. Technology converges upon itself; it's kind of a historical truism.And the database technologies are going to end up doing that—or continue to do that, even right now. So, that notion that—it's a ten-year-old notion of use a purpose-built database for that particular workload. Maybe sometimes in extreme cases that is the appropriate thing, but in more cases than not right now, if you need transactions when you need them, that's fine, I can do that. You don't necessarily need Aurora or RDS or Postgres to do that. But when you need search and geolocation, I support that too, so you don't need Elastic. And then when you need caching and everything, you don't need ElastiCache; it's all built-in.So, that multi-model notion of operate on the same pool of data, it's a lot less complex for your developers, they can code faster and better and more cleanly, debugging is significantly easier. As I mentioned, SQL++ is our language. It's basically SQL syntax for JSON. We're a reference implementation of this language, along with—[AsteriskDB 00:23:42] is one of them, and actually, the original author of that language also wrote DynamoDB's PartiQL.So, it's a common language that you wouldn't necessarily imagine, but the ease of entry in all of this, I think, is still going to be a driving goal for people. The old people like me and you are running around worrying about, am I going to get a particular, really specific feature out of the full-text search environment, or the other one that I pick on now is, “Am I going to need a vector database, too?” And the answer to me is no, right? There's going—you know, the database vendors like ourselves—and like Mongo has announced and a whole bunch of other NoSQL vendors—we're going to support that. It's going to be just another mode, and you get better bang for your buck when you've got more modes than a single one at a time.Corey: The consensus opinion that's emerging is very much across the board that vector is a feature, not a database type.Jeff: Not a category, yeah. Me too. And yeah, we're well on board with that notion, as well. And then like I said earlier, the JSON as a vehicle to give you all of that versatility is great, right? You can have vector information inside a JSON document, you can have time series information in the document, you could have graph node locations and ID numbers in a JSON array, so you don't need index-free adjacency or some of the other cleverness that some of my former employers have done. It really is all converging upon itself and hopefully everybody starts to realize that you can clean up and simplify your architectures as you look ahead, so that you do—if you're going to build AI-powered applications—feed it clean data, right? You're going to be better off.Corey: So, this episode is being recorded in advance, thankfully, but it's going to release the first day of re:Invent. What are you folks doing at the show, for those who are either there and for some reason, listening to a podcast rather than going to getting marketed to by a variety of different pitches that all mention AI or might even be watching from home and trying to figure out what to make of it?Jeff: Right. So, of course we have a booth, and my notes don't have in front of me what our booth number is, but you'll see it on the signs in the airport. So, we'll have a presence there, we'll have an executive briefing room available, so we can schedule time with anyone who wants to come talk to us. We'll be showing not only the capabilities that we're offering here, we'll show off Capella iQ, our coding assistant, okay—so yeah, we're on the AI hype band—but we'll also be showing things like our mobile sync capability where my phone and your phone can synchronize data amongst themselves without having to actually have a live connection to the internet. So, long as we're on the same network locally within the Venetian's network, we have an app that we have people download from the Apple Store and then it's a color synchronization app or picture synchronization app.So, you tap it, and it changes on my screen and I tap it and it changes on your screen, and we'll have, I don't know, as many people who are around standing there, synchronizing, what, maybe 50 phones at a time. It's actually a pretty slick demonstration of why you might want a database that's not only in the cloud but operates around the cloud, operates mobile-ly, operates—you know, can connect and disconnect to your networks. It's a pretty neat scenario. So, we'll be showing a bunch of cool technical stuff as well as talking about the things that we're discussing right now.Corey: I will say you're putting an awful lot of faith in conductivity working at re:Invent, be it WiFi or the cellular network. I know that both of those have bitten me in various ways over the years. But I wish you the best on it. I think it's going to be an interesting show based upon everything I've heard in the run-up to it. I'm just glad it's here.Jeff: Now, this is the cool part about what I'm talking about, though. The cool part about what I'm talking about is we can set up our own wireless network in our booth, and we still—you'd have to go to the app store to get this application, but once there, I can have you switch over to my local network and play around on it and I can sync the stuff right there and have confidence that in my local network that's in my booth, the system's working. I think that's going to be ultimately our design there because oh my gosh, yes, I have a hundred stories about connectivity and someone blowing a demo because they're yanking on a cable behind the pulpit, right?Corey: I always build in a—and assuming there's no connectivity, how can I fake my demos, just because it's—I've only had to do it once, but you wind up planning in advance when you start doing a talk to a large enough or influential enough audience where you want things to go right.Jeff: There's a delightful acceptance right now of recorded videos and demonstrations that people sort of accept that way because of exactly all this. And I'm sure we'll be showing that in our booth there too.Corey: Given the non-deterministic nature of generative AI, I'm sort of surprised whenever someone hasn't mocked the demo in advance, just because yeah, gives the right answer in the rehearsal, but every once in a while, it gets completely unglued.Jeff: Yes, and we see it pretty regularly. So, the emergence of clever and good prompt engineering is going to be a big skill for people. And hopefully, you know, everybody's going to figure out how to pass it along to their peers.Corey: Excellent. We'll put links to all this in the show notes, and I look forward to seeing how well this works out for you. Best of luck at the show and thanks for speaking with me. I appreciate it.Jeff: Yeah, Corey. We appreciate the support, and I think the show is going to be very strong for us as well. And thanks for having me here.Corey: Always a pleasure. Jeff Morris, VP of Product and Solutions Marketing at Couchbase. This episode has been brought to us by our friends at Couchbase. And I'm Cloud Economist Corey Quinn. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry comment, but if you want to remain happy, I wouldn't ask that podcast platform what database they're using. No one likes the answer to those things.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Laurent Doguin, Director of Developer Relations & Strategy at Couchbase, joins Corey on Screaming in the Cloud to talk about the work that Couchbase is doing in the world of databases and developer relations, as well as the role of AI in their industry and beyond. Together, Corey and Laurent discuss Laurent's many different roles throughout his career including what made him want to come back to a role at Couchbase after stepping away for 5 years. Corey and Laurent dig deep on how Couchbase has grown in recent years and how it's using artificial intelligence to offer an even better experience to the end user.About LaurentLaurent Doguin is Director of Developer Relations & Strategy at Couchbase (NASDAQ: BASE), a cloud database platform company that 30% of the Fortune 100 depend on.Links Referenced: Couchbase: https://couchbase.com XKCD #927: https://xkcd.com/927/ dbdb.io: https://dbdb.io DB-Engines: https://db-engines.com/en/ Twitter: https://twitter.com/ldoguin LinkedIn: https://www.linkedin.com/in/ldoguin/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Are you navigating the complex web of API management, microservices, and Kubernetes in your organization? Solo.io is here to be your guide to connectivity in the cloud-native universe!Solo.io, the powerhouse behind Istio, is revolutionizing cloud-native application networking. They brought you Gloo Gateway, the lightweight and ultra-fast gateway built for modern API management, and Gloo Mesh Core, a necessary step to secure, support, and operate your Istio environment.Why struggle with the nuts and bolts of infrastructure when you can focus on what truly matters - your application. Solo.io's got your back with networking for applications, not infrastructure. Embrace zero trust security, GitOps automation, and seamless multi-cloud networking, all with Solo.io.And here's the real game-changer: a common interface for every connection, in every direction, all with one API. It's the future of connectivity, and it's called Gloo by Solo.io.DevOps and Platform Engineers, your journey to a seamless cloud-native experience starts here. Visit solo.io/screaminginthecloud today and level up your networking game.Corey: Welcome to Screaming in the Cloud, I'm Corey Quinn. This promoted guest episode is brought to us by our friends at Couchbase. And before we start talking about Couchbase, I would rather talk about not being at Couchbase. Laurent Doguin is the Director of Developer Relations and Strategy at Couchbase. First, Laurent, thank you for joining me.Laurent: Thanks for having me. It's a pleasure to be here.Corey: So, what I find interesting is that this is your second time at Couchbase, where you were a developer advocate there for a couple of years, then you had five years of, we'll call it wilderness I suppose, and then you return to be the Director of Developer Relations. Which also ties into my personal working thesis of, the best way to get promoted at a lot of companies is to leave and then come back. But what caused you to decide, all right, I'm going to go work somewhere else? And what made you come back?Laurent: So, I've joined Couchbase in 2014. Spent about two or three years as a DA. And during those three years as a developer advocate, I've been advocating SQL database and I—at the time, it was mostly DBAs and ops I was talking to. And DBA and ops are, well, recent, modern ops are writing code, but they were not the people I wanted to talk to you when I was a developer advocate. I came from a background of developer, I've been a platform engineer for an enterprise content management company. I was writing code all day.And when I came to Couchbase, I realized I was mostly talking about Docker and Kubernetes, which is still cool, but not what I wanted to do. I wanted to talk about developers, how they use database to be better app, how they use key-value, and those weird thing like MapReduce. At the time, MapReduce was still, like, a weird thing for a lot of people, and probably still is because now everybody's doing SQL. So, that's what I wanted to talk about. I wanted to… engage with people identify with, really. And so, didn't happen. Left. Built a Platform as a Service company called Clever Cloud. They started about four or five years before I joined. We went from seven people to thirty-one LFs, fully bootstrapped, no VC. That's an interesting way to build a company in this age.Corey: Very hard to do because it takes a lot of upfront investment to build software, but you can sort of subsidize that via services, which is what we've done here in some respects. But yeah, that's a hard road to walk.Laurent: That's the model we had—and especially when your competition is AWS or Azure or GCP, so that was interesting. So entrepreneurship, it's not for everyone. I did my four years there and then I realized, maybe I'm going to do something else. I met my former colleagues of Couchbase at a software conference called Devoxx, in France, and they told me, “Well, there's a new sheriff in town. You should come back and talk to us. It's all about developers, we are repositioning, rehandling the way we do marketing at Couchbase. Why not have a conversation with our new CMO, John Kreisa?”And I said, “Well, I mean, I don't have anything to do. I actually built a brewery during that past year with some friends. That was great, but that's not going to feed me or anything. So yeah, let's have a conversation about work.” And so, I talked to John, I talked to a bunch of other people, and I realized [unintelligible 00:03:51], he actually changed, like, there was a—they were purposely going [against 00:03:55] developer, talking to developer. And that was not the case, necessarily, five, six years before that.So, that's why I came back. The product is still amazing, the people are still amazing. It was interesting to find a lot of people that still work there after, what, five years. And it's a company based in… California, headquartered in California, so you would expect people to, you know, jump around a bit. And I was pleasantly surprised to find the same folks there. So, that was also one of the reasons why I came back.Corey: It's always a strong endorsement when former employees rejoin a company. Because, I don't know about you, but I've always been aware of those companies you work for, you leave. Like, “Aw, I'm never doing that again for love or money,” just because it was such an unpleasant experience. So, it speaks well when you see companies that do have a culture of boomerangs, for lack of a better term.Laurent: That's the one we use internally, and there's a couple. More than a couple.Corey: So, one thing that seems to have been a thread through most of your career has been an emphasis on developer experience. And I don't know if we come at it from the same perspective, but to me, what drives nuts is honestly, with my work in cloud, bad developer experience manifests as the developer in question feeling like they're somehow not very good at their job. Like, they're somehow not understanding how all this stuff is supposed to work, and honestly, it leads to feeling like a giant fraud. And I find that it's pernicious because even when I intellectually know for a fact that I'm not the dumbest person ever to use this tool when I don't understand how something works, the bad developer experience manifests to me as, “You're not good enough.” At least, that's where I come at it from.Laurent: And also, I [unintelligible 00:05:34] to people that build these products because if we build the products, the user might be in the same position that we are right now. And so, we might be responsible for that experience [unintelligible 00:05:43] a developer, and that's not a great feeling. So, I completely agree with you. I've tried to… always on software-focused companies, whether it was Nuxeo, Couchbase, Clever Cloud, and then Couchbase. And I guess one of the good thing about coming back to a developer-focused era is all the product alignments.Like, a lot of people talk about product that [grows 00:06:08] and what it means. To me what it means was, what it meant—what it still means—building a product that developer wants to use, and not just want to, sometimes it's imposed to you, but actually are happy to use, and as you said, don't feel completely stupid about it in front of the product. It goes through different things. We've recently revamped our Couchbase UI, Couchbase Capella UI—Couchbase Capella is a managed cloud product—and so we've added a lot of in-product getting started guidelines, snippets of code, to help developers getting started better and not have that feeling of, “What am I doing? Why is it not working and what's going on?”Corey: That's an interesting decision to make, just because historically, working with a bunch of tools, the folks who are building the documentation working with that tool, tend to generally be experts at it, so they tend to optimize for improving things for the experience of someone has been using it for five years as opposed to the newcomer. So, I find that the longer a product is in existence, in many cases, the worse the new user experience becomes because companies tend to grow and sprawl in different ways, the product does likewise. And if you don't know the history behind it, “Oh, your company, what does it do?” And you look at the website and there's 50 different offerings that you have—like, the AWS landing page—it becomes overwhelming very quickly. So, it's neat to see that emphasis throughout the user interface on the new developer experience.On the other side of it, though, how are the folks who've been using it for a while respond to those changes? Because it's frustrating for me at least, when I log into a new account, which happens periodically within AWS land, and I have this giant series of onboarding pop-ups that I have to click to make go away every single time. How are they responding to it?Laurent: Yeah, it's interesting. One of the first things that struck me when I joined Couchbase the first time was the size of the technical documentation team. Because the whole… well, not the whole point, but part of the reason why they exist is to do that, to make sure that you understand all the differences and that it doesn't feel like the [unintelligible 00:08:18] what the documentation or the product pitch or everything. Like, they really, really, really emphasize on this from the very beginning. So, that was interesting.So, when you get that culture built into the products, well, the good thing is… when people try Couchbase, they usually stick with Couchbase. My main issue as a Director of the Developer Relations is not to make people stick with Couchbase because that works fairly well with the product that we have; it's to make them aware that we exist. That's the biggest issue I have. So, my goal as DevRel is to make sure that people get the trial, get through the trial, get all that in-app context, all that helps, get that first sample going, get that first… I'm not going to say product built because that's even a bit further down the line, but you know, get that sample going. We have a code playground, so when you're in the application, you get to actually execute different pieces of code, different languages. And so, we get those numbers and we're happy to see that people actually try that. And that's a, well, that's a good feeling.Corey: I think that there's a definite lack of awareness almost industry-wide around the fact that as the diversity of your customers increases, you have to have different approaches that meet them at various points along the journey. Because things that I've seen are okay, it's easy to ass—even just assuming a binary of, “Okay, I've done this before a thousand times; this is the thousand and first, I don't need the Hello World tutorial,” versus, “Oh, I have no idea what I'm doing. Give me the Hello World tutorial,” there are other points along that continuum, such as, “Oh, I used to do something like this, but it's been three years. Can you give me a refresher,” and so on. I think that there's a desire to try and fit every new user into a predefined persona and that just doesn't work very well as products become more sophisticated.Laurent: It's interesting, we actually have—we went through that work of defining those personas because there are many. And that was the origin of my departure. I had one person, ops slash DBA slash the person that maintain this thing, and I wanted to talk to all the other people that built the application space in Couchbase. So, we broadly segment things into back-end, full-stack, and mobile because Couchbase is also a mobile database. Well, we haven't talked too much about this, so I can explain you quickly what Couchbase is.It's basically a distributed JSON database with an integrated caching layer, so it's reasonably fast. So it does cache, and when the key-value is JSON, then you can create with SQL, you can do full-text search, you can do analytics, you can run user-defined function, you get triggers, you get all that actual SQL going on, it's transactional, you get joins, ANSI joins, you get all those… windowing function. It's modern SQL on the JSON database. So, it's a general-purpose database, and it's a general-purpose database that syncs.I think that's the important part of Couchbase. We are very good at syncing cluster of databases together. So, great for multi-cloud, hybrid cloud, on-prem, whatever suits you. And we also sync on the device, there's a thing called Couchbase Mobile, which is a local database that runs in your phone, and it will sync automatically to the server. So, a general-purpose database that syncs and that's quite modern.We try to fit as much way of growing data as possible in our database. It's kind of a several-in-one database. We call that a data platform. It took me a while to warm up to the word platform because I used to work for an enterprise content management platform and then I've been working for a Platform as a Service and then a data platform. So, it took me a bit of time to warm up to that term, but it explained fairly well, the fact that it's a several-in-one product and we empower people to do the trade-offs that they want.Not everybody needs… SQL. Some people just need key-value, some people need search, some people need to do SQL and search in the same query, which we also want people to do. So, it's about choices, it's about empowering people. And that's why the word platform—which can feel intimidating because it can seem complex, you know, [for 00:12:34] a lot of choices. And choices is maybe the enemy of a good developer experience.And, you know, we can try to talk—we can talk for hours about this. The more services you offer, the more complicated it becomes. What's the sweet spots? We did—our own trade-off was to have good documentation and good in-app help to fix that complexity problem. That's the trade-off that we did.Corey: Well, we should probably divert here just to make sure that we cover the basic groundwork for those who might not be aware: what exactly is Couchbase? I know that it's a database, which honestly, anything is a database if you hold it incorrectly enough; that's my entire shtick. But what is it exactly? Where does it start? Where does it stop?Laurent: Oh, where does it start? That's an interesting question. It's a… a merge—some people would say a fork—of Apache CouchDB, and membase. Membase was a distributed key-value store and CouchDB was this weird Erlang and C JSON REST API database that was built by Damian Katz from Lotus Notes, and that was in 2006 or seven. That was before Node.js.Let's not care about the exact date. The point is, a JSON and REST API-enabled database before Node.js was, like, a strong [laugh] power move. And so, those two merged and created the first version of Couchbase. And then we've added all those things that people want to do, so SQL, full-text search, analytics, user-defined function, mobile sync, you know, all those things. So basically, a general-purpose database.Corey: For what things is it not a great fit? This is always my favorite question to ask database folks because the zealot is going to say, “It's good for every use case under the sun. Use it for everything, start to finish”—Laurent: Yes.Corey: —and very few databases can actually check that box.Laurent: It's a very interesting question because when I pitch like, “We do all the things,” because we are a platform, people say, “Well, you must be doing lots of trade-offs. Where is the trade-off?” The trade-off is basically the way you store something is going to determine the efficiency of your [growing 00:14:45]—or the way you [grow 00:14:47] it. And that's one of the first thing you learn in computer science. You learn about data structure and you know that it's easier to get something in a hashmap when you have the key than passing your whole list of elements and checking your data, is it right one? It's the same for databases.So, our different services are different ways to store the data and to query it. So, where is it not good, it's where we don't have an index or a service that answer to the way you want to query data. We don't have a graph service right now. You can still do recursive common table expression for the SQL nerds out there, that will allow you to do somewhat of a graph way of querying your data, but that's not, like, actual—that's not a great experience for people were expecting a graph, like a Neo4j or whatever was a graph database experience.So, that's the trade-off that we made. We have a lot of things at the same place and it can be a little hard, intimidating to operate, and the developer experience can be a little, “Oh, my God, what is this thing that can do all of those features?” At the same time, that's just, like, one SDK to learn for all of the features we've just talked about. So, that's what we did. That's a trade-off that we did.It sucks to operate—well, [unintelligible 00:16:05] Couchbase Capella, which is a lot like a vendor-ish thing to say, but that's the value props of our managed cloud. It's hard to operate, we'll operate this for you. We have a Kubernetes operator. If you are one of the few people that wants to do Kubernetes at home, that's also something you can do. So yeah, I guess what we cannot do is the thing that Route 53 and [Unbound 00:16:26] and [unintelligible 00:16:27] DNS do, which is this weird DNS database thing that you like so much.Corey: One thing that's, I guess, is a sign of the times, but I have to confess that I'm relatively skeptical around, when I pull up couchbase.com—as one does; you're publicly traded; I don't feel that your company has much of a choice in this—but the first thing it greets me with is Couchbase Capella—which, yes, that is your hosted flagship product; that should be the first thing I see on the website—then it says, “Announcing Capella iQ, AI-powered coding assistance for developers.” Which oh, great, not another one of these.So, all right, give me the pitch. What is the story around, “Ooh, everything that has been a problem before, AI is going to make it way better.” Because I've already talked to you about developer experience. I know where you stand on these things. I have a suspicion you would not be here to endorse something you don't believe in. How does the AI magic work in this context?Laurent: So, that's the thing, like, who's going to be the one that get their products out before the other? And so, we're announcing it on the website. It's available on the private preview only right now. I've tried it. It works.How does it works? The way most chatbot AI code generation work is there's a big model, large language model that people use and that people fine-tune into in order to specialize it to the tasks that they want to do. The way we've built Couchbase iQ is we picked a very famous large language model, and when you ask a question to a bot, there's a context, there's a… the size of the window basically, that allows you to fit as much contextual information as possible. The way it works and the reason why it's integrated into Couchbase Capella is we make sure that we preload that context as much as possible and fine-tune that model, that [foundation 00:18:19] model, as much as possible to do whatever you want to do with Couchbase, which usually falls into several—a couple of categories, really—well maybe three—you want to write SQL, you want to generate data—actually, that's four—you want to generate data, you want to generate code, and if you paste some SQL code or some application code, you want to ask that model, what does do? It's especially true for SQL queries.And one of the questions that many people ask and are scared of with chatbot is how does it work in terms of learning? If you give a chatbot to someone that's very new to something, and they're just going to basically use a chatbot like Stack Overflow and not really think about what they're doing, well it's not [great 00:19:03] right, but because that's the example that people think most developer will do is generate code. Writing code is, like, a small part of our job. Like, a substantial part of our job is understanding what the code does.Corey: We spend a lot more time reading code than writing it, if we're, you know—Laurent: Yes.Corey: Not completely foolish.Laurent: Absolutely. And sometimes reading big SQL query can be a bit daunting, especially if you're new to that. And one of the good things that you get—Corey: Oh, even if you're not, it can still be quite daunting, let me assure you.Laurent: [laugh]. I think it's an acquired taste, let's be honest. Some people like to write assembly code and some people like to write SQL. I'm sort of in the middle right now. You pass your SQL query, and it's going to tell you more or less what it does, and that's a very nice superpower of AI. I think that's [unintelligible 00:19:48] that's the one that interests me the most right now is using AI to understand and to work better with existing pieces of code.Because a lot of people think that the cost of software is writing the software. It's maintaining the codebase you've written. That's the cost of the software. That's our job as developers should be to write legacy code because it means you've provided value long enough. And so, if in a company that works pretty well and there's a lot of legacy code and there's a lot of new people coming in and they'll have to learn all those things, and to be honest, sometimes we don't document stuff as much as we should—Corey: “The code is self-documenting,” is one of the biggest lies I hear in tech.Laurent: Yes, of course, which is why people are asking retired people to go back to COBOL again because nobody can read it and it's not documented. Actually, if someone's looking for a company to build, I guess, explaining COBOL code with AI would be a pretty good fit to do in many places.Corey: Yeah, it feels like that's one of those things that would be of benefit to the larger world. The counterpoint to that is you got that many business processes wrapped around something running COBOL—and I assure you, if you don't, you would have migrated off of COBOL long before now—it's making sure that okay well, computers, when they're in the form of AI, are very, very good at being confident-sounding when they talk about things, but they can also do that when they're completely wrong. It's basically a BS generator. And that is a scary thing when you're taking a look at something that broad. I mean, I'll use the AI coding assistance for things all the time, but those things look a lot more like, “Okay, I haven't written CloudFormation from scratch in a while. Build out the template, just because I forget the exact sequence.” And it's mostly right on things like that. But then you start getting into some of the real nuanced areas like race conditions and the rest, and often it can make things worse instead of better. That's the scary part, for me, at least.Laurent: Most coding assistants are… and actually, each time you ask its opinion to an AI, they say, “Well, you should take this with a grain of salt and we are not a hundred percent sure that this is the case.” And this is, make sure you proofread that, which again, from a learning perspective, can be a bit hard to give to new students. Like, you're giving something to someone and might—that assumes is probably as right as Wikipedia but actually, it's not. And it's part of why it works so well. Like, the anthropomorphism that you get with chatbots, like, this, it feels so human. That's why it get people so excited about it because if you think about it, it's not that new. It's just the moment it took off was the moment it looked like an assertive human being.Corey: As you take a look through, I guess, the larger ecosystem now, as well as the database space, given that is where you specialize, what do you think people are getting right and what do you think people are getting wrong?Laurent: There's a couple of ways of seeing this. Right now, when I look at from the outside, every databases is going back to SQL, I think there's a good reason for that. And it's interesting to put into perspective with AI because when you generate something, there's probably less chance to generate something wrong with SQL than generating something with code directly. And I think five generation—was it four or five generation language—there some language generation, so basically, the first innovation is assembly [into 00:23:03] in one and then you get more evolved languages, and at some point you get SQL. And SQL is a way to very shortly express a whole lot of business logic.And I think what people are doing right now is going back to SQL. And it's been impressive to me how even new developers that were all about [ORMs 00:23:25] and [no-DMs 00:23:26], and you know, avoiding writing SQL as much as possible, are actually back to it. And that's, for an old guy like me—well I mean, not that old—it feels good. I think SQL is coming back with a vengeance and that makes me very happy. I think what people don't realize is that it also involves doing data modeling, right, and stuff because database like Couchbase that are schemaless exist. You should store your data without thinking about it, you should still do data modeling. It's important. So, I think that's the interesting bits. What are people doing wrong in that space? I'm… I don't want to say bad thing about other databases, so I cannot even process that thought right now.Corey: That's okay. I'm thrilled to say negative things about any database under the sun. They all haunt me. I mean, someone wants to describe SQL to me is the chess of the programming world and I feel like that's very accurate. I have found that it is far easier in working with databases to make mistakes that don't wash off after a new deployment than it is in most other realms of technology. And when you're lucky and have a particular aura, you tend to avoid that stuff, at least that was always my approach.Laurent: I think if I had something to say, so just like the XKCD about standards: like, “there's 14 standards. I'm going to do one that's going to unify them all.” And it's the same with database. There's a lot… a [laugh] lot of databases. Have you ever been on a website called dbdb.io?Corey: Which one is it? I'm sorry.Laurent: Dbdb.io is the database of databases, and it's very [laugh] interesting website for database nerds. And so, if you're into database, dbdb.io. And you will find Couchbase and you will find a whole bunch of other databases, and you'll get to know which database is derived from which other database, you get the history, you get all those things. It's actually pretty interesting.Corey: I'm familiar with DB-Engines, which is sort of like the ranking databases by popularity, and companies will bend over backwards to wind up hitting all of the various things that they want in that space. The counterpoint with all of it is that it's… it feels historically like there haven't exactly been an awful lot of, shall we say, huge innovations in databases for the past few years. I mean, sure, we hear about vectors all the time now because of the joy that's AI, but smarter people than I are talking about how, well that's more of a feature than it is a core database. And the continual battle that we all hear about constantly is—and deal with ourselves—of should we use a general-purpose database, or a task-specific database for this thing that I'm doing remains largely unsolved.Laurent: Yeah, what's new? And when you look at it, it's like, we are going back to our roots and bringing SQL again. So, is there anything new? I guess most of the new stuff, all the interesting stuff in the 2010s—well, basically with the cloud—were all about the distribution side of things and were all about distributed consensus, Zookeeper, etcd, all that stuff. Couchbase is using an RAFT-like algorithm to keep every node happy and under the same cluster.I think that's one of the most interesting things we've had for the past… well, not for the past ten years, but between, basically, 20 or… between the start of AWS and well, let's say seven years ago. I think the end of the distribution game was brought to us by the people that have atomic clock in every data center because that's what you use to synchronize things. So, that was interesting things. And then suddenly, there wasn't that much innovation in the distributed world, maybe because Aphyr disappeared from Twitter. That might be one of the reason. He's not here to scare people enough to be better at that.Aphyr was the person behind the test called the Jepsen Test [shoot 00:27:12]. I think his blog engine was called Call Me Maybe, and he was going through every distributed system and trying to break them. And that was super interesting. And it feels like we're not talking that much about this anymore. It really feels like database have gone back to the status of infrastructure.In 2010, it was not about infrastructure. It was about developer empowerment. It was about serving JSON and developer experience and making sure that you can code faster without some constraint in a distributed world. And like, we fixed this for the most part. And the way we fixed this—and as you said, lack of innovation, maybe—has brought databases back to an infrastructure layer.Again, it wasn't the case 15 years a—well, 2023—13 years ago. And that's interesting. When you look at the new generation of databases, sometimes it's just a gateway on top of a well-known database and they call that a database, but it provides higher-level services, provides higher-level bricks, better developer experience to developer to build stuff faster. We've been trying to do this with Couchbase App Service and our sync gateway, which is basically a gateway on top of a Couchbase cluster that allow you to manage authentication, authorization, that allows you to manage synchronization with your mobile device or with websites. And yeah, I think that's the most interesting thing to me in this industry is how it's been relegated back to infrastructure, and all the cool stuff, new stuff happens on the layer above that.Corey: I really want to thank you for taking the time to speak with me. If people want to learn more, where's the best place for them to find you?Laurent: Thanks for having me and for entertaining this conversation. I can be found anywhere on the internet with these six letters: L-D-O-G-U-I-N. That's actually 7 letters. Ldoguin. That's my handle on pretty much any social network. Ldoguin. So X, [BlueSky 00:29:21], LinkedIn. I don't know where to be anymore.Corey: I hear you. We'll put links to all of it in the [show notes 00:29:27] and let people figure out where they want to go on that. Thank you so much for taking the time to speak with me today. I really do appreciate it.Laurent: Thanks for having me.Corey: Laurent Doguin, Director of Developer Relations and Strategy at Couchbase. I'm Cloud Economist Corey Quinn and this episode has been brought to us by our friends at Couchbase. If you enjoyed this episode, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry comment that you're not going to be able to submit properly because that platform of choice did not pay enough attention to the experience of typing in a comment.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Shawnna Sumaoang: Hi, and welcome to the Sales Enablement PRO Podcast. I'm Shawnna Sumaoang. Sales enablement is a constantly evolving space, and we're here to help professionals stay up to date on the latest trends and best practices so that they can be more effective in their jobs. Today I'm excited to have Nicholas Gregory from Qlik join us. Nick, I would love for you to introduce yourself, your role, and your organization to our audience. Nicholas Gregory: Thank you so much, Shawnna, for the opportunity to speak to you and to speak to your audience here. My name is Nicholas Gregory. I started my career in sales after university. Specifically with a cybersecurity company called McAfee about 15 years ago, where I was given an opportunity to fulfill a very personal and professional goal of mine to work in Latin America, which is a different conversation for a different day. Nonetheless, the powers that be at the company, knowing my aspirations to work in Latin America, tap me on the shoulder to be a new member of a new global team of sales consultants placed regionally across the globe to deploy what we would call ‘enablement services today' in a globally consistent manner. I was brought on to that team to lead their Latin America efforts from a sales enablement services perspective and that’s where I found myself in enablement. Since that time I’ve led a regional, and most of my career now, global sales enablement teams for technology organizations such as Symantec, Veritas, Sabre, and Couchbase. Currently, I’m the global head of sales enablement and effectiveness at Qlik, and we’re a business intelligence, data analytics, and data integration company where we help organizations to better understand their data, whatever that might mean to them, to run their business and help turn their data into action. SS: Well, Nick, we’re excited to have you here joining us with your wealth of experience. One of the things that caught my eye about your background was the focus on improving sales productivity, which I think is the ultimate goal for most folks in enablement. In your opinion, what is enablement’s role in helping to drive productivity for the business? NG: Enablement’s role in improving sales productivity is very multifaceted. To answer, first, I’ll speak to what I feel is important to share with the audience, which is my opinion on what are the four key principle enablement services that enablement should provide to the organization itself. that we’re working for. This is from an end-to-end strategic discipline perspective. Those are four in this order. Technology services, so that is, we may not own the sales tech stack or most of the sales tech stack, but we train on those particular tools, let’s say, or in partnership with whoever might own those tools, whether it’s marketing or other parts of organization, and also in some cases, we own part of the tech stack as well, where we are from an admin perspective, but we’re here to train on those tools, no matter where they reside and who funds them on how to be more efficient and effective with those tools. Whether it’s a conversation intelligence tool, a prospecting tool, whatever the case may be, or your CRM whatever the case may be, we’re here to help support being more effective. Number two, training services. We can’t forget where we came from in enablement. We’re born out of training, but that is a key component to the four services, training services. That is your onboarding, methodology, product training, business acumen training, industry training, and everything in between. Number three is coaching services, which is a critical component and often doesn’t get funded as much as it should with organizations today, especially in this changing buyer-seller landscape. Any of the investments we make that are imperative for the organization, be the actual organization itself or the sales organization, we should be supporting the organization through coaching services to protect those investments we’re making, whether those are financial investments from an enablement perspective, or be it that it’s like time, a soft cost investment, whatever the case may be, what’s the most important to the organization, we should be coaching to the sustainment of those investments. Last but not least is content services. A lot of times we create content and if you look at the research, sales themselves create a lot of content that they use in front of the customer or send to customers. Also, we work with partners in marketing that create a lot of content as well. Wherever the content comes from, we need to make sure that it’s synthesized for sales so that they make the most of that content and they’re not reinventing the wheel or having to edit a lot of that content that is being dispersed. Whether that’s through the technology services that I talked about before, integrated into the CRM, or however they get their content at their organization. That’s just to provide a perspective of the four key principal enablement services that I feel are most important that we drive from a strategic perspective. Second, let’s agree on a high-level definition of sales productivity. If we can agree on that, it means how we measure how the organization leverages those enablement services I just spoke about to achieve organizational outcomes while reducing the time and costs to acquire new business. No service that I just talked about is more important than the other on its own, it’s how many of these services work in concert to drive the outcomes, to achieve those results that we’re looking for across the organization. From my team’s perspective, the net on all this is that either we implement these services ourselves or work in partnership cross functionally to improve the efficacy and efficiency when using our sales tech stack as a part of our technology services, or reduce ramp time for new hires as a part of our onboarding to full productivity, or implement and drive adoption of the sales methodology that we might purchase from a methodology provider, or concentrate on the opportunities that will yield the most likelihood of winning or developing our most strategic accounts. That will increase selling time by focusing on those opportunities or on those accounts that matter the most as a part of training services. What I mentioned about coaching services, keeping our sales skills sharp and reinforcing the most critical programs and initiatives so that leaders and reps know what to focus on. Lastly, content services, whether we create the content ourselves or work in partnership with product marketing as I mentioned before, it’s about providing the right content to the right people at the right time internally so that they can then turn that content into Action or into customer-facing content through customer engagements, and they’re wasting time to find that content that might be outdated, not relevant, or requires a lot of updates from the sales reps as I mentioned before. It’s often these services working in concert to drive maximum productivity gains as much as possible, and we should always be measuring everything, whether it’s leading or lagging indicators across all these services. Especially at the cornerstone of productivity, whatever productivity might mean for you and your organization. SS: I love that. I love how crisply you’ve defined what productivity means within your own organization. Now, one way that we’ve seen enablement help enhance productivity is by enabling reps with a sales methodology. Can you walk us through why a sales methodology is critical for success? NG: First and foremost, you have to read the headlines over the last many years now that buyer expectations have dramatically changed and really sales, I would say more on the, maybe the B2B selling side, that our profession has truly changed and that what those buyer expectations are and the sales skills to keep up with those buyer expectations. It’s truly creating a gap. You can look at research to help show what that really looks like out there in the world today. Sales reps are having a difficult time keeping up with the exponential change on the buying side, so, in my opinion, sales methodology is one of the best investments a sales organization can make to help close the gap between the buyer expectations and the selling skills to make sure that we’re driving those predictable and repeatable results across the organization at scale. It provides that center line where we can be consistent in how our sales reps prepare for customer engagements through call planning or how they strategize on their most important opportunities, or the region’s most important opportunities, or from a global account manager perspective of the world’s most important opportunities for our organization and how they manage their most important and strategic accounts. With selling time at a premium, we can all agree that we’re not seeing more and more selling time across a given week, month, or quarter. When you establish a common way to operate. Internally away from the customer, as well as from an external perspective with the customer, a common language that is spoken by the entire sales force by the way of a methodology. Having a common scorecard to evaluate in a very succinct way, the most critical opportunities on the likelihood that they’ll close those opportunities that are worth pursuing the priorities from the organization on the opportunities that we should pursue now or later. After we look at the higher and higher sales methodology adoption rates that have higher and higher adoption rates of the sales methodology they institute or implement within the organization. Typically high adoption rate is anything above 75% of the organization adopting the sales methodology. This is according to Korn Ferry Sales Performance Research. Organizations start to see double-digit improvement and win rates on forecasted deals or opportunities and a double-digit increase in sellers, achieving quota and an increase in revenue attainment all the while decreasing voluntary turnover. More people making money, more people hitting quota, less and less likely to leave that organization. This is a very critical investment by the company to drive results that are most important to the organization. Oftentimes it gets overlooked in the place of more product training, or specifically just skills training or onboarding. They are all important, but if we don’t know where to place that new knowledge on skills training in a strategic way, through methodology, then it’s really missing a part of the formula to drive improved productivity across the organization. SS: I think that is fantastic. You talked about some of the key elements of key services of bringing enablement to life in terms of improving productivity. A couple of those were things like training and coaching. What are your best practices for training reps to effectively leverage a sales methodology? NG: I talked a little bit about the methodology as a whole and what it means to the organization, but in order to really start down a sales methodology journey, first and foremost, we have to understand that at the highest level, at the executive level, there has to be a commitment to change. That is demonstrated not only from a communication perspective, what is written and shared across the organization from senior leadership, but it’s also from a say, show, do perspective and leading by example. At the cornerstone of all of this is that leadership commitment shown across the organization way in advance of, hey, we’re moving down the sales methodology path of deployment. Let’s say we’ve got that buy-in from a sales leadership perspective. We are going to invest with a true sales methodology provider that is very wide in nature from focusing on how we engage with customers, how we strategize in our most important opportunities, and how we manage our most important or strategic accounts, full end to end, not just deal scorecard or things of that nature. Then it’s about making sure that we have that commitment from the top shown through communication. What are we doing, why we’re doing it, and what KPIs we are looking to improve? Also, a part of this before we even get to deploying the sales methodology is if we’re fortunate to have the funding to invest in a sales coach or a sales coaching team, a practice within the enablement team to help with not only deployment from a facilitation perspective, but ongoing reinforcement and sustainment adoption through the sales leaders as well as working one on one or one to many with sales teams. That would be a key component of this as a part of the investment. Then, we’re looking at deploying the sales methodology and we’re providing that center line of skills and behaviors and a framework. First and foremost, I’m a big believer in beyond the communications that really provide that fertile ground for making sure that we have some semblance of pre-work, whether that’s provided by the sales methodology provider, or we develop it internally or a mixture hybrid of both. We need to make sure that everyone is on a common playing field, if you will, before we head into what would be the next portion of the deployment and best practice is having the actual formal workshop. We have a coaching team, we commit to leadership, and we’re deploying pre-work that’s required before showing up at a virtual workshop, or if possible, an in-person workshop or various workshops to make sure we take care of the entire globe where they’ll apply their newly acquired knowledge. They got a lot of that knowledge from pre-work and they got a lot of that knowledge from the leadership commitment from communications and calls and things of that nature before deployment. Now it’s applying that knowledge, not just with hypotheticals, but if we’re talking about opportunity strategy as a part of our methodology, applying that knowledge with real opportunities for the sales team as a part of this workshop. If we’re talking about preparing for our most critical engagements, it’s about preparing for real customer engagements that we’ll have the buying side, leveraging the new methodology. If it’s about managing our most important accounts, it’s about applying that knowledge by using our real accounts. It’s establishing those skills and behaviors through workshops by using what’s real to the sales team. Also, part of this next is to establish a bi-weekly or weekly deal review. Now, a lot of companies already have that or should have that as a part of their operating cadence, but that being said, establishing a methodology is about providing a new way of going to market. It’s about providing a new way to strategize and opportunities. We should embed the methodology into what already exists and their deal reviews. We’re evaluating those deals through the methodology framework or a new method by which we strategize on opportunities. We’ll have a lot of success stories over the next three, six, nine months. Let’s syndicate those success stories as a part of this process and best practices across the organization. Let’s not make them isolated within one territory or one region of the globe. If we’re a global company, let’s syndicate those across the entire globe of the success stories of how the methodology is adding value to be more productive, reducing the admin time, and improving and increasing the selling time that we might have to give it across a given week or month or quarter. The number one thing when we’re thinking about those best practices I just mentioned is we have to define who was a part of this methodology as well. That goes back to the very beginning in some cases and what we’re going to deploy across the organization. While we call it a sales methodology, it’s truly an organization-wide commitment in many regards. We need to ensure that we are onboarding all members of the account team to the methodology and all of what I just said before, as far as those best practices are concerned. Most, if not all the people I’m about to mention should be a part of this journey, whether that’s through the full end-to-end methodology deployment experience or a subset of the deployment, depending on an individual’s role. Let’s take B2B technology sales for a moment that might take the form of fully implementing the methodology across account executives, solution engineers, partners, account management, teams, professional services, and customer success. Also, of course, all levels of leadership across those teams. Those are the core teams that engage with an interface with prospects and customers. Then we take the perspective of who else supports the account team across the company and my interface with customers from time to time. We may be on board to a lesser extent, marketing teams such as digital or social teams, field marketing, legal, procurement, and others who often, like I said, interface with prospects and customers throughout the sales or customer buying cycles. Sometimes those teams contribute in a variety of ways to opportunity and account-level strategy. Implementing a sales methodology is truly a cross-functional deployment, not just specific to the sales team. Number two, the last thing I’ll mention, Shawnna, is about partnership with marketing. While they will be going along the journey with us in many regards, maybe to a lesser extent from a full onboarding experience, we have to make sure that we support the sales team by partnering with marketing that supports us and enablement services so much and engages with sales directly with content and other ways. Our ongoing partnership with them shall provide that center line as marketing to engage with prospects and customers strategizes on those opportunities. They help us manage some of those most strategic accounts in a globally consistent manner. As our internal language shifts, so should the language that marketing uses externally and internally to be more customer outcome-driven, less product feature function-oriented. Therefore any content they’re creating that is customer-facing or sent to the sales teams internally, or like I said, in some cases, externally should evolve as well. That partnership with marketing to ensure alignment on content, the new language that’s used the intent of the content has to change with it. Whether that’s sales play content, competitive battle cards, or ongoing support through the creation of discovery questions to be used throughout the entire, that sales cycle, no matter the asset, it should change and align to the methodology in that common language. SS: I love that. You also mentioned coaching earlier a few times, actually throughout that. What role does coaching play in helping reps to effectively leverage a sales methodology? NG: Coaching, or the lack thereof, is one of the most critical determining factors if an investment is worthwhile. It truly is an investment financially in most regards, unless you’re fortunate to build one internally. Coaching can and should come in many forms. Coaching can come in the form of practice from a coaching practice perspective. If we’re fortunate to have a coaching team, like I’m fortunate to have here at Qlik, this team is dedicated to sales to the sales professionals, their leaders, and their leaders leaders and their remit is to coach leaders in the sales teams on the key imperatives for the sales team, the organization, such as methodology in this case that you asked about. Sales professionals can provide coaching themselves. It can come from not only the first-line, second-line leaders, a coaching team if we’re fortunate to have one, but also sales reps that are, I mentioned those success stories before. Sales can coach sales. I’m a big believer that sales learn best from sales. This is a great opportunity when we’re having success, We call out those sales reps to bring them into a pseudo-coaching role where they’re actually helping coach their peers from within their own teams, within their own region, whatever the case may be. Also, we can look at successful leaders who can request that other leaders, let’s say, provide a community of coaches from across the leadership teams where those leaders are not only developing and coaching their teams, but they’re also helping develop and coach other teams around on an ad-hoc basis, or maybe even a more formal basis, as well across the region or across the globe. That ongoing and effective coaching drives sustainment, adoption, and reinforcement of the methodology investment that can be very expensive on top of the commitment to change. It can be very expensive from a financial and soft cost perspective. Coaching is critically important to longevity and the likelihood of success as I mentioned before. On top of my coaching team being certified, I’m going to mention this point. Their responsibility is to facilitate the methodology training workshops and provide their own reinforcement in a variety of ways. My coaches are laser-focused when deploying a methodology to help those first-line and second-line leaders become better coaches. Oftentimes you’ll hear so many sales consultancy firms talk about how they are the most underinvested people in the sales organization with some of the most difficult jobs. That upward pressure from their teams, and downward pressure from leadership, but we provide little to no investment in them to be better coaches. A lot of times they weren’t really trained to be sales leaders. They were an individual contributor on a Friday promoted from within, let’s say five, 10 years ago, and they’ve just been in this leadership role for quite some time. Maybe successful, maybe you know, plateauing a little bit here and there, but they’ve never been invested in. It’s my team’s job to help them be better first-line and second-line leaders underpinned by the methodology. Sales organizations that have a sales methodology coupled with an ongoing and multifaceted coaching presence that I mentioned before, can see upwards of 28% of higher quota attainment and 32% higher win rates versus organizations that might have a methodology that made that investment. Leave coaching up to the leader’s discretion as I mentioned before, where they weren’t invested in their sales leadership career to be better coaches. This is an opportunity to have a coaching team drive true coaching in a consistent way, underpinned by the methodology to drive those results I just mentioned before. SS: Wonderful. In both training and coaching on methodology, I love that there’s this leadership-first mentality. Can you tell our audience about this approach and the impact that it’s had on the effectiveness of your training and coaching programs? NG: There are a few aspects to this that are top of mind and top of my list when deploying a true sales methodology. Let’s say that the org, as I mentioned previously, and the senior leadership have stacked hands, that there is a commitment to change, and that there are results that we’re looking to change and move the needle in a variety of different areas. From that commitment, we’re going to partner with a true sales methodology. Now, in order for that leadership-first mentality, you spoke of to really take hold. Number one, we need to bring leaders along with the pre-deployment journey. It can’t be something, hey, this isolated vacuum, we decided as a part of a senior leadership team that we’re going to be investing in a sales methodology and then all of a sudden it’s about to happen and they don’t get much of an advanced warning or awareness on from a change management perspective itself. We got to bring them along that pre-deployment journey to help with the change management side of the house because this is a huge change management initiative, a transformation. I think we agree that implementing a sales methodology is a big change management and transformational exercise. We need to work with those first-line leaders across all of the sales segments and across the cross-functional partners that I mentioned previously to help set expectations. What is their role during the actual implementation from a training perspective? What is the post-deployment? What are the expectations on how the leaders will reinforce, drive adoption, and sustainment? Sharing what the plan is, end to end, early and often prior to deployment, and what KPIs we’ll be measuring so that there are no surprises there. Gaining their commitment, now that’s not a hundred percent always going to happen there are going to be detractors. I think we can all agree that nothing that we do from an enablement services perspective or program or strategic comparative gets a hundred percent commitment, but that being said, let’s take the majority and get that commitment where possible. What changes should they expect there will definitely be changes moving forward. Also, what communications in some cases we would like these first-line second leaders to send out to their teams, to the region? A lot of those communications could be ghostwritten by us or others in the organization, but nonetheless, we need to make sure they put their voice behind the change that’s about to take place. In this regard, over-communication and constant engagement is key. With leaders, just as much as the individual contributors that report to them. The second is through the deployment from a training perspective. I’m a big believer, especially when it comes to methodology deployment or any large imperative for that matter, that leaders go first. What I mean by that is that leaders go through the same mandatory pre-work that their individual contributors or teams will go through. I typically have leadership-only training workshops. They go through pre-work first, then they have what we have. Leadership-only workshops where the leaders are trained ahead of their teams. They go through the training as their team is about to go through throughout the deployment. They go from learner now going through these leadership-only workshops to a second time going through the training because they’ll now be going through the training workshops with their team. They turn from learner to coach the second time around. As a quick recap, they take the pre-work, they go through leadership-only workshops, and they go through the workshop again with their teams when we deploy to the field at large, going from learner to coach. From that point, the individual contributors or field workshops become those coaches and start to reinforce and drive that adoption. That’s so critical during the workshop in real time, sitting next to their teams or at the same tables, if you will, or in a virtual setting with their team. This approach is where it’s front-loaded per se from a training perspective, but the large focus of leaders is critically important because they truly are the force multipliers when deploying a methodology or again, any large investment, because they’re the ones within the organization. That decides if typically a large investment like this, whether financially or soft cost-wise, is going to be successful or not. It really falls on their shoulders. We have to take that extra work, that front-loaded work during the rollout, prior to the rollout, and then of course, through any deployment or any sustainment or adoption reinforcement activities and exercises moving forward. Last but not least, this is for a very special group of leaders. In some cases, there are a handful of leaders who accept and go on a specific methodology deployment journey in a unique way by way of getting certified on the methodology themselves. While I’m a big believer in the enablement team, if we’re fortunate enough to have a coaching team or others across the needle, be certified to become facilitators. If we partner with an external methodology provider, sometimes these leaders also invest in themselves, their team, and the organization. by going through a very similar path that many of us go through an enablement to get certified in the methodology themselves. I may not be up to a facilitation grade certification if you will, but that being said, they go on some assemblage of that journey by being trained on the methodology in a unique way beyond the workshop by partnering with the methodology provider. Then going on this journey for this very special group shows commitment. In some cases, we can lean on those leaders because they’ve been on this certain journey up to a certain point to support other efforts within their region or globally based on their subject matter expertise and dedication to knowing the methodology at a deeper level than let’s say a traditional leader going through a leadership workshop only, as well as the workshop with their teams to drive that coaching. This is a special breed, if you will, of leadership that ops in and we partner with to help them on going through that unique journey to drive a different level of results. SS: I love that leader’s first mentality, Nick. Thank you so much for joining us. I enjoyed this conversation and I think it’s fantastic the work that you guys have been doing to increase productivity at Qlik. NG: Thank you so much Shawnna for the time and look forward to a conversation in the future. SS: To our audience, thanks for listening. For more insights, tips, and expertise from sales enablement leaders, visit salesenablement.pro. If there's something you'd like to share or a topic you'd like to learn more about, please let us know. We'd love to hear from you.

Welcome to episode 224 of The CloudPod Podcast - where the forecast is always cloudy! This week, your hosts Justin, Jonathan, and Ryan discuss some major changes at Terraform, including switching from open source to a BSL License. Additionally, we cover updates to Amazon S3, goodies from Storage Day, and Google Gemini vs. Open AI.  Titles we almost went with this week: None! This week's title was ✨chef's kiss✨ A big thanks to this week's sponsor: Foghorn Consulting provides top-notch cloud and DevOps engineers to the world's most innovative companies. Initiatives stalled because you have trouble hiring?  Foghorn can be burning down your DevOps and Cloud backlogs as soon as next week.

Do you love licensing drama? Last week HashiCorp made headlines with an announcement by CTO Armon Dadgar that they're changing licensing models. HashiCorp is now adopting the Business Source License, or BSL, which was popularized by MariaDB and Couchbase. Under the BSL, HashiCorp code will remain freely available and usable for non-production use. You may be granted a license for production use if your project doesn't compete with HashiCorp. If it does you'll need to buy a commercial license. The move has generated a lot of discussion and speculation in the community given how prevalent projects like Terraform are. This and more on the Rundown. Time Stamps: 0:00 - Welcome to the Rundown 0:43 - NVIDIA Launches Refreshed H100 Without Intel 4:41 - Years of Intel CPUs affected by Downfall Bug 9:06 - Groq and Samsung Foundry Bring Next-Gen LPU 13:43 - OpenELA is formed by Oracle, SUSE, and More 18:03 - Intel Terminates Tower Semiconductor Acquisition 21:27 - Itential and Alkira Team Up 24:27 - Business Source License Adopted by HashiCorp 39:41 - The Weeks Ahead41:07 - Thanks for WatchingFollow our Hosts on Social Media Tom Hollingsworth: https://www.twitter.com/NetworkingNerd Stephen Foskett: https://www.twitter.com/SFoskett Follow Gestalt IT Website: https://www.GestaltIT.com/ Twitter: https://www.twitter.com/GestaltIT LinkedIn: https://www.linkedin.com/company/Gestalt-IT #Rundown, #OpenELA, #AI, #Security, #Linux, #OpenSource, @IntelBusiness, @GroqInc, @Samsung, @Oracle, @SUSE, @Redhat, @Itential, @Alkira, @HashiCorp, #TFDx, #VMwareExplore, #SFD26, #SDC2023, #EFD2,

Join Nelson as he speaks to Fidelma Butler, Chief People Officer at Couchbase. They discuss how Fidelma entered the HR space, the power of storytelling and data to drive change, how CPOs can spend more wisely, work-life balance as a HR leader, and much more. Book a demo of HowNow: https://hubs.la/Q01RWy9P0 Download your FREE Death of the LMS guide: https://hubs.la/Q01RWyMr0 See HowNow in action! Sign up for a live walkthrough: https://hubs.la/Q01RWzht0  Running order: 0:00 Intro to the show 0:40 Getting into HR 4:36 HR transformation and buy-in 7:54 Storytelling and other CPO skills 10:27 Moving in-house from consulting 12:57 Keeping calm in fast-changing environments 15:18 What you wish you knew at the start 17:27 Future challenges for people leaders 19:12 Work-life balance as a CPO 21:22 Quickfire questions. Find Fidelma on LinkedIn: https://www.linkedin.com/in/fidelmabutler/ Find Nelson on LinkedIn: https://www.linkedin.com/in/nelsonsivalingam/ --- Send in a voice message: https://podcasters.spotify.com/pod/show/gethownow/message

#219: In a world overflowing with data, traditional relational databases struggled to keep up with the demands of scalability, flexibility, and performance. Enter NoSQL, a groundbreaking approach to database management that shattered the limitations of the past. In this episode, we talk with Matthew Groves, developer advocate for Couchbase, about his thoughts on SQL (the language), where you should actually start programming if you're new to the industry and why conferences and user groups are starting to make their return.   Matthew's contact information: Twitter: https://twitter.com/mgroves LinkedIn: https://www.linkedin.com/in/mgroves/   YouTube channel: https://youtube.com/devopsparadox/   Books and Courses: Catalog, Patterns, And Blueprints https://www.devopstoolkitseries.com/posts/catalog/   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

Here's what Alex got into today:Stocks are mixed around the world this morning while crypto stays pretty flat. Earnings this week that we're excited about include Gitlab, Couchbase, Yext, Smartsheet, and Hashicorp. (We're also keeping an eye on the Atomic Wallet hack.)Reddit's proposed API changes (charges, more like) are having a pretty big impact on the service's userbase; there are calls for a blackout of certain forums in response to the proposed updates. Reddit, on the other hand, is a business and needs to make money.Sticking to social media, news broke this morning that Twitter's revenues are down sharply compared to year-ago totals, at least when we consider its American advertising incomes. Twitter does more than just ads in North America, but given that it's likely a pretty big chunk of its total top line, it's not good news.Canva's valuation was slashed by a mutual fund (something that we have seen a lot lately), the latest in a string of similar headlines for other unicorns.Closing, WWDC is today. Get. Hype.Don't forget: our listener survey is back! If you can, please take a moment to let us know what you want more of, what you want less of, and how we can make this the kind of podcast you want to come back to every week. Equity will be back on Thursday this week, but in the meantime, you can catch us on Twitter @EquityPod.For episode transcripts and more, head to Equity's Simplecast website. Equity drops at 7:00 a.m. PT every Monday, Wednesday and Friday, so subscribe to us on Apple Podcasts, Overcast, Spotify and all the casts. TechCrunch also has a great show on crypto, a show that interviews founders, one that details how our stories come together and more!

Join THE HOSS Matt Yonkovit and his guest Laurent Doguin (Developer Relations and Strategy at Couchbase) in the Hacking Open Source Business Podcast as they explore various aspects of the DevRel role in the Open Source space. From transforming into a developer-friendly organization to the vital connection between Developer Relations (DevRel) and Sales, they discuss strategies, challenges, and future trends. They highlight the importance of understanding different types of developers, optimizing recruitment, integrating technologies, and collaboration between departments. The podcast also covers topics like community management, technical understanding in sales, and measuring value and metrics.Laurent's LinkedIn Profile: https://www.linkedin.com/in/ldoguin/Latest Couchbase Capella Release: https://www.couchbase.com/press-releases/latest-couchbase-capella-release-features-new-developer-platform-integrations-and-greater-enterprise-features/Checkout our other interviews, clips, and videos: https://l.hosbp.com/YoutubeDon't forget to visit the open-source business community at: https://opensourcebusiness.community/Visit our primary sponsor, Scarf, for tools to help analyze your #opensource growth and adoption: https://about.scarf.sh/Subscribe to the podcast on your favorite app:Spotify: https://l.hosbp.com/SpotifyApple: https://l.hosbp.com/AppleGoogle: https://l.hosbp.com/GoogleBuzzsprout: https://l.hosbp.com/Buzzsprout

In this next episode of the Tech Talks Daily Podcast, I'm thrilled to welcome Ravi Mayuram, the CTO of Couchbase. As the technological sphere enters an intense period of competition in artificial intelligence (AI), with key players like Microsoft and Google vying for supremacy, we find ourselves at a critical juncture for AI adoption. Ravi argues that confronting and eliminating inherent bias in AI is now more crucial than ever. Ravi also discusses the critical need for AI to be a beacon of virtue, especially when 36% of enterprises report negative impacts due to AI bias. He'll explore the wide-ranging implications of AI bias, from reputational damage to severe financial and legal consequences, backed by recent examples. He'll also stress the urgency for AI's "Guardians of the Galaxy." In a world rife with hate speech and misinformation, the role of data scientists as AI and data custodians has never been more significant. Ravi will emphasize the need for ethical practices during data collection and cleansing to ensure fair and representative decision-making by AI algorithms. Ravi will delve into the importance of a robust AI architecture that can "connect the dots" and observe the broader picture. In line with classic tales of small-town individuals discovering a diverse world, AI must also transcend its limited perspectives that can potentially induce bias. By eliminating data siloes and curating a conducive environment for AI to absorb diverse perspectives, we can mitigate bias. Join us as we navigate this complex and vital issue with Ravi Mayuram, understanding Couchbase's role in aiding businesses to counter AI bias, the importance of flexible data architectures, and the need for constant learning amid rapid technological change. Don't miss this insightful conversation, shedding light on the responsible use of AI, fostering the democratization of creativity, and preparing for the profound impact of emergent technologies on application development and software composition.

In this episode, Ravi Mayuram highlights the functionality of Couchbase as an evolutionary database platform, citing several simple day-to-day use cases and particular advantages of Couchbase. Ravi Mayuram is CTO of Couchbase. He is an accomplished engineering executive with a passion for creating and delivering game-changing products for startups as well as Fortune-500 industry-leading companies. Notes Couchbase set out to build a next-generation database. Data has evolved greatly with IT advancements. The goal was to build a database that will connect people to the newer technologies, addressing problems that relational systems did not have to solve. The fundamental shift is that earlier systems were internally focused, built for trained users but now the systems are built directly for consumers. This shift also plays out in the vast difference in the number of consumers now interacting with these systems compared to the fewer trained users previously interacting with the systems. One of the key factors that sets Couchbase apart is the No-SQL Database. It is a database that has evolved by combining five systems; a Cache and Key-value store, a Document store, a Relational document store, a Search system, and an Analytical system. Secondly, Couchbase performs well in the geo-distributed manner such that with one click, data is made available across availability zones. Lastly, all of this can be done at a large scale in seconds. Regarding the global database concept that Google talks about, a globally consistent database may not be needed by most companies. The performance will be the biggest problem as transaction speed will be considerably low. Couchbase does these transactions locally within the data center and replicates them on the other side. The main issue of relational systems is that they make you pay the price of every transaction no matter how minor, but with Couchbase, it is possible to pay only the cost only with certain crucial transactions. Edge has become a part of the enterprise architecture even such that people now have edge-based solutions. Two edges are emerging; the Network edge and the Tool edge where people are interfacing. Couchbase has built a mobile database available on devices, with sync capability. As a consumer, the primary advantage of bringing data closer to the consumer is the latency issue. Often, data has to go through firewalls and multiple steps which delays it but this is the benefit of Couchbase. The user simply continues to have access to the data while Couchbase synchronizes the data in the back. One of the applications of Couchbase in healthcare is insulin tracking. With many devices that monitor insulin which must work everywhere you go, Couchbase Lite does the insulin tracking, keeps the data even in the absence of a network, and later syncs it for review by healthcare professionals. This is also useful in operating rooms where the network is not accessible. The real benefit is seen when the data eventually gets back to the server and can be interpreted to make decisions on patient care. The Couchbase Capella Service runs in the cloud and allows clients to specify what data should be sent to the edge and what should not be. This offers privacy and security measures, such that even in the loss or damage of a device, the data is secure and can be recovered. To effectively manage edge in devices, a lot of problems must be addressed to make it easier. One of the concerns for anyone coming into Couchbase Capella is the expense of data extraction from the cloud, however, Couchbase is available on all three cloud providers. Also, with Couchbase, there is no need to keep replicating data as you can work on the data without moving it, which largely saves costs. Other use cases for Couchbase include information for flight bookings, flight crew management systems, hotel reservations, and credit card payments. To learn more, visit the Couchbase website. There is also a free trial for the Couchbase Capella Service.   Top Quotes

Chris is the cofounder of Couchbase, Chief Architect of Mobile, and President & CFO during the Membase/CouchOne merger. Recently he created Fireproof: a cloudless database I almost recorded this episode in McDonalds - but common sense prevailed SUPPORT THE SHOW Open to discussion with four companies who like my show and want to lock in a sponsorship deal at a flat yearly rate for both the next 12 and 24 months GUEST'S LINKS: LinkedIn: https://www.linkedin.com/in/jchris/ Twitter: https://twitter.com/jchris Fireproof: https://fireproof.storage/ TIMELINE: 0:00 Why do we need a new cloudless database 2:10 Can we use a Fireproof database for a banking 5:40 This could take away billions from AWS, Microsoft and Google 11:20 What could we replace some of our #postgres databases with, with Fireproof

Old technology stacks can be found throughout the sector, especially in companies that have been around for more than a few years. While most firms have undergone digital transformation of some kind, shedding legacy tech is no easy job and can lead people to take the path of least resistance, using a mix of old and new tech across their IT estate.This can lead to big issues down the line. A recent example is the outage that led to thousands of flights being cancelled and delayed across the United States, which the Federal Aviation Administration (FAA) blamed on accidental file deletion while updating a database. The authority is heavily-reliant on old systems, and has said it will take until 2029 to phase them out.In this episode, Jane and Rory speak to Ravi Mayuram, SVP of engineering and CTO at cloud database platform Couchbase, to discuss the challenges presented by legacy infrastructure, and why enterprises need to take the opportunity to upgrade before problems become entrenched.

Couchbase avec Laurent DoguinEssayez Couchbase sur Capella https://cloud.couchbase.comOu le playground https://couchbase.live/Ou dans Gitpod avec du GraphQL https://gitpod.io/#https://github.com/ldoguin/couchbase-graphql-travelVenez nous voir sur Discord: https://discord.gg/jJfT4pDU6zOn reprend les meetups https://www.meetup.com/couchbase-france/ML Meets NoSQL: Integrating Python User-Defined Functions with N1QL for Analyticshttps://www.couchbase.com/blog/ml-meets-nosql-integrating-python-user-defined-functions-with-n1ql-for-analytics/On recrute https://www.couchbase.com/careers/open-positions

Overview Today's guest is Dipti Borkar, Vice President and General Manager, SaaS, Azure Databases at Microsoft. Prior to joining Microsoft, Dipti was the Founder and Creator of Ahana, a cloud managed service. Dipit has vast experience working in startups such as Counchbase, and Marklogic, and began her career working as a software engineer for IBM. In today's episode, Dipti shares how Databases have evolved over the past 15 years, her predictions for the future of technology and provides actionable advice for those looking to start a career in technology. About Dipti Borkar Dipti is a senior technology executive and entrepreneur with over 18 years of experience in cloud, open source and distributed data / database tech including relational, NoSQL, and federated systems. Dipti is the Vice President & General Manager at Azure Data, Microsoft where she leads product and engineering teams to make cloud databases simple and smart. She founded Ahana and created a cloud managed service for SQL on data lakes where she played many roles including Chief Product Officer and VP of Cloud / Open source engineering. Prior to Ahana, she held various different executive roles at Alluxio, Couchbase and IBM. At Couchbase she held several leadership positions over the years leading and building out the product, engineering and world-wide solutions engineering teams. At IBM, Dipti managed large world-wide dev teams for DB2 Distributed where she also started her career as a software engineer in the DB2 LUW kernel. She also served as Chairperson of the Linux Foundation / Presto Foundation community for many years. Dipti holds a MS in Computer Science from UC San Diego with a specialization in databases and holds an MBA from the Haas School of Business at UC Berkeley. She is very passionate about empowering and mentoring women in tech and open source. Learn more about our mission and become a member here: https://www.womenindata.org/ All Data Bytes listeners get 20% off of WiD membership by using the code: DATABYTES20 --- Support this podcast: https://anchor.fm/women-in-data/support

Let's say you're a passenger on a cruise ship. Floating in the middle of the ocean, far from reliable Wi-Fi, you wear a device that lets you into your room, that discreetly tracks your move from the bar to the dinner table to the pool and delivers your drink order wherever you are. You can buy sunscreen or toothpaste or souvenirs in the ship's stores without touching anything. If you're a Carnival Cruise Lines passenger, this is reality right now, in part because of the company's partnership with Couchbase, according to Mark Gamble, product and solutions marketing director, Couchbase. Couchbase provides a cloud native, no SQL database technology that's used to power applications for customers including Carnival but also Amadeus, Comcast, LinkedIn, and Tesco. In Carnival's case, Gamble said, “they run an edge data center on their ships to power their Ocean Medallion application, which they are super proud of. They use it a lot in their ads, because it provides a personalized service, which is a differentiator for them to their customers.” In this episode of The New Stack Makers, Gamble spoke to Heather Joslyn, features editor of TNS, about edge computing, 5G, and Couchbase Capella, its Database as a Service (DBaaS) offering for enterprises. This episode of Makers was sponsored by Couchbase.5G and Offline-First AppsThe goal of edge computing, Gamble told our podcast audience, is bring data and compute closer to the applications that consume it. This speeds up data processing, he said, “because data doesn't have to travel all the way to the cloud and back.” But it also has other benefits “This serves to make applications more reliable, because local data processing sort of removes internet slowness and outages from the equation,” he said. The innovation of 5G networks has also had a big impact on reducing latency and increasing uptime, Gamble said. “To compare with 4G, things like the average round trip data travel time between the device, and the cell tower is like 15 milliseconds. And with 5G, that latency drops to like two milliseconds. And 5G can support they say, a million devices, within a third of a mile radius, way more than what's possible with 4G.” But 5G, Gamble said, “really requires edge computing to realize its its full potential.” Increasingly, he said, Couchbase hears interest from its customers in building “offline-first” applications, which can run even in Wi-Fi dead zones. The use cases, he said, are everywhere: “When I pass a fast food restaurant, it's starting to become more common, where you'll see that, instead of just a box you're talking to, there's a person holding a tablet, and they walk down the line, and they're taking orders. And as they come closer to the restaurant, it syncs up with the kitchen. They find that just a better, more efficient way to serve customers. And so it becomes a competitive differentiator forum.” As part of Couchbase's Capella product, it recently announced Capella App Service, a new capability for mobile developers, is a fully managed backend designed for mobile, Internet of Things (IoT) and edge applications. “Developers use it to access and sync data between the Database as a Service and their edge devices, as well as it handles authenticating and managing mobile and edge app users,” he said. Used in conjunction with Couchbase Lite, a lightweight, embedded NoSQL database used with mobile and IoT devices, Capella App Services synchronizes the data between backend and edge devices. Even for workers in remote areas, “eventually, you have to make sure that data updates are shared with the rest of the ecosystem,” Gamble said. “ And that's what App Services is meant to do, as conductivity allows — so during network disruptions in areas with no internet, apps will still continue to operate.” Check out the rest of the conversation to learn more about edge computing and the challenges Gamble thinks still need to be addressed in that space.

The brains behind Couchbase's leading data platform, CTO Ravi Mayuram, joins me on Tech Talks Daily to discuss how businesses can avoid the $8.75m cloud overspend revealed in the company's latest cloud evolution report. Ravi shares that even though companies now view the move to the cloud as inevitable, enterprises are still caught out by issues such as inflexible pricing plans, ineffective management tools, and data not stored where it needs to be. We also explore how businesses can make the cloud live up to its promise and how new tech adoption impacts companies. Despite the current reputation of Web 3.0 being tarnished by Crypto-bros, NFTs, and Mega – Ravi believes there is definite potential for companies to explore blockchain technology. We also talk about how businesses can unlock this potential and what it will mean for data. While it's no surprise that the decentralization concept has extended to the IT industry, business infrastructure must be in place to achieve the benefits. Finally, Ravi shares his thoughts on how the future of IT must mean managing data anywhere, including on the edge, a server, or the cloud

About PerryPerry Krug currently leads the Shared Services team which is focused on building tools and managing infrastructure and data to increase the productivity of Couchbase's Sales and Field organisations.  Perry has been with Couchbase for over 12 years and has served in many customer-facing technical roles, helping hundreds of customers understand, deploy, and maintain Couchbase's NoSQL database technology.  He has been working with high performance caching and database systems for over 15 years.Links Referenced: Couchbase: https://www.couchbase.com/ Perry's LinkedIn: https://www.linkedin.com/in/perrykrug/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is brought to us by our friends at Pinecone. They believe that all anyone really wants is to be understood, and that includes your users. AI models combined with the Pinecone vector database let your applications understand and act on what your users want… without making them spell it out. Make your search application find results by meaning instead of just keywords, your personalization system make picks based on relevance instead of just tags, and your security applications match threats by resemblance instead of just regular expressions. Pinecone provides the cloud infrastructure that makes this easy, fast, and scalable. Thanks to my friends at Pinecone for sponsoring this episode. Visit Pinecone.io to understand more.Corey: InfluxDB is the smart data platform for time series. It's built from the ground-up to handle the massive volumes and countless sources of time-stamped data produced by sensors, applications, and systems. You probably think of these as logs.InfluxDB is programmable and performant, has a common API across the platform, and handles high granularity data–at scale and with high availability. Use InfluxDB to build real-time applications for analytics, IoT, and cloud-native services, all in less time and with less code. So go ahead–turn your apps up to 11 and start your journey to Awesome for free at InfluxData.com/screaminginthecloudCorey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Today's episode is a promoted guest episode brought to us by our friends at Couchbase. Now, I want to start off by saying that this week is AWS re:Invent. And there is Last Week in AWS swag available at their booth. More on that to come throughout the next half hour or so of conversation. But let's get right into it. My guest today is Perry Krug, Director of Shared Services over at Couchbase. Perry, thanks for joining me.Perry: Hey, Corey, thank you so much for having me. It's a pleasure.Corey: So, we're recording this before re:Invent, so the fact that we both have, you know, personality and haven't lost our voices yet should probably be a bit of a giveaway on this. But I want to start at the very beginning because unlike people who are academically successful, I tend to suck at doing the homework, across the board. Couchbase has been around for a long time. We've seen the company do a bunch of different things, most importantly and notably, sponsoring my ridiculous nonsense for which I thank you. But let's start at the beginning. What is Couchbase?Perry: Yeah, you're very welcome, Corey. And it's again, it's a pleasure to be here. So, Couchbase is an enterprise database company at the very top level. We make database software and we distribute that to our customers. We have two flavors, two ways of getting your hands on it.One is the kind of legacy, what we call self-managed, where you the user, the customer, downloads the software, installs it themselves, sets it up, manages the cluster monitoring, scaling all of that. And that's, you know, a big part of our business. Over the last few years we've identified, and certainly others in the industry have, as well the desire for users to access database and other technology in a hosted Software-as-a-Service pay-as-you-go, cloud-native, buzzword, et cetera, et cetera, vehicle. And so, we've released the Couchbase Capella, which is our fully managed, fully hosted database-as-a-service, running in—currently—Amazon and Google, soon to be Azure as well. And it wraps and extends our core Couchbase Server product into a, as I mentioned, hosted and managed platform that our users can now come to and consume as developers and build their applications while leaving all of the operational and administration—monitoring, managing failover expansion, all of that—to us as the experts.Corey: So, you folks are non-relational database, NoSQL in the common parlance, which is odd because they call it NoSQL, yet. They keep making more of them, so I feel like that's sort of the Hollywood model where okay, that was so good. We're going to do it again. Where did NoSQL come from? Because back when I was learning databases, when dinosaurs roamed the earth, it was all about relational models, like we're going to use a relational database because when the only tool you have is an axe, every problem looks like hours of fun. What gave rise to this, I guess, Cambrian explosion that we've seen of NoSQL options that proliferate o'er the land?Perry: Yeah, a really, really good question, and I like the axe-throwing metaphor. So sure, 20, 30, 40 now years ago, as digital applications needed a place to store their data, the world invented relational databases. And those were used and continue to be used very well for what they were designed for, for data that follows a very strict structure that doesn't need to be served at significant scale, does not need to be replicated geographically, does not need to handle data coming in from different sources and those sources changing their formats of things all the time. And so, I'm probably as old as you are and been around when the dinosaurs were there. We remember this term called ‘Web 2.0.' Kids, you're going to have to go look that up in the dictionary or TikTok it or something.But Web 2.0 really was the turning point when websites became web applications. And suddenly, there was the introduction of MySpace and Facebook and Amazon and Google and LinkedIn, and a number of others, and they realized that relational databases we're not going to meet their needs, whether it be performance, whether it be flexibility, whether it be changing of data models, whether it be introducing new features at a rapid pace. They tried; they stretched them, they added a bunch of different databases together, and really was not going to be a viable solution. So, 10 now, maybe 15 years ago, you started to see the rise of these tech giants—although we didn't call them tech giants back then but they were the precursors to today's—invent their own new databases.So, Amazon had theirs, Google has theirs, LinkedIn, and a number of others. These companies had reached a level of scale and reached a level of user base, had reached a level of data requirement, had reached a level of expectation with their customers. These customers, us, the users, us consumers, we expect things to be fast, we expect them to be always available. We expect Facebook to give us our news feed in milliseconds. We expect Google to give us our website or our search results in immediate, with more and more information coming along with them.And so, it was these companies that hit those requirements first. The only solution for them was to start from scratch and rewrite their own databases. Fast forward five, six, seven years, and we as consumers turned around and said, “Look, I really liked the way Facebook does things. I really like the way Google does things. I really like the way Amazon does things.“Bank of America, can you do the same? IRS, can you do the same? Health care vendor number one, two, three, and four, government body, can you all give me the same experience? I want my taxi to tell me exactly where it's going to take me from one place to another, I want it to give me a receipt immediately after I finish my ride. Actually, I want to be able to change my payment method after I paid for that ride because I used the wrong one.”All of these are expectations that we as consumers have taken from the tech giants—Apple, LinkedIn, Facebook—and turned around to nearly every other service that we interact with on a daily basis. And all of a sudden, the requirements that Facebook had, that Google had, that no other company had, you know, outside of the top five, suddenly were needed by every single industry, nearly every single company, in order to be competitive in their markets.Corey: And there's no way to scale relational to get to a point where it can wind up handling those type workloads efficiently?Perry: Correct, correct. And it's not just that the technology cannot do it—everything is technically feasible—but the cost both financially and time-to-market-wise in order to do that in a relational database was untenable. It either cost too much money, or it costs too much developers time, or cost too much of everybody's time to try to shoehorn something into it. And then you have the rise of cloud and containers, which relational databases, you know, never even had the inkling of a thought that they might need to be able to handle someday. And so, these requirements that consumers have been placed on everything else that they interact with really led to the rise of NoSQL as a commodity or as a database for the masses.LinkedIn is not in the business of developing a database and then selling it to everybody else to use as a database, right? They built it for themselves, they made their service better. And so, what you see is some of those founding fathers created databases, but then had no desire to sell them to others. And then after that followed the rise of companies like Couchbase and a number of others who said, “Look, we think we can provide those capabilities, we think we can meet those requirements for everybody.” And thereby rose the plethora of NoSQL databases because everybody had a little bit different of an approach to it.If you ask ten people what NoSQL is about, you're going to get eleven or twelve different answers. But you can kind of distill that into two categories. One is performance and operations. So, I need it to be faster, I need it to be scalable, I need it to be replicated geographically. And that's what NoSQL is to me. And that's the right answer.And so, you have things like Cassandra and Redis that are meant to be fast and scalable and replicated. You ask another group and they're going to tell you, “No, no, no. NoSQL needs to be flexible. I need to get rid of the rigid database schemas, I need to bring JSON or other data formats in and munge all this data together and create something cool and new out of it.” And thereby you have the rise of things like MongoDB, who focused nearly exclusively on the developer experience of working with data.And for a long time, those two were in opposite camps, where you have the databases that did performance and the databases that did flexibility. I'm not here to say that Couchbase is the ultimate kitchen sink for everything, but we've certainly tried to approach both of those challenges together so that you can have something that scales and performs and can be flexible enough in data model. And everybody else is trying to do the same thing, right? But all these databases are competing for that same nirvana of the best of both worlds.Corey: And it almost feels like there's a convergence play in place where everything now is trying to go away from the idea of, “Oh, yeah, we started off as a purpose-built database, but you can use this for everything.” And I don't necessarily know that is going to be the path that a lot of companies want to go down. What do you view Couchbase as I guess, falling down? In other words, what workloads is Couchbase inappropriate for?Perry: Yeah, that's a good question. And my [crosstalk 00:10:35]—Corey: Anyone who can't answer that one is a zealot and that's one of those okay, let's be very careful and not take our eyes off you for one second, while smiling and backing away slowly.Perry: Let's cut to commercial. No, I mean, there certainly are workloads that you know, in the past, we've not been good for that we've made improvements to address. There are workloads that we had not address well today that we will try to address in the future, and there are workloads that we may never see as fitting in our wheelhouse. The biggest category group that comes to mind is Couchbase is not an archival database. We are not meant to have data put in us that you don't care about, that you don't want to—that you just need to keep it around, but you don't ever need to access.And there are systems that do that well, they do that at a solid total cost of ownership. And Couchbase is meant for operational data. It's meant for data that needs to be interacted with, read and/or written, at scale and at a reasonable performance to serve a user-facing or system-facing application. And we call ourselves a general-purpose database. Bongo and others call themselves as well. Oracle calls itself a general-purpose database, and yet, not everybody uses Oracle for everything.So, there are reasons that you—Corey: Who could afford that?Perry: Who could? Exactly. It comes down to cost, ultimately. So, I'm not here to say that Couchbase does everything. We like to think, and we're trying to target and strive towards an 80%, right? If we can do 80% of an application or an organization's workloads, there is certainly room for 20% of other workloads, other applications, other requirements that can be met or need to be met by purpose-built databases.But if you rewind four or five years, there was this big push towards polyglot persistence. It's a buzzword that came and kind of has gone out of fashion, but it presented the idea that everybody is going to use 15 different databases and everybody is going to pick the right one for exactly the workload and they're going to somehow stitch them all together. And that really hasn't come to fruition either. So, I think there's some balance, where it's not one to rule them all, but it's also not 15 for every company. Some organizations just have a set of requirements that they want to be met and our database can do that.Corey: Let's continue our tour of the competitive landscape here now that we've handled the relational side of the world. The best database, as anyone who's listened to this show knows, is of course, Amazon's Route 53 TXT records stuffed into DNS, especially in the NoSQL land. Clearly, you're all fighting for second place after that. How do you stack up against the idea of legitimately using that approach? And for those who are not in on the joke, please don't do this. It is not the right answer. But I'm curious to get your take as to why DNS TXT records are an inappropriate NoSQL option.Perry: Well, it's a joke, right? And let's be clear about that. But—Corey: I have to say that because otherwise, someone tries it in production. I've gotten that wrong a few times, historically, so now I put a disclaimer in because yeah, it's only funny, so long as people are in on the joke. If not, and I lead someone down the primrose path to disaster, I feel bad. So, let's be very clear. We're kidding.Perry: And I'm laughing. I'm laughing here behind the camera. I am. I am.Corey: Yeah.Perry: So, the element of truth that I think Couchbase is in a position, or I'm in a position to kind of talk about is, 12 years ago, when Couchbase started, we were a key-value database and that's where we saw the best part of the market in those days, and where we were able to achieve the best scale and replication and performance, and fairly quickly realized that simple key-value, though extremely valuable and easy to manage, was not broad enough in requirements-meeting. And that's where we set our sights on and identified the larger, kind of, document database group, which is really just a derivative of key-value, where still everything is a key and a value; it's just now a document that you can reason about, that you can create an index on, that you can query, that you can run full-text search on, you can do much more with the data. So, at our core, we are still a key-value database. When that value is JSON, we become a document database. And so, if Route 53 decided that they wanted to enter into the document database market, they would need to be adding things that allowed you to introspect and ask questions of the data within that text which you can't, right?Corey: Well, not with that attitude. But yeah, I agree with you.Perry: [laugh].Corey: Moving up the stack, let's talk about a much more fearsome competitor here that I'm certain you see an awful lot of deals that you wind up closing, specifically your own open-source product. You historically have wound up selling software into environments, I believe, you referred to as your legacy offering where it's the hosted version of your commercial software. And now of course, you also have Capella, your cloud-hosted version. But open-source looks surprisingly compelling for an awful lot of use cases and an awful lot of folks. What's the distinction?Perry: Sure. Just to correct a little bit the distinction, we have Couchbase Server, which we provide as a what we call self-managed, where you can download it and install it yourself. Now, you could do that with the open-source version or you could do that with our Enterprise Edition. What we've then done is wrapped that Enterprise Edition in a hosted bottle, and that's Capella. So, the open-source version is something we've long been supporters of; it's been a core part of our go-to-market for the last 12 or 13 years or so and we still see it as a strong offering for organizations that don't need the added features, the added capabilities, don't need the support of the experts that wrote the software behind them.Certainly, we contribute and support our community through our forums and Discord and other channels, but that's a very big difference than two o'clock in the morning, something's not working and I need a ticket to track. We don't do that for our community edition. So, we see lots of users downloading that, picking it up building it into their applications, especially applications that are in their infancy or are with organizations that they simply can't afford the added cost and therefore they don't get the added benefit. We're not here to gouge and carve out every dollar that we can, but if you need the benefit that we can provide, we think there's value in that and that's what we're trying to run a business as.Corey: Oh, absolutely. It doesn't work when you're trying to wind up charging a license fee for something that someone is doing in their spare time project for funsies just to learn the technology. It's like, and then you show up. It's like, “That'll be $700. Surprise.”Yeah, that's sort of the AWS billing model approach, where—it's not a viable onramp for most folks. So, the open-source direction down there make sense. Counterpoint. If you're running a bank on top of it, “Well, we're running it ourselves and really hoping for the best. I mean, we have access to the code and all.” Great, but there are times you absolutely want some of the best minds in the world, with respect to that particular product, able to help troubleshoot so the ATM start working again before people riot in the streets.Perry: Yeah, yeah. And ultimately, it's a question of core competencies. Are you an organization that wants to be in the database development market? Great, by all means, we'd love to support you in that. If you want to focus on doing what you do best be at a bank or an e-commerce website, you worry about your application, you let us worry about the database and everybody gets along very well.Corey: There's definitely something to be said for outsourcing some of the pain, some of the challenge around an awful lot of it.Perry: There's a natural progression to the cloud for that and Software-as-a-Service, database-as-a-service where you're now outsourcing even more by running on our hosting platform. No longer do you have to download the binary and install yourself, no longer do you have to setup the cluster and watch it in case it has a blip or the statistic goes up too far. We're taking care of that for you. So yes, you're paying for that service, but you're getting the value of not having to be a database manager, let alone database developer for them.Corey: Love how serverless helps you scale big and ship fast, but hate debugging your serverless apps? With Lumigo's serverless observability, it's fast and easy (and maybe a little fun, too). End-to-end distributed tracing gives developers full clarity into their most complex serverless and containerized applications, connecting every service from AWS Lambda and Amazon ECS to DynamoDB, API Gateways, Step Functions and more. Try Lumigo free and debug 3x faster, reduce error rate and speed up development. Visit snark.cloud/lumigo That's snark.cloud/L-U-M-I-G-OCorey: What is the point of distinction between Couchbase Server and Couchbase Capella? To be clear, your self-hosted versus managed cloud offerings. When is one appropriate versus the other?Perry: Well, I'm supposed to say that Capella is always the appropriate choice, but there are currently a number of situations where Capella is not available in particular regions or cloud providers and so downloading running the software yourself certainly in your own—yes, there are people who still run their own data centers. I know it's taboo and we don't like to talk about that, but there are people who have on-premise. And so, Couchbase Capella is not available for them. But Couchbase Server is the original Couchbase database and it is the core of Couchbase Capella. So, wrapping is not giving it enough credit; we use Couchbase Server to power Couchbase Capella.And so, there's an enormous amount of value added around the core database, but ultimately, it's the behind the scenes of Couchbase Capella. Which I think is a nice benefit in that when an application is connecting to either one, it gets the same experience. You can point an application at one versus the other and because it's the same database running behind the scenes, the behavior, the data model, the query language, the APIs are all the same, so it adds a nice level of flexibility four customers that are either moving from one to another or have to have some sort of hybrid approach, which we see in the market today.Corey: Let's talk economics for a second. I can see scenarios where especially you have a high volume environment where you're sending tremendous amounts of data back and forth and as soon as it crosses an availability zone boundary or a region boundary, or God forbid, goes out to the internet via standard egress fees over in AWS-land, there's a radically different economic modeling that comes into play as opposed to having something in the same availability zone, in the same subnet just where that—or all traffic back and forth is free. Do you see that in your customer base, that that is a model that is driving people towards self-hosting?Perry: No. And I'd say no because Capella allows you to peer and run your application in the same availability zone as the as a database. And so, as long as that's an option for you that we have, you know, our offering in the right region, in the right AZ, and you can put your application there, then that's not a not an issue. We did have a customer not too long ago that didn't set that up correctly, they thought they did, and we noticed some high data transfer charges. Again, the benefit of running a hosted service, we detected that for them and were able to turn around and say, “Hmm, you might want to change this to over there so that we all save some money in doing so.”If we were not there watching it, they might not have noticed that themselves if they were running it self-managed; they might not have known what to do about it. And so, there's a benefit to working with us and using that hosted platform that we can keep an eye out. And we can apply all of our learning and best practices and bug fixes, we give that to everybody, rather than each person having to stumble across those hurdles themselves.Corey: That's one of those fun, weird corner-case trivia things about AWS data transfer. When you're transferring data within the same region between availability zones, it costs a penny on the sending side and a penny on the receiving side. Everything else is one side or the other that winds up getting the charge. And what makes this especially fun is that when it shows up on your bill, if you transfer a petabyte, it shows as cross-AZ data transfer: two petabytes.Perry: Two. Yeah.Corey: So, it double-counts so they can bill for it appropriately, but it leads to some really weird hunting it down, like, “Okay, well, we found half of it, but where's the other half hiding?” It's always obnoxious to trace this stuff down. The fact that you see it on your bill, well, that's testament to the fact that yeah, they're using the service. Good for them and good for you. Being able to track it down on a per-customer basis that does speak to your level of insight into what exactly is going on in your environment and where. As someone who does this for a living, let me confirm that is absolutely non-trivial.Perry: No, definitely not trivial. And you know, we've learned over the last four or five years, we've learned an enormous amount about how cloud providers work, how AWS works, but guess what, Google does it completely differently. And Azure does it—Corey: Yep.Perry: —completely differently. And so, on the surface level, they're all just cloud providers and they give you a VM, and you put some stuff on it, but integrating with the APIs, integrating with the different systems and naming of things, and then understanding the intricacies of the ins and outs, and, yeah, these cloud providers have their own bugs as well. And so, sometimes you stumble across that for them. And it's been a significant learning exercise that I think we're all better off for, having Couchbase gone through it for you.Corey: Let's get this a little bit more germane for this week for those of you who are listening to this during re:Invent. You folks are clearly here at the show—it's funny to talk about ‘here,' even though when we're recording this, it is not near here; we're actually home and enjoying ourselves, but welcome to temporal dislocation; here we are—here at the show, you folks are—among other things—being kind enough to pass out the Last Week in AWS swag from your booth, which, thank you. So, that is obviously the primary reason that you were at the show. What are the other reasons? What are the secondary reasons that you decided to come here?Perry: Yeah [laugh]. Well, I guess I have to think about this now since you already called out the primary reason.Corey: Exactly. Wait, we can have more than one reason for things? My God.Perry: Can we? Can we? AWS has long been a huge partner of ours, even before Capella itself was released. I remember sometime in, you know, five years or so ago, some 30% of our customers were running Couchbase inside of AWS, and some of our largest were some of your largest at times, like Viber, the messaging platform. And so, we've always had a very strong relationship with AWS, and the better that we can be presenting ourselves to your customers, and our customers can feel that we are jointly supporting them, the better. And so, you know, coming to re:Invent is a testament to that long-standing and very solid partnership, and also it's meant to get more exposure for us to let it be clear that Couchbase runs very well on AWS.Corey: It's one of those areas where when someone says, “Oh yeah, this is a great service offering, but it doesn't run super well on AWS.” It's like, “Okay, so are you bad computers or is what you have built so broken and Byzantine that it has to live somewhere else?” Or occasionally, the use case is absolutely not supported by AWS. Not to beat them up some more on their egress fees, but I'm absolutely about to if you're building a video streaming site, you don't want it living in AWS. It won't run super well there. Well, it'll run well, it'll just run extortionately expensively and that means that it's a non-starter.Perry: Yeah, why do you think Netflix raises their fees?Corey: Netflix, to their credit, has been really rather public about this, where they do all of their egress via their Open Connect, custom-built CDN appliances that they drop all over the place. They don't stream a single byte from AWS, and we know this from the outside because they are clearly still solvent.Perry: [laugh].Corey: I do the math on that. So, if I had been streaming at on-demand prices one month with my Netflix usage, I would have wound up spending four times my subscription fee just in their raw costs for data transfer. And I have it on good authority that is not just data transfer that is their only bill in the entire company; they also have to pay people and content and the analytics engine and whatnot. And it's kind of a weird, strange world.Perry: Real estate.Corey: Yeah. Because it's one of those strange stories because they are absolutely a showcase customer for AWS. They've been a marquee customer trotted out year after year to talk about what they're doing. But if you attempt to replicate their business purely on top of AWS, it will not work. Full stop. The economics preclude that happening.What is your philosophy these days on what historically has felt like an existential threat to most vendors that I've spoken to in a variety of ways: what if Amazon decides to enter your market? I'd ask you the same thing. Do you have fears that they're going to wind up effectively taking your open-source offering and turning it into Amazon Basics Couchbase, for lack of a better term? Is that something that is on your threat radar, or is that not really something you concern yourselves about?Perry: So, I mean, there's no arguing, there's no illusion that Amazon and Google and Microsoft are significant competitors in the database space, along with Oracle and IBM and Mongo and a handful of others.Corey: Anything's a database if you hold it wrong.Perry: This is true. This specific point of open-source is something that we have addressed in the same ways that others have addressed. And that's by choosing and changing our license model so that it precludes cloud providers from using the open-source database to produce their own service on the back of it. Let me be clear, it does not impact our existing open-source users and anybody that wants to use the Community Edition or download the software, the source code, and build it themselves. It's only targeted at Amazon because they have a track record of doing that to things like Elastic and Redis and Mongo, all of whom who have made similar to Couchbase moves to prevent that by the licensing of the open-source code.Corey: So, one of the things I do see at re:Invent every year is—and I believe wholeheartedly this comes historically from a lot of AWS's requirements for vendors on the show floor that have become public through a variety of different ways—where you for a long time, you are not allowed to mention multi-cloud or reference the fact that you work on any other cloud provider there. So, there's been a theme of this is why, for whatever it is we sell or claim to sell or hope one day to sell, AWS is the absolute best place for you to run it, full stop. And in some cases, that's absolutely true because people build primarily for a certain cloud provider and then when they find customers and other places, they learn to run it over there, too. If I'm approaching this from the perspective of I have a database problem—because looking at my philosophy on databases is hard to imagine I don't have database problems—then is my experience going to be better or even materially different between any of the cloud providers if I become a Couchbase Capella customer?Perry: I'd like to say no. We've done our best to abstract and to leverage the best of all of the cloud providers underneath to provide Couchbase in the best form that they will allow us to. And as far as I can see, there's no difference amongst those. Your application and what you do with the data, that may be better suited to one provider or another, but it's always been Couchbase is philosophy—sort of say, strategy—to make our software available to wherever our customers and users want to, to consume it. And that goes everything from physical hardware running in a data center, virtual machines on top of that, containers, cloud, and different cloud providers, different regions, different availability zones, all the way through to edge and other infrastructures. We're not in a position to say, “If you want Couchbase, you should use AWS.” We're in a position to say, “If you are using AWS, you can have Couchbase.”Corey: I really want to thank you for being so generous with your time, and of course, your sponsorship dollars, which are deeply appreciated. Once again, swag is available at the Couchbase booth this week at re:Invent. If people want to learn more and if for some unfathomable reason, they're not at re:Invent, probably because they make good life choices, where can they go to find you?Perry: couchbase.com. That'll to be the best place to land on. That takes you to our documentation, our resources, our getting help, our contact pages, directly into Capella if you want to sign in or login. I would go there.Corey: And we will, of course, put links to that in the show notes. Thank you so much for your time. I really appreciate it.Perry: Corey, it's been a pleasure. Thank you for your questions and banter, and I really appreciate the opportunity to come and share some time with you.Corey: We'll have to have you back in the near future. Perry Krug, Director of Shared Services at Couchbase. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry and insulting comment berating me for being nowhere near musical enough when referencing [singing] Couchbase Capella.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Having trouble with understanding your team's productivity outside of frameworks and tooling? Create a backlog and work through it: Instant Agile! How much of that backlog you work through is a good baseline measure. The Stack Overflow blog recently featured an article from Stack Overflow's Director of Engineering, Ben Matthews: Does high velocity lead to burnout? That may be the wrong question to askIf you're interested in seeing how Couchbase's SQL database solutions can help improve your team's velocity, check out Capella.  Cory House helps teams deliver successful React projects through his consulting business, ReactJS Consulting.  If you want to learn more about Matt, check out his LinkedIn.Congrats to Lifeboat badge winner, Alohci, who threw a great answer to rescue the question, Display button with  inline CSS.

Hi, Spring fans! In this installment, Josh Long (@starbuxman) talks to his friend, fellow Java Champion, and director of developer relations and strategy at Couchbase, Laurent Doguin (@ldoguin)

In this episode, I got to talk with Ravi Mayuram, CTO at Couchbase. From edge persistence and self healing databases to quantum computing, we got to chat about a range of the trends he's been seeing in the data persistence space.PARTNERThanks to our partner CloudZero — Cloud Cost Intelligence Platform. Control cost and drive better decisions with CloudZero cloud cost intelligence. The CloudZero platform provides visibility into cloud spend without the typical pitfalls of legacy cloud cost management tools, like endless tagging or clunky Kubernetes support. Optimize unit economics, decentralize cost data to engineering, and create a shared language between finance and technical teams. CloudZero helps you organize cloud spending better than anyone else.Join companies like Drift, Rapid7, and SeatGeek by visiting cloudzero.com/ctoconnection to get started.

As business leaders look at developing digital strategies to create better customer experiences, they are struggling with a shortage of talent with the right IT skills to implement and manage these technologies. Stuart Fisher, Regional Vice President, Asia Pacific and Japan for Couchbase talks to us about investing in mobile technology to bridge the APAC talent gap, and deliver unmatched customer experiences.Image Credit: Shutterstock | LookerStudio

Couchbase is a distributed NoSQL cloud database. Since its creation, Couchbase has expanded into edge computing, application services, and most recently, a database-as-a-service called Capella.  Couchbase started as an in-memory cache and needed to be rearchitected to be a persistent storage system. In this episode, We interviewed Ravi Mayuram, SVP Products, and Engineering at Couchbase. The post Couchbase Architecture with Ravi Mayuram appeared first on Software Engineering Daily.

Couchbase is a distributed NoSQL cloud database. Since its creation, Couchbase has expanded into edge computing, application services, and most recently, a database-as-a-service called Capella.  Couchbase started as an in-memory cache and needed to be rearchitected to be a persistent storage system. In this episode, We interviewed Ravi Mayuram, SVP Products, and Engineering at Couchbase. The post Couchbase with Ravi Mayuram appeared first on Software Engineering Daily.

In this podcast episode, you will learn:According to Insik, what are the values, skillsets and dynamics of a great team? What should be the ideal size of a founding team?What are some things that the startup founders don't understand about VCs?When should startups think about forming a board, what is the role of the board and who should be a part of it?What is the role of a board member and an advisor?How does Insik assess a company that works with data; for example, a company working on data security for the cloud?What is an investment thesis and how do you come up with it? Do investors really need an investment thesis?What is the reason for the current VC funding winter and why a correction like this is needed for the startup ecosystem?AboutInsik is a General Partner at Vertex Ventures US and is a former founder of Loudcloud and Kiva Software, companies that helped shift enterprise technology categories. At Vertex US, he works with founders who are pursuing advancements in data science and machine learning, enterprise process automation, and real-time infrastructure.Prior to Vertex US, Insik served as General Partner at Rembrandt Venture Partners where he led investments in A Bit Lucky (acquired by Zynga), CloudOn (acquired by Dropbox), and Ooyala (acquired by Telstra). Before that, he was a Partner at Accel Partners, here investing and advising companies including Cloudera, Couchbase, Facebook, Mochi Media (acquired by Shanda), and Terracotta (acquired by Software AG).As the Co-founder and Chief Tactician of Loudcloud, which later was renamed Opsware, Insik helped create the cloud computing paradigm and the data center automation software category.Loudcloud IPO'ed and then was acquired by HP in 2007. His first company, Kiva Software created the Application Server Market market. Enterprises such as E*Trade, Bank of America, and Wells Fargo developed their first online sites using Kiva. Netscape acquired Kiva in 1997 for $180 million.He is currently on the boards of Testlio, Interana, Zepl, Cyberhaven, Evisort and Upsolver and holds a B.S. in Electrical Engineering and Computer Science from UC Berkeley and currently serves on the university's Executive Advisory Board for the College of Engineering. 

Databases are exciting! Matt Cain, the CEO of Couchbase, contends that databases are right in the middle of digital transformation and that this reality provides great meaning to Couchbase's work. Tune in to learn about Matt's position that leaders must first look inside themselves to uncover the best way for them to lead.  Main Takeaways: Technology in the Family: Matt shares how his parents and grandmother worked at HP for many years, and he mentions the great culture at HP. He talks in more detail about how he learned valuable business lessons from his father's leadership experience at HP. The Tesla of Databases: Matt explains how Couchbase views its work via an apt metaphor: “We think about our approach to databases like Tesla approached cars.” He describes how just like Tesla builds cars, Couchbase builds its database. But he then goes further to explain how Couchbase has innovated databases in a similar manner that Tesla has innovated cars. According to him, Tesla's cars and Couchbase's database may look like other cars and databases, respectively, but their capabilities may be quite different from other traditional products. Becoming a Great Leader: Does learning about leadership come more from external sources or a person's self-knowledge? Matt believes that a process of self-discovery is the best way to grow as a leader. It's a strong position but holds true. Without self-awareness, acting on constructive external information will be difficult. With self-awareness, necessary leadership adjustments can be understood and implemented. Self Care: Leaders can only be effective if their own well-being is maintained. Matt describes how he takes care of himself by exercising and having supportive peers to lean on. He shares how there can be a level of what he describes as “loneliness” connected to being a leader and how it has been helpful to discuss the difficulties that come with leadership and life with close peers.  Being in the Middle of Digital Transformation: Data is everywhere and an intrinsic part of digital transformation. Matt describes databases as a central aspect of this change. This puts Couchbase in an ideal position to make a substantial impact with their work.   Key Quotes: [26:32] “My vision is a coach. We take the field together. If we're bought into a common vision and we all play our roles, great things can happen.” [12:28] “We think about our approach to databases like Tesla approached cars. If you think about Tesla, what did they do? Well, there's still a gas pedal and a brake pedal and a steering wheel, and then the car still needs to go forward and backward and left and right, but under the hood it's a completely different approach. Couchbase is very similar [in] that under the hood of our database, our engine or our data model has a very flexible schema and command of structured and unstructured information that allows these applications to perform. And no longer is it these large monolithic applications, but it's this microservice based personalized applications at scale, where instead of managing terabytes of information, you've got petabytes of information that are constantly changing and accessed by thousands of different users.”  [27:28] “And what I would encourage people to do is say, ‘Where have I been successful in my life? And what led to that success?' That's the person I am. You don't have to be someone else. So I would say put down the book that says, ‘Here's how you need to do it.' And instead spend some time inside and reflect on where have you been successful and why, and use that and be who you are. And that is how I think you're going to get the most out of your leadership.”  [32:18] “People often ask, ‘How do you describe the CEO job?' And I say, ‘It's Chief Strategy Officer, Chief Culture Officer, and Chief Worry Officer.' And no one talks about the third… There is a loneliness that comes with it that at the end of the day, most decisions after all the input that you've taken to the world come down to a person making a call.”  [37:35] “We think we are in the very early innings of digital transformation… Think about how we shop, how we travel, how we entertain ourselves, [and] how we receive healthcare. It's going to be fundamentally different. And we're only getting started on how technology is going to shape those industries… The critical path of enabling all that is databases. And so if you look at the 60 plus billion dollars that are spent on databases, that does not include the adjacent areas like what's happening at the edge and analytics and other technologies that make that happen. The makeup of that spend and what it's going to enable is going to be fundamentally different. And so to be a player in that at scale that can continue to innovate and shape the future, I mean, that's the gift that not many people get to be a part of, and we at Couchbase take that very seriously.” [45:30] “I'm a big believer that if you stay committed to something and you work hard and you apply the gifts that you've been given, you can shape your life in the direction you want to — understanding what that passion is and the impact of the decisions you're making. Just be conscious about the life that you're choosing. And if you're aligned with that and the outcome is what you expect it to be and based on what drives [you], you're going to be fulfilled. Fulfillment should be the measure of success.”

Today's guest is Ravi Mayuram, Chief Technology Officer and Senior Vice President of Engineering at Couchbase in Santa Clara, CA. Founded in 2009, Couchbase believes data is at the heart of the enterprise. They empower developers and architects to build, deploy and run their mission-critical applications. Couchbase delivers a high-performance, flexible and scalable modern database that runs across the data center and any cloud. Many of the world's largest enterprises rely on Couchbase to power the core applications their businesses depend on. As CTO, Ravi is focused on driving deeper customer and partner relationships and evangelizing Couchbase in the market. He joined Couchbase from Oracle, where he served as senior director of engineering and led innovation in the areas of recommender systems and social graph, search and analytics, and lightweight client frameworks. Ravi was responsible for kickstarting the cloud collaboration platform at Oracle. Previously in his career, Ravi held senior technical and management positions at BEA, Siebel, Informix, HP and startup BroadBand Office. In the episode, Ravi will discuss: What Couchbase is all about, A typical Customer journey and benefits they bring to users, Problems they are solving using AI and Data, What it's like to work at Couchbase, Upcoming projects & what the future holds, & Exciting opportunities to work with Couchbase

2022-06-07 Weekly News - Episode 151Watch the video version on YouTube at https://www.youtube.com/watch?v=CKnPCL8870Q&list=PLNE-ZbNnndB98oRT8THamdCUiyDQL1uEj&index=151 Hosts: Gavin Pickin - Senior Developer at Ortus Solutions Dan Card - Senior Developer at Ortus Solutions Thanks to our Sponsor - Ortus SolutionsThe makers of ColdBox, CommandBox, ForgeBox, TestBox and all your favorite box-es out there. A few ways  to say thanks back to Ortus Solutions: BUY SOME ITB TICKETS - COME TO THE CONFERENCE Like and subscribe to our videos on YouTube.  Help ORTUS reach for the Stars - Star and Fork our Repos Star all of your Github Box Dependencies from CommandBox with https://www.forgebox.io/view/commandbox-github  Subscribe to our Podcast on your Podcast Apps and leave us a review Sign up for a free or paid account on CFCasts, which is releasing new content every week BOXLife store: https://www.ortussolutions.com/about-us/shop Buy Ortus's Book - 102 ColdBox HMVC Quick Tips and Tricks on GumRoad (http://gum.co/coldbox-tips)  Patreon SupportGoal 1 - We have 37 patreons providing 100% of the funding for our Modernize or Die Podcasts via our Patreon site: https://www.patreon.com/ortussolutions. Goal 2 - We are 53% of the way to fully fund the hosting of ForgeBox.io PATREON SPONSORED JOB POSTING!Hagerty - MotorSportReg2 Job Opportunities for Senior Software Engineer, Motorsport - more in the job section.Ready to get in the driver's seat? Join us!https://bit.ly/3985J3U News and AnnouncementsLive Stream Series - Koding with the Kiwi + FriendsStarting this Friday, June 10th, at 1pm PDTGoal is for Weekly Streams - when possibleGavin will be hosting a live stream, for Patreon members only. This stream try to include special guests from the community, to get their viewpoints / advice on how Gavin should do something. We'll be pair programming / talking with Adam Cameron about TDD, Sam Knowlton on Quick/QB, and Wil De Bruin on API documentation and Validation, and others from the Ortus Team and Community too. This week's guest is a surprise, you'll have to tune in to find out.Patreon's check your email, there will be an email sent soon with the registration link for the zoom call.Blog Post with more details coming tomorrow.Not a patreon? Sign up today or wait for us to release the recording on CFCasts after the session.INTO THE BOX - UpdatesThis week we're going to be announcing some attendee perks, like CFCasts, as well as some more sponsors. Last week was full of announcements, and special code and the last workshop selected.Announcing - Into the Box 2022 Podcast SeriesThis podcast is a special podcast for attendees or undecided attendees, to get a view of what the conference has to offer, we'll be interviewing Ortus members organizing the conference, as well as workshop trainers, session speakers and sponsors as well. You'll get all of this information, in short sharp episodes, so you can decide if you want to Into the Box and WHEN you decide you are going, which workshop and sessions will you attend.https://www.intothebox.org/blog/announcing-into-the-box-2022-podcast-series Free Month of CFCasts for all ITB Attendees in Addition to ITB 2022 VideosEvery year, when you are an attendee of Into the Box, you get all of the recordings from the Into the Box Conference you attended made available for future viewing, or reviewing. We have always done this so you don't miss out on all of the amazing content in both tracks at the conference. In addition to that, this year, after Into the Box, we'll also be sending all of the attendees a coupon for 1 month free access to all of the content on CFCasts.http://www.intothebox.org/blog/free-month-of-cfcasts-for-all-itb-attendees-in-addition-to-itb-2022-videos Couchbase - Platinum Sponsor for Into the Box 2022We are excited to announce Couchbase as a Platinum Sponsor at Into the Box 2022. Ortus Solutions has built the Couchbase Extension for Lucee and has been using Couchbase for many years now, to provide lightning fast caching, vital in a clustered environment. Couchbase has continued to grow and expand features and benefits, and we are so happy they are sponsoring Into the Box 2022.http://www.intothebox.org/blog/couchbase-platinum-sponsor-for-into-the-box-2022 Top Secret - Big Announcement coming next week - fingers crossedICYMI - ColdBox BE ready for next release - testers neededHas major refactoring and improvements on wirebox - we have a need for speed!https://ortussolutions.atlassian.net/browse/COLDBOX-1113?jql=project%20%3D%20%22COLDBOX%22%20AND%20fixVersion%20%3D%20%22Current%22https://ortussolutions.atlassian.net/browse/COLDBOX-1107?jql=project%20%3D%20%22WIREBOX%22%20AND%20fixVersion%20%3D%20%22Current%22ICYMI - CBFS is going to be cut any day now - testers neededWe're looking for others to contribute other providers to make it even more powerful.https://www.forgebox.io/view/cbfsNew Releases and UpdatesICYMI - Hyper v3.5.0 is out with:- New `getStatusText()` and `getStatus()` methods- `getMemento()` methods for both `HyperRequest` and `HyperResponse`- And a better `throwOnError` experience showing much more information than `cfhttp` gives you out of the box.https://www.forgebox.io/view/hyper ICYMI - Minor Update to the Lucee Mongo DB Extensionfixes an issue where cache entries with a “last access” timeout would not properly be removed from the cache in a timely manner.fixes an issue where the hit count in the table was incremented twice on each “hit”minor code cleanup (typos in function names)https://dev.lucee.org/t/mongodb-extension-minor-update-3-12-8-132/10254 WEBINARS / MEETUPS AND WORKSHOPSTHIS WEEK - Online CF Meetup - "When Should I Use 3rd Party Libraries vs Roll My Own?", with Gavin PickinThere is always a trade-off between using a 3rd party library and rolling your version in software development. I often hear many of these points in discussions, but I wonder how many people know and consider them, so I wanted to share my pros and cons.This presentation will help convince you that libraries are not EVIL like so many haters believe. Choosing the right libraries will make you more productive and efficient, not lazy. We'll look at how to identify solid use-cases for using a 3rd party library in your application. It gives you a checklist of questions to help you identify the red flags of unsafe, unreliable, poorly supported, or ill-suited libraries.We'll look at some CF Landscape exampleshttps://www.meetup.com/coldfusionmeetup/events/286262739/ Ortus Webinar - June - Getting started with the Legacy Migration with Dan CardJune 24th 2022: Time 11:00 AM Central Time ( US and Canada )We will look at the process of converting legacy .cfm based sites into a more modern coding design which has less overall code, is easier to maintain and manage, mistakes and errors can more readily and speedily identified and fixed, and is easier to read.Registration Link: https://us02web.zoom.us/meeting/register/tZAvceqsqj4vGd2jojyCgn7cUnytPpBeWvV5 View all Webinars: https://www.ortussolutions.com/events/webinars June 2022 Seattle ColdFusion User Group MeetingWe are restarting our Seattle ColdFusion User Group meetings and are looking forward to meeting online with all of you.This month's meeting includes a presentation by Leon O'Daniel on sending SMS messages using ColdFusion and the Twilio API.https://www.meetup.com/Seattle-ColdFusion-User-Group/events/285974950/ Adobe WorkshopsJoin the Adobe ColdFusion Workshop to learn how you and your agency can leverage ColdFusion to create amazing web content. This one-day training will cover all facets of Adobe ColdFusion that developers need to build applications that can run across multiple cloud providers or on-premiseWEDNESDAY, JUNE 15, 20229:00 AM EDTAdobe ColdFusion WorkshopBrian Sappeyhttps://1-day-coldfusion-workshop.meetus.adobeevents.com/ WEDNESDAY, JUNE 22, 20229:00 AM CETAdobe ColdFusion WorkshopDamien Bruyndonckx (Brew-en-dohnx) https://adobe-cf-workshop.meetus.adobeevents.com/ FREE :)Full list - https://meetus.adobeevents.com/coldfusion/ Adobe and Carahsoft workshopsICYMI - Wednesday June 01, 2022Adobe ColdFusion Advanced Workshop CPE credit availableHosted By: Adobe & Carahsofthttps://www.carahsoft.com/learn/event/37899-Adobe-ColdFusion-Advanced-Workshop Tuesday, June 7, 2022Adobe ColdFusion WorkshopCPE credit availableHosted By: Adobe & Carahsofthttps://www.carahsoft.com/learn/event/37401-adobe-coldfusion-workshopCFCasts Content Updateshttps://www.cfcasts.comJust Released LogBox 101 https://cfcasts.com/series/logbox-101Installation and Getting Started - https://cfcasts.com/series/logbox-101/videos/installation-and-getting-started Publish your First ForgeBox Package - https://cfcasts.com/series/publish-your-first-forgebox-package ForgeBox Admin - Dashboard - https://cfcasts.com/series/publish-your-first-forgebox-package/videos/forgebox-admin---dashboard  2022 ForgeBox Module of the Week Series - 3 new Videoshttps://cfcasts.com/series/2022-forgebox-modules-of-the-week 2022 VS Code Hint tip and Trick of the Week Series - 3 new Videoshttps://cfcasts.com/series/2022-vs-code-hint-tip-and-trick-of-the-week  Coming Soon Last couple of videos for Gavin Pickin - Publish Your First ForgeBox Package LogBox 101 from Eric Peterson Box-ifying a 3rd Party Library from Gavin More ForgeBox and VS Code Podcast snippet videos Conferences and TrainingTHIS WEEK - US VueJS ConfFORT LAUDERDALE, FL • JUNE 8-10, 2022Beach. Code. Vue.Workshop day: June 8Main Conference: June 9-10https://us.vuejs.org/Speakers and Schedule Announced https://us.vuejs.org/schedule/ THIS WEEK - Apple WWDCJune 6 to 10https://developer.apple.com/wwdc22/Quasar ConfPlease let us know about you and what you'd like to speak about in all things Quasar or Vue!!!Conference Date: Saturday, July 9th, 2022 - 3 p.m. GMTDeadline for Proposals: June 9th, 2022Call for Proposals - https://docs.google.com/forms/d/e/1FAIpQLSecQfTFUM1BINAvpPl-Khbk7UYpLk2srIR0pLgMcVjpJwWMCA/viewform THAT ConferenceHowdy. We're a full-stack, tech-obsessed community of fun, code-loving humans who share and learn together.We geek-out in Texas and Wisconsin once a year but we host digital events all the time.WISCONSIN DELLS, WI / JULY 25TH - 28TH, 2022A four-day summer camp for developers passionate about learning all things mobile, web, cloud, and technology.https://that.us/events/wi/2022/ Our very own Daniel Garcia is speaking there https://that.us/activities/sb6dRP8ZNIBIKngxswIt Adobe Developer Week 2022July 18-22, 2022Online - Virtual - FreeThe Adobe ColdFusion Developer Week is back - bigger and better than ever! This year, our experts are gearing up to host a series of webinars on all things ColdFusion. This is your chance to learn with them, get your questions answered, and build cloud-native applications with ease.Note: Speakers listed are 2021 speakers currently - check back for updates - I heard speakers were being contacted, and info coming very soon!!! Wink wink nudge nudgehttps://adobe-coldfusion-devweek-2022.attendease.com/registration/form VueJS Forge After many requests - New Dates - July 13th-14thDue to many of you taking advantage of early summer vacations, we have decided to postpone the event to a date that will make sure as many of you as possible won't miss out on the opportunity to attend Vue.js Forge!Organized by Vue School_The largest hands-on Vue.js EventTeam up with 1000s of fellow Vue.js devs from around the globe to build a real-world application in just 2 days in this FREE hackathon-style event.Make connections. Build together. Learn together.Sign up as an Individual or signup as a companyCompany Deal - $2000 for a team of 5, includes VueSchool annual membership and guaranteed seat at the workshops at VueJS Forge as well… and you can pick your teamSneak Peek into the Project: If you've ever wanted to build your own SaaS app, then “the project” is definitely right up your alley! Work with Vue.js, VueUse, Vue Router, and Pinia on the front-end along with a dynamic back-end to create the main application. Also create a marketing site that's easily maintained by a non-technical marketing team, then deploy everything live to the world.https://vuejsforge.com/Into The Box 2022September 6, 7 and 8, 2022One day workshops before the two day conference!Super Early bird pricing ended May 31st, 2022 - Get the early bird price nowConference Website:https://intothebox.orgITB Blog has new updates almost every day!CF Summit - OfficialMirageOct 3rd & 4th - CFSummit ConferenceOct 5th - Adobe Certified Professional: Adobe ColdFusion Certification Classes & Testshttps://cfsummit.adobeevents.com/ Registrations are now open.For just $99!Grab your early-bird tickets before June 30.Call for Speakers is now OpenFrom Slack re Adobe Certified ProfessionalThe Adobe Certified Professional: Adobe ColdFusion cert is a totally different, MUCH more difficult and comprehensive certification than the CF Specialist previously offered. Mark Takata, Nolan and Dave F + the CF engineering team, Elishia and Kishore all spent a week together building the new one and it is HARD. I highly recommend it as a test of your skills, I guarantee everyone will learn something new.Yes, but there's also over 100 hours of video to go over before the 1 day lecture + cert. So you watch videos, sit in class, then take the exam there. It is no joke, definitely challenging, but super satisfying to pass.Plus you get access to those videos for a year, which is nice for going back and reviewing things down the line.Into the Box Latam 2022Dec 7thMore information is coming very soon.CFCampNo CFCAMP 2022, we're trying again for summer 2023TLDR is that it's just too hard and there's too much uncertainty right now.More conferencesNeed more conferences, this site has a huge list of conferences for almost any language/community.https://confs.tech/Blogs, Tweets, and Videos of the Week 6/7/22 - Ben Nadel - Disabling Async Attribute On CFMail For At-Least-Once Delivery In Lucee CFMLWhen I'm sending emails out in a ColdFusion application, not all emails are created equal. Much of the time, if an email is lost here-and-there, it's not the end of the world. For example, a "Forgot My Password" email can always be sent a second time. In critical ColdFusion workflows, however, when losing an email is unacceptable, I track the processing of pending emails in the database; and, I make sure to set the async (Lucee CFML) / spoolEnable (Adobe ColdFusion) attribute on the CFMail tag to false.https://www.bennadel.com/blog/4278-disabling-async-attribute-on-cfmail-for-at-least-once-delivery-in-lucee-cfml.htm 6/7/22 - Peter Amiri - CFWheels - Two New Repositories PublishedWe have published two new repositories named cfwheels/cfwheels-www and cfwheels/cfwheels-api which handle the CFWheels.org landing page site and the api.cfwheels.org API documentation site respectively.https://cfwheels.org/blog/two-new-repositories-published/ 6/6/22 - Peter Amiri - CFWheels - CFWheels DotEnvSettings Plugin publishedA new plugin was published to provide support for .env settings files in a production environment. This plugin is based on Eric Peterson's CommandBox module and allows the use of .env or similarly named files to store your application secrets so they can be kept out of source control.https://cfwheels.org/blog/cfwheels-dotenvsettings-plugin-published/ 6/6/22 - Wil De Bruin - ImageNew bug in LuceeSeveral months ago Eric Peterson published the totp module, a cfml implementation of Time-based One-time Password. I  decided to give the totp module a try. I immediately discovered a bug in the module: the bar codes where not generated correctly. I contacted the author on Slack, and we soon discovered, this was only a problem on Lucee, and apparently it was caused by the ImageNew() function. As I am developing API's most of the time, I never used this function before, and I guess it is not used by many other people.https://shiftinsert.nl/imagenew-bug-in-lucee/ 6/5/22 - Ben Nadel - Adding New Regular Expression Parsing To My JRegEx Project For ColdFusionAs part of the recent Regular Expression Day celebrations, I was working on some fun and exciting ways to parse strings and lists using RegEx patterns in ColdFusion. As a quick follow-up to those joyous outbursts, I've gone and added those new methods to my JRegEx ColdFusion component. In fact, I've added a new JRegExList.cfc component to this project for list-specific parsing - I didn't want to mix the two genres together.https://www.bennadel.com/blog/4277-adding-new-regular-expression-parsing-to-my-jregex-project-for-coldfusion.htm 6/3/22 - Mark Takata - Adobe - CLI Installation of ColdFusion for lower memory useOne of the key feature updates of CF2021 was the addition of modularity to the server. No longer were you limited to just installing the “whole kit and caboodle”, now you could pick and choose your connectors and packages, allowing you a leaner installation. You could, of course, use the GUI installer to get everything in place, then remove the things you didn't need. But the other way to get things in place is to use the Command Line Interface(CLI) to install ColdFusion, and then use the new Package Manager Command Line Interface (PMCLI) to install the packages you need, scan your code to see what packages you need, download packages locally, and much more!https://coldfusion.adobe.com/2022/06/cli-installation-of-coldfusion-for-lower-memory-use/ 6/3/22 - Ortus Solutions - Ortus Content Digest for week of June 3rdWhat has Ortus been publishing this week? We have the Podcast, some CFCasts and YouTube Videos. We have a lot more planned for next week as wellhttps://www.ortussolutions.com/blog/ortus-content-digest-for-week-of-june-3rd?utm_source=contentstudio.io&utm_medium=podcast 6/2/22 - Ortus Solutions - June 2022 Webinar - Getting started with the Legacy Migration with Dan CardWe are happy to announce the Ortus Webinar for June 2022 - Getting started with the Legacy Migration with Dan Cardhttps://www.ortussolutions.com/blog/june-2022-webinar-getting-started-with-the-legacy-migration-with-dan-card?utm_source=contentstudio.io&utm_medium=podcast    6/2/22 - Ben Nadel - Parsing Lists Using A RegEx Delimiter In Lucee CFML 5.3.8.201In honor of yesterday's Regular Expression Day 2022 celebration, I wanted to play around with parsing lists in ColdFusion using a RegEx (Regular Expression) delimiter. Lists are the unsung heroes of the CFML language; and, are usually delimited by a single character (or set of single characters). But, the beauty of a list is that it's just a String; and, you can make a list out of anything using any delimiter. And, sometimes, I'd like that delimiter to be something more flexible, more dynamic. To start exploring this concept, I'm going to create jreListFirst() and jreListRest() functions.https://www.bennadel.com/blog/4275-parsing-lists-using-a-regex-delimiter-in-lucee-cfml-5-3-8-201.htm 6/1/22 - Ben Nadel - The 15th Annual Regular Expression Day - June 1st 2022Happy Regular Expression Day! This is your annual reminder to learn you some Regular Expressions for great good! Pattern matching is a skill that comes with a massive return on investment (ROI). It is no exaggeration that I use ColdFusion and JavaScript Regular Expression (RegEx) functions every single day. Literally! Once you understand how patterns work, you see them everywhere! They are a game changer!https://www.bennadel.com/blog/4274-the-15th-annual-regular-expression-day-june-1st-2022.htm 6/1/22 - Gavin Pickin - Ortus - How to Make Windows Folders Case SensitiveIn the last blog post in this series, we discussed Case Sensitivity on Windows, what is it, why does it matter, and how it could mess up your developer day in ways you never thought of. In this blog post, we're going to show you how to enable case sensitivity in windows, for a given folder, all folders underneath it, and explain how that case sensitivity is inherited, and when it isn't.https://www.ortussolutions.com/blog/how-to-make-windows-folders-case-sensitive?utm_source=contentstudio.io&utm_medium=podcast 6/1/22 - Into the Box - Couchbase - Platinum Sponsor for Into the Box 2022We are excited to announce Couchbase as a Platinum Sponsor at Into the Box 2022.Ortus Solutions has built the Couchbase Extension for Lucee and has been using Couchbase for many years now, to provide lightning fast caching, vital in a clustered environment. Couchbase has continued to grow and expand features and benefits, and we are so happy they are sponsoring Into the Box 2022.https://www.intothebox.org/blog/couchbase-platinum-sponsor-for-into-the-box-2022/?utm_medium=referral&utm_source=podcast Tweet - Charlie Arehart - Good to see - Adobe - Sometimes it's the little things Good to see: Adobe today updated their downloads page with the latest Java versions 11.0.15.1 (vs 11.0.15 added last month) and 8u333 (over 8u331 last month), and also fixed sort order and how filenames are shown. Sometimes it's the little things. #coldfusion #luceehttps://twitter.com/carehart/status/1532021965212499979https://twitter.com/carehart Blog - Adam Tuttle - The Flywheel of TestingOn my continuing quest to get better at testing, I have spent quite a lot of time in the last couple of weeks reading about testing, watching tutorial videos, and practicing testing in my work. It has been a long, slow, difficult, slog. I'm not sure what made me think of it, but I was reminded of a flywheel.https://adamtuttle.codes/blog/2021/the-flywheel-of-testing/ CFML JobsSeveral positions available on https://www.getcfmljobs.com/Listing over 94 ColdFusion positions from 53 companies across 47 locations in 5 Countries.2 new jobs listedFull-Time - ColdFusion Dev at Kovilpatti, Tamil Nadu - India Jun 03https://www.getcfmljobs.com/jobs/index.cfm/india/ColdFusion-Dev-at-Kovilpatti-Tamil-Nadu/11481 Full-Time - Senior Coldfusion Developer WORK |LATAM| at Colon, PA - United States Jun 01https://www.getcfmljobs.com/jobs/index.cfm/united-states/Senior-Coldfusion-Developer-WORK-LATAM-at-Colon-PA/11480 PATREON SPONSORED JOB POSTING!Hagerty - MotorSportRegSenior Software Engineer, MotorsportWe are seeking a Senior Software Engineer to work primarily with Node/Vue.js, ColdFusion, and AWS to improve our platform and build greenfield experiences.We are a 25-person team supporting 1,600 organizations with our SaaS CRM, commerce and event management platform. With 8,000 events managed in our marketplace annually by our customers, our goal is to be the number one software platform for automotive and motorsport events.Ready to get in the driver's seat? Join us!https://bit.ly/3985J3U Other Job Links Ortus Solutionshttps://www.ortussolutions.com/about-us/careers  Clear Capital - Carol from Working Code Podhttps://jobs.jobvite.com/careers/clearcapital/search?j=o7OCjfwA&j=oWVlhfwd&j=oj7Vhfwm&j=oKzjifwE&j=oh43hfwp&j=ol9Jjfwg&j=oEhyjfww&j=oJgCjfwE&j=obZxgfwH&j=o19JjfwW&__jvst=employee&__jvsd=sporQiwR&__jvsc=Url&bid=nTn6s0wj  There is a jobs channel in the cfml slack team, and in the box team slack now too ForgeBox Module of the WeekCFWheels DotEnvSettings PluginThis module reads secrets contained in a .env file (or other file you specify) and loads the values into the CFWheels settings. Based on Eric Peterson's CommandBox Module.https://www.forgebox.io/view/cfwheels-dotenvsettings VS Code Hint Tips and Tricks of the WeekSQL Server Client(mssql)The Database Client makes your life easy. It supports databases MySQL/MariaDB, Microsoft SQL Server, PostgreSQL, SQLite, MongoDB, Redis, and ElasticSearch.https://marketplace.visualstudio.com/items?itemName=cweijan.vscode-myssql-client2 Thank you to all of our Patreon SupportersThese individuals are personally supporting our open source initiatives to ensure the great toolings like CommandBox, ForgeBox, ColdBox,  ContentBox, TestBox and all the other boxes keep getting the continuous development they need, and funds the cloud infrastructure at our community relies on like ForgeBox for our Package Management with CommandBox. You can support us on Patreon here https://www.patreon.com/ortussolutionsDon't forget, we have Annual Memberships, pay for the year and save 10% - great for businesses. Bronze Packages and up, now get a ForgeBox Pro and CFCasts subscriptions as a perk for their Patreon Subscription. All Patreon supporters have a Profile badge on the Community Website All Patreon supporters have their own Private Forum access on the Community Website https://community.ortussolutions.com/ PatreonsNEW PATREON - JORDAN CLARK John Wilson - Synaptrix Brian Ghidinelli - Hagerty MotorsportReg   Eric Hoffman Gary Knight Mario Rodrigues Giancarlo Gomez David Belanger Dan Card Jonathan Perret Jeffry McGee - Sunstar Media Dean Maunder Wil De Bruin Joseph Lamoree Don Bellamy Jan Jannek Laksma Tirtohadi Carl Von Stetten Jeremy Adams Didier Lesnicki Matthew Clemente Daniel Garcia Scott Steinbeck - Agri Tracking Systems Ben Nadel  Brett DeLine Kai Koenig Charlie Arehart Jonas Eriksson Jason Daiger Shawn Oden Matthew Darby Ross Phillips Edgardo Cabezas Patrick Flynn Stephany Monge John Whish Kevin Wright Peter Amiri You can see an up to date list of all sponsors on Ortus Solutions' Websitehttps://ortussolutions.com/about-us/sponsors ★ Support this podcast on Patreon ★

Data is more critical, more abundant, and less structured than at any point in history. The attributes and uses of data are shifting, stressing traditional relational database management tools that we've come to rely on. NoSQL promises one answer to modern data management. Couchbase's VP of Product & Solution Marketing, Jeff Morris, joins hosts Matt Kimball and Steve McDowell, principal analysts at Moor Insights & Strategy, to talk us through the technology, where its best deployed, and how Couchbase plays in the space. 00:00 Show Open 00:03 Matt's Foolishness 00:45 Let's Talk about NoSQL 01:20 Introduce CouchBase VP Solutions & Product Marketing, Jeff Morris 02:46 How has data management evolved over the past decade? 05:39 Is there a performance hit when moving away from traditional RDMS? 07:54 Optimal use-cases for NoSQL databases 15:45 CouchBase Mobile & Devices 19:53 Is NoSQL a 'big lift' for IT practitioners? 24:44 Capella: CouchBase-as-a-Service 30:33 SQL & NoSQL, a Peaceful Co-Existance? 32:24 Where is CouchBase Focused over the next 12-18 months? 34:37 Wrapping Up. 35:43 The End! Special Guest: Jeff Morris.

About ChrisChris Harris is Vice President, Global Field Engineering at Couchbase, a provider of a leading modern database for enterprise applications that 30% of the Fortune 100 depend on. With almost 20 years of technical field and professional services experience at early-stage, open source and growth technology companies, Chris held leadership roles at Cloudera, Hortonworks, MongoDB and others before joining Couchbase.Links Referenced: couchbase.com: https://couchbase.com LinkedIn: https://www.linkedin.com/in/chris-harris-5451953/ Twitter: https://twitter.com/cj_harris5 TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Couchbase Capella Database-as-a-Service is flexible, full-featured and fully managed with built in access via key-value, SQL, and full-text search. Flexible JSON documents aligned to your applications and workloads. Build faster with blazing fast in-memory performance and automated replication and scaling while reducing cost. Capella has the best price performance of any fully managed document database. Visit couchbase.com/screaminginthecloud to try Capella today for free and be up and running in three minutes with no credit card required. Couchbase Capella: make your data sing.Corey: This episode is sponsored in part by LaunchDarkly. Take a look at what it takes to get your code into production. I'm going to just guess that it's awful because it's always awful. No one loves their deployment process. What if launching new features didn't require you to do a full-on code and possibly infrastructure deploy? What if you could test on a small subset of users and then roll it back immediately if results aren't what you expect? LaunchDarkly does exactly this. To learn more, visit launchdarkly.com and tell them Corey sent you, and watch for the wince.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. One of the stranger parts of running this show is when I have a promoted guest episode like this one, where someone comes on, and great, “Oh, where do you work?” And the answer is a database company. Well, great, unless it's Route 53, it's clearly not the best database in the world, but let's talk about how you're making a strong showing for number two.It sounds like it's this whole ridiculous, negging nonsense or whatever the kids are calling it these days, but that's not how it's intended. Today's promoted guest is Chris Harris, who's the Vice President of Global Field Engineering at Couchbase. Chris, thank you for joining me and I really hope I got it right and that Couchbase is a database company or that makes no sense whatsoever.Chris: It's great to be on the show, and thank you for the invitation. I'm looking forward to it. Yeah, we're a database company. That's exactly what we do.Corey: I always find it interesting when companies start pivoting from a thing that they were and, “What do you do?” “We build databases.” [unintelligible 00:01:29] getting out of that space it's, “What do you do?” “We're a finance company.” And then there's a period of time in which they start reframing what they do. It's, “We're a data platform.” Or, “We're now a tech company.”Really? Because I don't get that sense in any meaningful perspective. Couchbase was founded as a database company. You went public last year—congratulations on that—and now you continue to say, “Yes, we're a database company,” rather than an everything trying to eat the world all at the same time, mostly ineffectively, company. So, what kind of database are you folks?Chris: So, if you look at the database world, you can see—I've been in the space for quite some time now, a good few years, and I've had the privilege, if you like, of being at other database companies, been in the analytics space, and I'm here at Couchbase. But if you look at the history over the last—let's just not go back all the way that far, but let's go back to, like, ten years ago, everybody was building their applications on traditional relational databases. And what you saw is that the Oracle and MySQL, as traditional databases of the world. And then… probably at the time, we realized that with, talking ten years ago where we had this demand for high throughput of data, next generation of applications will be built, and then people realized the traditional database architectures weren't going to cut it, if you like. And it spawned this industry.You know, a big NoSQL market was created. And you have document databases, and then you have graph databases, and then you have analytics databases, and you have search databases, and then you have every sort of database you could possibly think of type database that's out there in the world.Corey: You have so many kinds you need to keep track of it all inside of the database.Chris: That's what you have to do, right? [laugh]. But the interesting thing is it became different types of database. And even see this in many of the code providers today, right, that you have multiple different types of databases no matter what you're trying to do, right? So, we kind of went—Couchbase kind of took a step back and went, okay, we were originally a cache, right, this is where we came from, and then kind of built that into a document database, and then kind of went to the market and went hold on here, rather than it being let's call it a noSQL versus SQL discussion, why can't it just be a database, right?Why can't you have a SQLite interface on top of a modern architecture? Why can you do that, right? Why can't you have the flexibility and architectural [unintelligible 00:04:16] of a JSON-based database with the interface of—with SQL, and then analytics built on top of that, right? So, why can't you have the power of SQL on the next generation architecture? So, that's kind of where we fit in the world.Corey: When we talk about origin stories and where things come from, well, let's start with you. I guess the impolite version of the question is, “Why on earth would you be in a space like this for so long?” But you've been on a lot of interesting places doing somewhat similar things. You were at Cloudera, you were at Hortonworks until you apparently heard a who or whatnot, you were at MongoDB, you were at VMware, you were at Red Hat. And that's going reverse chronologically, but it's clear that you're very focused on a particular expression of a particular problem. Why are you the way that you are? Only pretend that's a polite question.Chris: “Why am I the way that I am?” Well, first of all, I love technology, right? That's the key. And I think many of us in the industry would definitely say that, right? I started off in core engineering, building—I know some people today wouldn't probably remember this, but when you had Chip and Pin where your credit card and you have to type it in and put in a pin number, that was created originally in the UK, and then went off and built e-commerce websites for retailers.Well, that then turned into—was a common theme that I kept seeing is that lot of the technology that we're using was open-source technology. And that kind of got me into the open-source movement, if you like, and I was lucky enough to then join Red Hat when they built middleware frameworks, so got into that space there. And then did a lot of innovation in the middleware space. Went to SpringSource and we did some great work there in the Java Development Framework space. But what became interesting is that—you still see it today—like, in this innovation happening in that middleware space and there's some great innovation happening, right?There's all this stuff with Lambda and serverless architecture that's out there, but they always came back to, we've got the database, this thing that is in the architecture if it goes down, you're stuffed, right? This is where the core value of your company is sitting. So, then that got me interested to see what innovation was happening in this space. And as I say, I got into this field in the early stages of NoSQL, where there was that spawn of new database technologies being created. And then from there, it was like, “Okay, let's get into what was happening in the analytic space.”Again, I'm still in the Hortonworks, and Cloudera space, that's all open-source. But it came down to this is different types of databases that were required different types of skills. And then I started talking to the team here, who was like, “How can we take as great innovation and leverage the skills I already have?” And I thought that was an interesting point.Corey: In the interest of full disclosure, I tend to take the exact inverse approach to the way that you did. When I was going through the worlds of systems administrator, than rebadged as DevOps, or SRE, or systems engineer, production engineer, whatever we're calling ourselves this week, I was always focused primarily on stateless things like web servers, or whatnot because it turns out that—this should be no surprise to longtime listeners of this show—but I'm really bad with computers. And most other things, too; I just brute force my way through it. And that's hilarious when you keep taking down web servers you can push a button and recreate. When you do that to a database or anything that's stateful, it leaves a mark.And if you do it the wrong way, just well enough, you might not have a company anymore, so your DR plan starts to look a lot more like updating your resume. So, I always tried to shy away from things that played to my specific weaknesses that would, you know, follow me around like a stink. You, on the other hand, apparently sound—how to frame it—you know, good at things, and in a way that I never was. So you're—ah, you see a problem, you're running towards it trying to help fix it; I'm trying to how do I keep myself away from making the problem worse is my first approach. It seems like you have definitely been focused on not just data themselves—I mean at some level, [if it was a 00:08:55] pure data problem, it feels like we'd be talking a lot more about storage, but rather how to wind up organizing that data, how to wind up presenting that data, and the relationship that data has to other things that are going on. I'm not speaking in the sense of a traditional relational database, necessarily, but the idea of how that data empowers businesses and enables them to do different things. Is that directionally a fair synopsis of how you see it?Chris: I think the [unintelligible 00:09:21] thing is what I would agree with. What makes it really interesting to me is what we enable people to do with that data, and being able to build, kind of, really fascinating innovation applications that are affecting their underlying businesses, right, from it could be health care, it could be airlines, financial services, some really high, interesting use cases that people are doing that are leveraging the database to be able to drive that level of innovation. Because it's very difficult; I can build some sophisticated application, but if I can't get the performance out of my database, I have a pretty poor experience to my users in today's world. Because, fortunately or unfortunately, people aren't very patient, right? If you have a website that doesn't return very quickly, a customer's gone like minutes ago. You literally got to instantly respond to someone. That's a challenging problem.Corey: It absolutely is. Something that I found as I've talked to a bunch of different companies operating in different ways is the requirements on data stores are generally very different depending upon primarily latency and performance. There's only so long people that are going to watch the spinning circle of doom on a website spin before they realize they're going to go somewhere that has its act together. Conversely, for a lot of business intelligence and analytics queries, there are an awful lot of stories where the thing that people care about is that we actually have to have the results of this query by noon on Thursday. And there are very different use cases for that, and some companies seem to be focused very much on, “We're going to solve both of those use cases extremes and everything in between with the same product offering,” and others tend to say, “Okay, this is the area of the market we're going to focus on.”You could also say that this is an expression of the larger industry question of do I want, more or less a one-size-fits-most database that's general-purpose, or do I want very specific purpose-built databases based upon the use case and the problem? Where do you find yourself on that spectrum?Chris: I find myself on that spectrum is that there's—if you want to describe it at a high level and we can break it down, there's operational-type databases, where I'd say Couchbase fits where you're talking about, I've just built an application; I'm talking to the live user, right, this is what I care about, and when I'm talking about speed and performance here, I'm talking about something that returned within milliseconds of response time. I'm playing an online game, or I'm doing online betting on a sports game. That has to be pretty much instant, right? If we're playing multiplayer games and you're doing something, then I want to be able to see what you're doing straight away, right? People don't expect it to lay there.If you're looking at streaming—people do this with Couchbase—streaming the Olympic Games or Super Bowl in the US, and you want to be able to be there, that whole profile management of that user has to be instant, have that stream to you has to be instant. People use telephone calls and use Couchbase to do, behind the scenes, profile management, right, so they know who you are who's making that call. That's an operational database problem. That's not a traditional analytical problem, right? So, there's a whole other space in the database world for analytics, right, which is bringing all the data together into one place, and I'll help you do data science, AI, machine learning, be able to crunch and compute large volumes of data. If I get back to you, rather than a week in an hour, that's great, but that's not operational. That's analytical.Corey: In data center environments, it's an argument to be made for going in a bunch of different directions; we're going to use a bunch of different data stores to store all these things. Because, generally speaking, the marginal cost of moving data from one of your data storage systems to another one of your data storage systems, one rack row over is fairly small, whereas in cloud, effectively, there are no real capacity constraints anymore until you can get the bill, but that's the entire problem where a lot of the transfer for these things is metered per gigabyte. So, there's a increased desire on a lot of architectural pressures, to wind up making sure that where the data lives, it stays. And whatever it is that you do with that data, it should be able to operate on that data in a way that fits your performance characteristic requirements in the place that it currently is. And on the one hand, I can definitely see that driving a lot of decisions people have made.The counterargument is that it feels a little weird when the cost constraints of how the cloud providers—mostly you, AWS—have decided to build these things out. And that, in turn, is shaping your entire approach to not just your architecture, but your systems design of how data winds up working its way through your lifecycle. It's frustrating, on some level, especially given that they themselves offer something like 15 distinct managed databases offerings but more announced all the time. It becomes very difficult not only to disambiguate between all of them but to afford moving data from one to the next.Chris: The affordability is an interesting discussion, right, because you can look at it from a billing perspective and go absolutely, there's a challenge associated to that. Then is a question of where is my data because it's spread across all these different services; that's another challenge. And then you have the challenge of, okay, the cost associated to having developers build applications against all these different types of services because they all require different APIs and different ways of programming. So that's, there's a cost associated everywhere.Corey: Oh, by far and away, the most expensive part of your AWS, or any cloud spend, is not the infrastructure itself; it's the payroll expense associated with the people working on it. People always cost more than infrastructure. If not, something very strange is going on.Chris: But then you look at it, and you go, okay, if that's the case, I kind of use the analogy, right, that it's like a car, where everyone is talking these days about the electric car [that's going 00:16:05] on that path, right? Now, I should be able—if I was getting an electric car—think of it now, I actually have one—that I can get in the car and I can drive it like any other car. I know what a steering wheel is, I know where my pedals work, it looks and feels like a normal car. But architecturally it's fundamentally different how it operates. So, why can you apply that same thing, that same analogy to a database, right?So, why can't I have the ability from an operational perspective, [unintelligible 00:16:42] talk about operational databases, not necessarily, I don't know, full-blown analytical databases, but operationally being able to say I can store the data in an enterprise database; I can use that to leverage my SQL skills like I have before, and also use it to have a document store under operational analytics, to eventing, to full-stack search, key things that people want to do operationally, but keeping the data together in one database, like an iPhone. I want a database to have these capabilities; I don't want to have all these different types of devices that are everywhere. I want, you know, my iPhone to be able to go to have the capabilities that I'm using. Or my car, to feel like I'm driving a car; doesn't matter if the underlying architecture of the engine changed. That's great, I want the benefit, but I want to be able to drive it in the same way that I've driven any other car out there. And that's kind of trying to solve multiple problems that because you're trying to solve the issue of skills.Corey: It's one of the hard challenges out there, and I think your car analogy can even be extended a bit further because in the early days of the automobile, you were more or less taking some significant risk by driving a car if you weren't also mechanically inclined and to fix it yourself. And in time, we've sort of seen that continue to evolve where they mostly work, and now they work really reliably. And then you take it even a step beyond that, and all right now I'm just going to pay a car service so someone else has to deal with the car and a driver, and I don't have to deal with any of that aspect. And it feels like there are certain parallels, similar to that, toward the end of last year, 2021, you folks, more or less moved away from you can have it in any color you want, as long as you run it yourself—more or less—into offering a fully-managed database-as-a-service cloud option called Capella, which, on the ads for this show, I periodically sing because if you didn't want me to do that, you would not have named it Capella. Now, what was it that inspired you folks to say, “Hm, we could actually offer this as a managed service ourselves?”It's definitely a direction a lot of companies have gone in, but usually, they have to wait to be forced into it by—let's be serious for a second here—Amazon launching the Amazon Basics version of whatever it is themselves and, “Okay, well, they validated our market for us. Let's explore it.”Chris: If you look at that, you go Couchbase has been around for a good few years now selling, as you point out, high-performance databases to large-scale enterprises, on real mission-critical, people call it tier-zero type applications, high-performance applications. And these are some of the most fascinating, most innovative type of applications that I've been involved with through my career. Now, how can we take that capability, provide it to the mass market if you'd like, to be able to give it to people that don't need to have a large number of people out there managing their own infrastructure, being able to understand how to finely tune that underlying infrastructure to get the level of performance that you need from high-performance databases. Now, there are use cases for doing that, so it's not one or the other. It's not that you have to go all-in.There are particular companies out there that, for the economics reasons, for the use case reasons that are running today on-premise, and there's a rational reason for why they do that, right? But for a lot of people out there, whether they're leveraging the cloud, there's an opportunity here to take the power of the database, allow us to then manage it for people, take away that complexity of it, but being able to give them the power so they can leverage their skills, take advantage of Couchbase far easier than ever have been able to in the past. It's opened up a bigger market for us, to summarize your question.Corey: This episode is sponsored by our friends at Oracle Cloud. Counting the pennies, but still dreaming of deploying apps instead of “Hello, World” demos? Allow me to introduce you to Oracle's Always Free tier. It provides over 20 free services and infrastructure, networking, databases, observability, management, and security. And—let me be clear here—it's actually free. There's no surprise billing until you intentionally and proactively upgrade your account. This means you can provision a virtual machine instance or spin up an autonomous database that manages itself, all while gaining the networking, load balancing, and storage resources that somehow never quite make it into most free tiers needed to support the application that you want to build. With Always Free, you can do things like run small-scale applications or do proof-of-concept testing without spending a dime. You know that I always like to put asterisks next to the word free? This is actually free, no asterisk. Start now. Visit snark.cloud/oci-free that's snark.cloud/oci-free.Corey: One way that I tend to evaluate where a given vendor sees themselves—and it's sort of an odd thing to do, but given that I do fix AWS bills for a living, it probably makes sense—I wind up pulling up the website, I ignore the baseline stuff of the, “This is what Gartner says,” and here's a giant series of scrolls. I just go for the hamburger menu and I look for, “All right, where's the pricing information?” Because pricing speaks a lot. And there are two things I generally try to find. One is, is there a free trial that I can basically click and get started working with?Because invariably, I'm trying to beat my head off of a problem at two in the morning, and if it's, “Oh, talk to a salesperson,” well as a hobbyist, or as an engineer who does not have signing authority for things, but it's talk to sales, I realize, “Oh, yeah. One, I probably can't afford it. Two, it's going to be a week or so before I can actually make progress on this, and I'm hoping to get something up by sunrise, and it's probably not for me.” Conversely, the enterprise tier should always have a, “Call for details,” because that is a signal to large enterprise procurement departments and buyers and the rest were it's, “Oh, we will never accept default terms. We always want them customized. We also don't believe in signing any contract without at least two commas in it.”Great. So, being able to speak to both ends of the market is one of those critical things that you folks absolutely nail that. What I like is the fact that if someone has a problem that they're experimenting with at two in the morning, they can get started with your database-as-a-service platform—Capella; or however you want to sing it—and they don't need to wind up talking to you folks directly, first. There's no long-term commitments, there's no [unintelligible 00:22:39] of the infrastructure themselves. There's no getting hounded for the rest of their days over making a purchase for something that didn't pan out.To me, that's always been the real innovation and breakthrough of cloud is that I can spend a few hours some evening kicking around an idea, and if it doesn't work, I can turn it off and spend 17 cents on the process, whereas if it does work, I can keep scaling up without at some point having to replace all of the Raspberry Pi's and popsicle sticks, I build things with real enterprise-grade stuff. There's a real accessibility and democratization that is entered into it. So, I'm always excited when I see companies that are embracing that model. Because, yeah, I'm a grumpy old sysadmin because it's not like there's a second kind of sysadmin, but—and I have a particular exposure and experience level with these things that I can't expect modern developers to work on. They have an idea, they want to launch something, and they just need a database to throw things against and put data into, and ideally get it back again when they query later. And that empowers them to move forward.They're not in this because they really want to run virtual machines themselves and get those set up and secured and patched and hardened, and then install the software on top of it, and, “Why is it not working? Oh, security groups, how you vex me again. I'll just open you to the entire world,” and so on. And we know where that path leads. So, it's nice to see that there is an accessible option there.Conversely, if you come at this with an approach if we are only available in our hosted cloud environment, well now those big enterprise companies that have, you know, compliance concerns are going to have some thoughts for you, none of them particularly pleasant in some cases. So, I like the fact that you're able to expand your offering to encompass different user personas without also, I don't know, turning what has historically been a database into now it's an LDAP server, and trying to eat the world, piece by piece, component by component.Chris: It's interesting that you say that because I think there's a number of things that you're touching on that were to me, if you look at us as a company in particularly this space, there's a lot of focus around the community and the open-source community. And I think there's an element of how do you make it accessible to people as a community as a whole? And then you kind of go down the path of, “Okay, let's allow people,”—as a developer, let's think of it this way, right, the ultimate thing they want to do, and you touched upon it there, is they want to build an application. They get passionate about building the application or maybe even in the weekend, and they got this funky idea that they're going to literally knock some code out.And I remember my fond memories of being an application engineer of being able to sit down for hours just been able to put my ideas into code and watch it execute. The last thing that I want to do is get to the point where I get the database and go, oh, here we go. This is going to take me a bunch of hours, now, and I'm going to set it all up and do other stuff. And I almost literally want to be able to click a few buttons—Corey: You know what I want to do tonight? Feel really dumb as I tackle a problem I don't fully understand. Gr—I'd love smacking into walls that point out my own ignorance. It's discouraging as hell. I'm right there with you.Chris: Yeah, you don't want to do that, right? So, you almost want to make like the database disappear for people, right? You want to be able to just say, like, “Here's your command. Off you go. Bring the data back. Bring it back in full. Allow it to scale.”Because you want that developer to have that experience of not breaking their flow. And what do you want them to be able to be so excited about the application and innovation that they've built, that they want to go and show that teammates? They want to say, “Look at the great thing I built over the weekend. Look at this, this is amazing.” Right?And then be able to get all the teammates pretty excited about what they built in a way in which they can try it out really easily, right? They can take this little thing that they built into the database, click some buttons, and off we go, right? And now your development team is super excited about some of the great innovation that you have. But you also have to have the reverse. You have to have the architecturally sound, so then when you get to the architect, if you like, who is looking at the bigger picture of what's the future going to look like? Is it the right technology? Is this something that we can bring into the organization? And you know, this is a cool bit of application you just built me, but you know, is this realistic that I can deploy this thing?And this is where you start going back into it still has to have high performance, the security has to be there, the scalability has to be there so that I can potentially—I can start small and grow this thing horizontally as I see the requirements coming. There are different set of requirements architecturally, so we're looking at—you know, as a company, our key focus is how do you drive that developer community so that you give the people the freedom to build the next generation of applications in the simplest way [unintelligible 00:27:35], say with free trials, click some buttons, have the database up in minutes, but also then being able to have that capability in the underlying database to take it to the architect. That's what our core focus is every day.Corey: I agree with everything that you're saying. You're making an awful lot of great points, but for me, the proof in the pudding is the second thing that I tend to look at on your website after the pricing page, and that is your list of customers. Because it's always interesting when someone talks about how they're revolutionizing everything, and this is the way to go, and everyone who's anyone is doing these things. And then you look at their customer page and either they don't have one, which is telling, or the customers on that page are terrifying in that, “Wow, that sounds like a whole bunch of fly-by-night startups whose primary industry is scamming people.”You have a bunch of household blue-chip names as well as a bunch of newer companies that are very clearly not what people think of as legacy—you know, that condescending engineering term that means it makes money. It's across the board, it is broad-spectrum, and it is companies that absolutely know exactly what it is that they're doing when it comes to these things. That to me is far more convincing than almost anything else that can be said because it's—look, you can come on and talk to me about anything you want about your product, and I can dismiss it and, “Yeah, whatever. Great.” But when I start talking to customers, as I did prior to recording this episode, and seeing how they talk about you folks, that to me is what reaffirms that, okay, this is actually something that has legs and is solving real customer problems.Because early stage, it's, “We have this idea for this company we're going to build that it's going to be great.” “Awesome. Go talk to more customers.” That is a default, safe piece of advice generically you can give to anyone. And it's easy to give and hard to take.I've been saying this for years, and I still screwed it up and we started trying to launch a SaaS product here called DuckTools. Yeah, it turns out that we didn't talk to enough customers first about what they're actually trying to achieve, and we assumed we knew the answers. It's an easy mistake to make. What I really appreciate is—about a Couchbase in particular—is not just the fact that you have all of these customer references, but the fact that each one talks about what the value to the business is not just in terms of, “Oh yes, now we can query data and there was no way for us to do that before.” Of course, people have found ways to do that since business started.Instead, it's much more about this is how it made it more efficient, more optimal, how it unlocked possibilities and capabilities for us. That alone tells me that there definitely is significant value that you're delivering to customers. In my own business, whenever I think I've seen it all, I have to do is talk to one more customer and learn something new. What have you seen in recent memory, from a customer, that surprised you about how they're using Couchbase?Chris: You look at that, and you can see—I could probably talk for hours on different types of customers, but it's the ones that you can literally see in your life and you can reflect to, right? So, if you taken one of the biggest airlines that are out there today, they're completely changing, kind of, the whole experience. And our whole experience of and how do I get feedback? Because Couchbase's customers, [unintelligible 00:31:01] customer, right, is what they're thinking about, right? They're an airline.So, these passengers; fine. But how many times have you got on a plane, and you see all these people, literally, there's obviously the passengers, and then there's the cabin crew, and then there's the people on the ground, and then there's the pilot, and for the sake of the discussion, the staff that are there are literally passing paper back and forth to each other. And surely there a better way to do this. And for someone who likes to solve complex technical problems, you go, “Wow, this is going to be a bit of a challenge.” Because if you want to collect feedback from an aeroplane in the air, [laugh] right, and you want to connect that to the ground data that people are having in terms of maintenance data, you want to do that across the world, in multiple different time zones, that's pretty tricky problem to try to go solve, right?So therefore, how do you get a database that is able to work remotely and on what people would call the edge; let's just call it in this case in a device that's literally a cabin crew member is carrying around with them that's not connected because there is no connection because I'm in the middle of the air. But I want to pair it with the other cabin crew members that are around, right, in flight, and then when I land, I want to sync that data backup to the maintenance people. So, you need a database that's able to operate on a device with no connection, and then being able to synchronize backup to a cloud database that is then collecting data from all the other flights around the world.Corey: Synchronization sounds super easy until you actually try and do it, and then, “Oh, wow.” It's like, you could cut to pieces by the edge cases.Chris: And then people go, “Well, there's no problem. There's internet everywhere these days.” Yeah, sure there is. [laugh]. You get disconnected all of the time.Corey: Not to name names. This is very evocative, an earlier episode of this show I had with Tyler Slove, who's a senior manager over at United Airlines, about specifically how they're approaching a lot of their own reimagining and the rest. It's a fascinating use case, and as someone who's a bit of a travel geek himself—you know, in the before times—that's always an area of intense interest because it's… I'm sorry, I'm still a little boy at heart; it's magic to me. You get on a plane, you go somewhere else, close the doors, it opens it up, and you're on the other side of the world. And now there's internet on it? Oh, my God, who would have imagined such a thing?Chris: Uh-huh. But that's changing the experience for people. It's just really fascinating.Corey: Completely. And it's empowering and unlocking that experience you're talking about of being able to sync between the crews, about handling all this stuff behind the scenes. Everyone loves to complain about airlines because no one knows really how to run the massive logistical part of an airline. But the WiFi was a little bit slow or the food was cold; well, that's something I know how to complain about Twitter.Chris: [laugh].Corey: It becomes this idea of almost a bikeshed problem expression, where it's, “Oh, yeah. I'm just going to complain about things I can wrap my head around.” Yeah.Chris: I was talking to somebody recently, and they were—swapping topics a little bit—and they were like, so—they were talking about innovation on some new web application that they built. And I literally have to explain them, and I said, “Well, if you think of it, the underlying whole technology stack that's behind this for high-scale e-commerce, it's sophisticated, right, because people will literally walk away from a page, an application, a mobile app, if they don't get an instant response time. And that request has to literally travel, physically, quite a fair amount of distance, talk to multiple different types of technology, answer to that question, then come back to you instantly.” The sheer amount of technology that's involved here of moving that data around is a complicated architectural problem to fix. A database only plays a small part of that. You can't be the slowest player in the party.Corey: No. And that is always the challenge is that when you're looking at different use cases, there's always a constraint, and how that constraint winds up manifesting in different ways, if it's not the thing that's slowing things down, it's also not where the attention goes. If you have a single thing like, the database for example, slowing things down, everyone cares about improving databases, people focusing on, “Well, we're going to improve the JavaScript load time on the website,” that's not the problem. Find the bottleneck and focus on it. And although I'm generally a fan of picking a database and using that as a general-purpose thing until it makes sense not too—much like I am cloud providers—[audio break 00:35:54]Corey: —journey personally, where's the best place to find you?Chris: Clearly, if you want to find more about Couchbase, you can obviously go to couchbase.com. You kindly pointed out you can go and look at the trial for Capella and try out the tech. You're more than welcome to do that as a free trial.If you want to contact me particularly, you find me on LinkedIn; I'm Chris Harris at Couchbase. You'll find me [unintelligible 00:36:26] with Chris Harris in general and probably find lots of them. In the UK, Chris Harris is a famous racing driver. That's not me; it's someone else. So, find me on LinkedIn, I'm sure it won't be that difficult to find what you find. Or you can find me on Twitter.Corey: And we will of course, but links to all of that into the [show notes 00:36:43]. I really want to thank you for being so generous with your time today. It's always appreciated to talk to people who actually know what they're doing.Chris: You're more than welcome. It's been great to be on the show. Thanks, Corey.Corey: Chris Harris, Vice President of Global Field Engineering at Couchbase. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry comment. I'm going to wind up using all of those angry comments, at one point, as a database.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

In today's episode, I interview Chris Harris, VP of Global Field Engineering at Couchbase, about how he has been accelerating technology innovation at the database software company and establishing a more open, collaborative culture. Together, we talk about how databases can be the building blocks that allow businesses to innovate with greater ease.  Innovation unlocks the ability to set a vision, but bringing it to life successfully requires we use a set of foundational tools and architecture. With the surge in demand for improved end-user experiences, Chris shares his insights about why the way we approach innovation is more critical than ever.

This week we meet Chin-Heng Hong, the VP of Product Management at Couchbase, for a discussion about what’s new in database technologies and some of the patterns he sees in the industry. We also talk about Couchbase’s recent survey of Data Architects and some of the interesting findings it contains. Watch this episode on YouTube: https://youtu.be/kO0jQs_O6rk Your next business card will be a YouTube channel! – Learn more at https://algmin.com Save 20% on your first order at the DATAVERSITY Training Center with promo code “AlgminDL” – https://training.dataversity.net/?utm_source=algmindl_res About Chin-Heng Hong: Chin-Heng Hong is VP Product Management at Couchbase, the modern database for enterprise applications. A senior engineering executive with more than 25 years of experience, Hong previously held roles at Hewlett Packard, Oracle, Siebel Systems and others. Couchbase – https://couchbase.com Episode Transcript 100:00:05,000 –> 00:00:08,916anthony_algmin: Welcome to the Data Leadership Lessons Podcast. I’m your host, Anthony J. 200:00:09,166 –> 00:00:12,666anthony_algmin: Algmin. Data is everywhere in our businesses and it takes leadership to make 300:00:12,833 –> 00:00:16,375anthony_algmin: the most of it. We bring you the people stories and lessons to help you 400:00:16,625 –> 00:00:20,541anthony_algmin: become a data leader. Our show is produced by Algmin Business Media, where we 500:00:20,625 –> 00:00:23,958anthony_algmin: make having your own video podcast as easy as joining a video call and 600:00:24,041 –> 00:00:28,208anthony_algmin: sending an email. At Algmin Business Media, the stage is yours! Today 700:00:28,291 –> 00:00:28,583anthony_algmin: on data leadership lessons we welcome Chin Hong. Chin is V. P of product 800:00:28,583 –> 00:00:31,625anthony_algmin: on data leadership lessons we welcome Chin Hong. Chin is V. P of product 900:00:31,625 –> 00:00:36,208anthony_algmin: management at Couchbase, the modern database for enterprise applications, a 1000:00:36,291 –> 00:00:39,416anthony_algmin: senior engineering executive with more than twenty five years of experience. 1100:00:39,916 –> 00:00:44,625anthony_algmin: Chin previously held roles at Hewlett Packard, Oracle, Siebel systems, as well 1200:00:44,791 –> 00:00:46,958anthony_algmin: as others. Chin, welcome to the show! 1300:00:48,208 –> 00:00:49,666chin: thank you, Antony. 1400:00:50,625 –> 00:00:53,666anthony_algmin: So likely, do with all our first time guests. Please take a moment and 1500:00:53,750 –> 00:00:57,833anthony_algmin: just tell the audience a bit more about your career before Couchbase, And A. 1600:00:57,916 –> 00:01:01,083anthony_algmin: How that led you to what you’re doing now? 1700:01:01,875 –> 00:01:02,208chin

Amy Tom talks to Mark Gamble, the Product & Solutions Marketing Director at Couchbase, about data-for-good initiatives and creating a Multi-Cloud Strategy. In this episode of The HackerNoon Podcast: Mark talks about the data-for good and the initiatives he is passionate about (01:57) Data visualization is a skill (08:31) Multi-Cloud vs. Hybrid-Cloud (12:30) Does Amazon/AWS do this internationally as well? (21:23) How do the Kubernetes Containers connect across multiple platforms? (25:30) As a CTO, do I have to worry about the connection layer between clouds? (28:50) Is it difficult to get my Couchbase database to connect with another AWS location? (30:00) Where will Multi-Cloud go in the next 5 years? (35:20) Connect Mark Gamble: Email him at mark.gamble@couchbase.com Shownotes: Learn more about Couchbase: https://www.couchbase.com/

Amy Tom talks to Anil Kumar, the Product Manager at Couchbase, about becoming a Product Manager, writing his book: Couchbase on Kubernetes, and creating a multi-cloud strategy.

In the age of extreme personalization, how can you remain safe and secure online?