Elasticsearch

“The database that was the most difficult for me to scale during that time, and that was the most aggravating to be on call for, was Elasticsearch. It was very, very difficult to deal with, and I saw a lot of projects that were just being held back in their amb…”

“So, to build search, you don't necessarily need elastic search. You maybe need Algolia. If that's what you're looking for, and you're focusing on building great search, you don't have to build everything around what you need in order to operate a complete sear…”

“The next day I called Elasticsearch. We ended up investing in the company a month later, and then it went public.”

“If you try and do that on top of, like, an elastic search, you know, your joins that are going to emerge on top of the derived information are going to just slow that thing down to being unusable.”

“What we found though is that while it was good getting started, we encountered a lot of challenges with it, especially when we started to cross over into the multiple terabyte range. And we had a lot of trouble scaling it.”

“So being being real-time and processing this data was really important, and that was a real challenge with Elasticsearch.”

“What was interesting is that all of these storages have different strengths, but none of them really could just completely replace Elasticsearch.”

“What we're doing is we're going to be running our own Elasticsearch instances ourselves that we can then fully configure and it'll just give us a lot more flexibility.”

“One was, we were looking for something that was truly open source, where we had a lot more control over open source and, sorry, source code, and a lot more saying how the direction goes.”