Elasticsearch at Scale: Reference Architecture and Common Pitfalls

You like it, you love it, want some more of it? Don’t worry, you are not alone in your desire to expand and scale your Elasticsearch deployment. Join Elastic’s Solutions Architect, Alan Hardy, for a presentation on Elastic’s Reference Architecture and discussion on designing for scaling.

Chris Earle, Elastic Support Engineer, will then dive into one of the most frequent problems with scaling Elasticsearch workloads: fielddata.

Register to Watch

You'll also receive an email with related content.

Chris Earle

Chris is a Support Engineer based outside of Washington DC. When Chris isn't helping Elastic's subscribers fine-tune their deployment he helps train the next generation as a lecturer at Johns Hopkins University. Before joining Elastic, he was at Boeing and Grove Software developing software and pushing API design. Chris is a regular participant on StackOverflow and the Elastic IRC community.

Alan Hardy

Alan is a Solutions Architect based in London. Before joining Elastic, Alan worked as a consultant and a developer, flirting between: Financial, Media, Web and Telco industries for the past 15 years. He even enjoyed some time surveying in the Canadian Rockies for kicks. He is a long time user of Elasticsearch, and now works closely with customers to get the full power out of the ELK stack to meet their needs.