Stretching The Elastic Stack with Philipp Krenn - Episode 23
51:02 Share

Summary

Search is a common requirement for applications of all varieties. Elasticsearch was built to make it easy to include search functionality in projects built in any language. From that foundation, the rest of the Elastic Stack has been built, expanding to many more use cases in the proces. In this episode Philipp Krenn describes the various pieces of the stack, how they fit together, and how you can use them in your infrastructure to store, search, and analyze your data.

Preamble

• Hello and welcome to the Data Engineering Podcast, the show about modern data management

• When you’re ready to build your next pipeline you’ll need somewhere to deploy it, so check out Linode. With private networking, shared block storage, node balancers, and a 40Gbit network, all controlled by a brand new API you’ve got everything you need to run a bullet-proof data platform. Go to dataengineeringpodcast.com/linode) to get a $20 credit and launch a new server in under a minute.

• For complete visibility into the health of your pipeline, including deployment tracking, and powerful alerting driven by machine-learning, DataDog has got you covered. With their monitoring, metrics, and log collection agent, including extensive integrations and distributed tracing, you’ll have everything you need to find and fix performance bottlenecks in no time. Go to dataengineeringpodcast.com/datadog) today to start your free 14 day trial and get a sweet new T-Shirt.

• Go to dataengineeringpodcast.com) to subscribe to the show, sign up for the newsletter, read the show notes, and get in touch.

• Your host is Tobias Macey and today I’m interviewing Philipp Krenn about the Elastic Stack and the ways that you can use it in your systems

Interview

• Introduction

• How did you get involved in the area of data management?

• The Elasticsearch product has been around for a long time and is widely known, but can you give a brief overview of the other components that make up the Elastic Stack and how they work together?

• Beyond the common pattern of using Elasticsearch as a search engine connected to a web application, what are some of the other use cases for the various pieces of the stack?

• What are the common scaling bottlenecks that users should be aware of when they are dealing with large volumes of data?

• What do you consider to be the biggest competition to the Elastic Stack as you expand the capabilities and target usage patterns?

• What are the biggest challenges that you are tackling in the Elastic stack, technical or otherwise?

• What are the biggest challenges facing Elastic as a company in the near to medium term?

• Open source as a business model: https://www.elastic.co/blog/doubling-down-on-open?utm_source=rss&utm_medium=rss

• What is the vision for Elastic and the Elastic Stack going forward and what new features or functionality can we look forward to?

Contact Info

• @xeraa) on Twitter

• xeraa) on GitHub

• Website)

• Email)

Parting Question

• From your perspective, what is the biggest gap in the tooling or technology for data management today?

Links

• Elastic)

• Vienna) – Capital of Austria)

• What Is Developer Advocacy?)

• NoSQL)

• MongoDB)

• Elasticsearch)

• Cassandra)

• Neo4J)

• Hazelcast)

• Apache Lucene)

• Logstash)

• Kibana)

• Beats)

• X-Pack)

• ELK Stack)

• Metrics)

• APM (Application Performance Monitoring))

• GeoJSON)

• Split Brain)

• Elasticsearch Ingest Nodes)

• PacketBeat)

• Elastic Cloud)

• Elasticon)

• Kibana Canvas)

• SwiftType)

The intro and outro music is from The Hug) by The Freak Fandango Orchestra) / CC BY-SA)

Support Data Engineering Podcast)