{"id":5129,"date":"2020-01-02T14:25:07","date_gmt":"2020-01-02T14:25:07","guid":{"rendered":"http:\/\/www.odbms.org\/blog\/?p=5129"},"modified":"2020-01-02T14:25:07","modified_gmt":"2020-01-02T14:25:07","slug":"on-kubernetes-hybrid-and-multi-cloud-interview-with-jonathan-ellis","status":"publish","type":"post","link":"https:\/\/www.odbms.org\/blog\/2020\/01\/on-kubernetes-hybrid-and-multi-cloud-interview-with-jonathan-ellis\/","title":{"rendered":"On Kubernetes, Hybrid and Multi-cloud. Interview with Jonathan Ellis"},"content":{"rendered":"
\n
\n

“Container and orchestration technologies have made a quantum leap in manageability for microservice architectures.\u00a0 Kubernetes is the clear winner in this space.\u00a0 It\u2019s taken a little longer, but recently Kubernetes has turned a corner in its maturity and readiness to handle stateful workloads, so you\u2019re going to see 2020 be the year of Kubernetes adoption in the database space in particular. “<\/strong>—\u00a0Jonathan Ellis.<\/strong><\/p>\n<\/blockquote>\n

I have interviewed Jonathan Ellis<\/strong>, Co-Founder and CTO at <\/i>DataStax<\/a>. <\/i>We talked\u00a0about\u00a0Kubernetes, Hybrid and Multi-cloud. \u00a0In addition, Jonathan tells us his 2020 predictions and thoughts around migrating from relational to NoSQL.<\/span><\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0Happy and Healthy New Year!<\/strong> RVZ<\/p>\n<\/div>\n

Q1. Hybrid cloud vs. multi-cloud: What’s the difference?<\/span><\/b><\/p>\n

Jonathan Ellis:\u00a0<\/strong>Both hybrid and multi-cloud involve spreading your data across more than one kind of infrastructure.\u00a0 As most people use the terms, the difference is that hybrid cloud involves a mix of public cloud services and self-managed data center resources, while multi-cloud involves using multiple public cloud services together, like Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). <\/span><\/p>\n

Importantly, multi-cloud is more than using multiple regions within one cloud provider\u2019s infrastructure. Multiple regions can provide resiliency and distribution of your data (although outages with a large enough blast radius can still affect multiple regions, like Azure\u2019s global DNS outage earlier this year<\/a>), but you\u2019re still limited to the features of a single provider rather than a true multi-cloud environment. <\/span><\/p>\n

Q2. What is your advice: When is it better to use on-prem, or hybrid, or multi-cloud? <\/span><\/b><\/p>\n

Jonathan Ellis:\u00a0<\/strong>There are three main areas to consider when evaluating the infrastructure options for an application.\u00a0 The best approach will depend on what you want to optimize for. <\/span><\/p>\n

The first thing to consider is agility<\/em>\u2014cloud services offer significant advantages on how quickly you can spin infrastructure up and down, allowing you to concentrate on creating value on the software and data side.\u00a0 But the flip side of this agility is our second factor, which is cost<\/em>.\u00a0 The agility and convenience of cloud infrastructure comes with a price premium that you pay over time, particularly for \u201chigher level\u201d services than raw compute and storage.<\/span><\/p>\n

The third factor is control<\/em>.\u00a0 If you want full control over the hardware or network or security environment that your data lives in, then you will probably want to manage that on-premises.<\/span><\/p>\n

A hybrid cloud strategy can let you take advantage of the agility of the cloud where speed is the most important factor, while optimizing for cost or for control where those are more critical.\u00a0 This approach is popular for DataStax customers in the financial services sector, for instance.\u00a0 They like the flexibility of cloud, but they also want to retain control over their on-premises data center environment. We have partnered with VMware on delivering the best experience for public\/private cloud deployments here.<\/span><\/p>\n

DataStax builds on Apache Cassandra<\/a><\/span>\u2122<\/span><\/a> technology to provide fine-grained control over data distribution in hybrid cloud deployments.\u00a0 <\/span>DataStax Enterprise<\/a><\/span> (DSE) adds performance, security and operational management tools to help enterprises improve time-to-market and TCO.<\/span><\/p>\n

Q3. IT departments are facing an uphill battle of managing hybrid, multi-cloud environments. Why does building scalable modern applications in the cloud remain a challenge?<\/span><\/b><\/p>\n

Jonathan Ellis:\u00a0<\/strong>Customers of modern, cloud-native applications expect quick response times and 100% availability, no matter where you are in the world.\u00a0 This means your data layer needs the ability to scale both in a single location and across datacenters.\u00a0 Relational databases and other systems built on master\/slave architectures can\u2019t deliver this combination of features.\u00a0 That\u2019s what Cassandra was created for.<\/span><\/p>\n

Cloud vendors have started trying to tackle these market requirements, but by definition their products are single-cloud only.\u00a0 DSE not only provides a data layer that can run anywhere, but it can actually run on a single cluster that spans machines on-premises and in the cloud, or across multiple public clouds.<\/span><\/p>\n

Q4. Securing a multi-cloud strategy can be difficult due to a lack of visibility across hosts. What is your take on this?<\/span><\/b><\/p>\n

Jonathan Ellis:\u00a0<\/strong>Security for a multi-cloud architecture is more complex than security for a single cloud and has unique challenges. Security is required at multiple levels in the cloud and often involves compliance with regulatory standards. While security vendors are trying to solve this problem across clouds, the current tooling is limited and the feature sets vary so the ability to have a cohesive view of the underlying IaaS across clouds is not optimal. This implies a need for IT teams to have skill sets for each cloud in their architecture, while relying on the AWS, GCP or Azure specific security, monitoring, alerting and analytics services to provide visibility.\u00a0 (As applications and databases move to managed kubernetes<\/a> platforms like GKE<\/a>, EKS<\/a> and AKS<\/a>, some of the security burden for host level security shifts to the cloud providers who manage and secure these instances at different levels.) <\/span><\/p>\n

These challenges are not stopping companies from moving forward with a multi-cloud strategy, driven by the advantages of avoiding vendor lock in and improved efficiency from a common data layer across their infrastructure, as well as by non-technical factors such as acquisitions.<\/span><\/p>\n

Datastax provides capabilities that enable companies to improve their security posture and help with the security challenges. At the data security level, DSE advanced security allows companies to minimize risk, achieve granular access control, and help with regulatory compliance. It does this with functionality like unified authentication, end-to-end encryption, and enhanced data auditing. We are also developing a next generation cloud based monitoring tool that will have a unified view across all of your Cassandra deployments in the cloud and will be able to provide visibility into the underlying instances running the cluster.\u00a0 Finally, Datastax managed services offerings like Apollo<\/a> (see below) will also provide some relief to this problem.<\/b><\/span><\/p>\n

Q5. You recently announced early access to the DataStax Change Data Capture (CDC) Connector for Apache Kafka\u00ae. What are the benefits of bridging Apache Kafka with Apache Cassandra?<\/span><\/b><\/b><\/p>\n

Jonathan Ellis:\u00a0<\/strong>Event streaming is a great approach for applications where you want to take actions in realtime. Apache Kafka <\/a>was developed by the technology team at LinkedIn to manage streaming data and events for these scenarios.<\/span><\/p>\n

Cassandra is the perfect fit for event streaming data because it was built for the same high ingest rates that are common for streaming platforms such as Kafka. DataStax makes it easier to bring these two technologies together so that you can do all of your real-time streaming operations in Kafka and then serve your application APIs with a highly available, globally distributed database. This defines a future proof architecture that handles any needs that microservices and associated applications throw at it. <\/span><\/p>\n

It\u2019s important to recognise what Kafka does really well in streaming, and what Cassandra does well in data management. Bringing these two projects together allows you to do things that you can\u2019t do with either by itself.<\/span><\/p>\n

Q6. DataStax recently <\/span><\/b>announced<\/b><\/a><\/span> a production partnership with VMware in support of their VMware vSAN to include hybrid and multi-cloud configurations. Can you please elaborate on this? <\/span><\/b><\/p>\n

Jonathan Ellis:\u00a0<\/strong>We have worked with VMware for years on how to support hybrid cloud environments, and this partnership is the result.\u00a0VMware and DataStax have a lot of customers in common, and for a lot of those customers, the smoothest path to cloud is to use VMware to provide a common substrate across their on-premises and cloud deployments.\u00a0 Partnering with VMware allows DataStax to provide improved performance and operational experience for these enterprises.<\/span><\/p>\n

Q7. What are your 2020 predictions and thoughts around migrating from relational to NoSQL? <\/span><\/b><\/p>\n

Jonathan Ellis:\u00a0<\/strong>Container and orchestration technologies have made a quantum leap in manageability for microservice architectures.\u00a0 Kubernetes is the clear winner in this space.\u00a0 It\u2019s taken a little longer, but recently Kubernetes has turned a corner in its maturity and readiness to handle stateful workloads, so you\u2019re going to see 2020 be the year of Kubernetes adoption in the database space in particular.\u00a0 (<\/span>Kubernetes support for DSE is available on our Labs site<\/a><\/span>.)<\/span><\/p>\n

In terms of moving from relational to NoSQL<\/a>, there\u2019s still a gap that exists in terms of awareness and understanding around how best to build and run applications that can really take advantage of what Cassandra can offer.\u00a0 Our work in <\/span>DataStax Academy<\/a><\/span> for Cassandra training will continue in 2020, educating people on how to best make use of Cassandra and get started with their newest applications. This investment in education and skills development is essential to helping the Cassandra community develop, alongside the drivers and other contributions we make on the code side.<\/span><\/p>\n

Q8. What is the road ahead for Apache Cassandra?<\/span><\/b><\/p>\n

Jonathan Ellis:\u00a0<\/strong>I was speaking to the director of applications at a French bank recently, and he said that while he thought the skill level for developers had gone up massively overall, he also thought that skills specifically around databases and data design have remained fairly static, if not down over time.\u00a0 To address this skills gap, and to take advantage of cloud-based agility, we\u2019ve created the <\/span>Apollo<\/a><\/span> database (now in open beta) as a cloud-native service based on Cassandra. This makes the operational complexities of managing a distributed system a complete non-problem.<\/span><\/p>\n

Our goal is to continue supporting Cassandra as the leading platform for delivering modern applications across hybrid and multi-cloud environments.\u00a0 For companies that want to run at scale, it\u2019s the only choice that can deliver availability and performance together in the cloud.<\/span><\/p>\n

———————<\/p>\n

\u00a0\"Jonathan<\/a><\/span><\/p>\n

Jonathan Ellis<\/span><\/span><\/strong><\/p>\n

Jonathan is a co-founder of DataStax. Before DataStax, Jonathan was Project Chair of Apache Cassandra for six years, where he built the Cassandra project and community into an open-source success. Previously, Jonathan built an object storage system based on Reed-Solomon encoding for data backup provider Mozy that scaled to petabytes of data and gigabits per second throughput.<\/span><\/em><\/p>\n

Resources<\/span><\/strong><\/p>\n

–\u00a0DataStax Enterprise<\/a><\/span><\/strong> (DSE)<\/span><\/p>\n

–\u00a0DataStax Academy<\/a><\/strong><\/p>\n

–\u00a0Apollo<\/a><\/strong><\/span> database<\/span><\/p>\n

Related Posts<\/strong><\/p>\n

– \u00a0The Global AI Index 2019<\/a><\/strong>, ODBMS.org\u00a0DEC. 17, 2019<\/p>\n

– \u00a0Look ahead to 2020 in-memory computing<\/a>,\u00a0<\/strong>ODBMS.org\u00a0DEC. 27, 2019<\/p>\n

Follow us on Twitter: @odbmsorg<\/a><\/strong><\/p>\n

Follow us on:\u00a0LinkedIn<\/a><\/strong><\/p>\n

##<\/p>\n","protected":false},"excerpt":{"rendered":"

“Container and orchestration technologies have made a quantum leap in manageability for microservice architectures.\u00a0 Kubernetes is the clear winner in this space.\u00a0 It\u2019s taken a little longer, but recently Kubernetes has turned a corner in its maturity and readiness to handle stateful workloads, so you\u2019re going to see 2020 be the year of Kubernetes adoption […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[39,789,1530,54,1161,66,97,102,1524,1525,142,1527,1528,1532,907,322,1386,908,1526,412,446,614,1529,1531],"_links":{"self":[{"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/posts\/5129"}],"collection":[{"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/comments?post=5129"}],"version-history":[{"count":12,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/posts\/5129\/revisions"}],"predecessor-version":[{"id":5143,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/posts\/5129\/revisions\/5143"}],"wp:attachment":[{"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/media?parent=5129"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/categories?post=5129"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/tags?post=5129"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}