Leapfire Solutions, LLC • Sunnyvale, California

Engagement Possibilites

Most effective is for me to work with your team for a 2 hour session to start, and then 2 hours a day for a few days. In the first session, you can teach me about your application and existing cluster; I can make recommendations for your team to implement. Then, I can coach them subsequent days as they do their work. I love to lend my experience to good software engineers so they can accelerate up the learning curve.

Starter Package: Cluster Health Check

We can start with a package of 10 hours. We can make significant progress for Elasticsearch and the rest of the Elastic Stack. We can meet on-site, video conference or a mix.

The focus of the Health Check starter package would be cluster topology, configuration, operations scripts, and capacity/growth planning, monitoring, alerting, security, backup/restore, and disaster recovery.

Starter Package: Elasticsearch Data Modeling

A data-modeling package of 10 hours across several days would yield good progress. I can do initial schema and query development in collaboration with your software engineers. Or, I can review existing Elasticsearch mappings and queries to make recommendations. We will discuss choosing field types, the tradeoff between Precision and Recall of search results. We will seek indexing improvements for replacing expensive queries.

Elasticsearch Performance Improvements

Cluster Health Check plus Elasticsearch Data Modeling

Starter Package: Learn PreJoin!

Leapfire’s PreJoin Solution is an innovative join-compare solution that works well for many use cases. It needs no changes to Elasticsearch, no extra plugins, and uses the existing Elasticsearch Query DSL. In a 10 hour starter package, I can provide training and mentoring so that your software engineers can effectively implement the PreJoin Solution. See Join Solution.

Elasticsearch Architecture

I'll join your project for 10 hours a week for 12 weeks. We'll collaborate on data modeling, distributed systems design, and anything mentioned above. Embedded consulting to make the software engineers Elasticsearch experts themselves.

Initial Questionnaire

Upon engagement, this questionnaire will get us off to a good start. You can just check one item for most questions; provide numbers for the metrics. Download: Initial Questionnaire

Project Name: ___________________

1. What is the Use Case?
  • Application Search
  • Business Analytics
  • Log Analytics
  • Reporting
  • Distributed Database
  • Time-Series Event System
  • Other
2. New or Old?
  • New system; “greenfield project”
  • Existing system adding Elasticsearch
  • Existing system using Elasticsearch
  • V 2.0 Replacement system; existing system is:
    • SOLR
    • Relational
    • NoSQL
    • Splunk
    • Other
3. At what Stage is the project?
  • Planning
  • Proof-of-Concept Programming
  • Initial Minimal Viable Product Development
  • Working in Production; continuing development
  • Other
4. What metrics do you know?
  • Single Document Size in bytes
  • Number of Documents to Index per day
  • Queries per Second
  • Days of Retention for Event or Log Systems
5. Where does it live?
  • Elastic Cloud
  • Internal Data Centers
  • AWS
  • Azure
  • Other
5. What version of Elasticsearch are you using or planning?
  • 1.x
  • 2.x
  • 5.x

Elastic asks

“How did Geena become so knowledgeable of Elasticsearch?”

Elastic Training Classes that I have taken

▸ Core Elasticsearch
▸ Core Elasticsearch: Operations
▸ From 5 to 1000 Nodes
▸ Core Elasticsearch: Developer
▸ Advanced Elasticsearch: Data Modeling

“And another one bites the dust. Replication has saved my butt… Because, I’ve got an Elastic Heart.”