AUGUST 30, 2021

Graham Gillen

Graham Gillen

VP of Marketing for Pureinsights

In early 2021, on the heels of a major licensing change by Elastic, Amazon announced the OpenSearch project, a code branch of Elasticsearch and Kibana under the Apache 2.0 open-source license.  In the first of a three-part Elasticsearch vs OpenSearch blog series, we will examine practical implications of this development on the user and vendor communities that developed around these products.  Subsequent blogs will cover the Elastic point-of-view and the Amazon point-of-view.

Wait, What Happened?

If you are a search  application engineer the biggest development in 2021 was Elastic’s announced license change, stating “We are moving our Apache 2.0-licensed source code in Elasticsearch and Kibana to be dual licensed under Server Side Public License (SSPL) and the Elastic License.”   Elastic posted a useful FAQ and clarification of the license change.

This news might have fallen under the radar of the broader IT-verse if not for the subsequent announcement of the OpenSearch initiative by Amazon. OpenSearch is a fork of the Elasticsearch and Kibana code base which will remain under the Apache 2.0 license.  You can find the official OpenSearch project here.

This news impacts a much broader ecosystem than at first glance.

- With over 100 million downloads, Elasticsearch’s popularity has eclipsed Solr (pun intended).  A huge developer community is affected.

- Elasticsearch and Kibana’s functionality has created a large business ecosystem worth billions, not just around enterprise search but also analytics (observability), and IT security applications.

Elastic is hugely popular because Elasticsearch and Kibana are great products  But also because they were available under the minimally restrictive Apache 2.0 license. And while the Elastic licensing change seems to mostly target Amazon, users are scrambling to interpret how they are impacted.  Independent providers of products or services based on Elasticsearch or Kibana are especially concerned about the Limitations in the Elastic 2.0 license and how it impacts their business models.

But rather than take sides as things heat up between Elastic and Amazon, you should be objectively asking yourself “what does this mean to me or my company?”

Consumers Always Win When There is Choice

While it can be daunting to decide what to watch on Netflix or Hulu, consumer choice is generally always seen as a good thing.

Before the latest Elastic and Amazon drama, there were already very good commercial search solutions in the market even with recent consolidation.  OpenSearch might distinguish itself over time.  Solr also remains a proven (if less trendy) option as well.  The market will dictate which options survive.

If OpenSearch succeeds, it will become popular among open-source purists (at the expense of Solr).  Enterprises with products or services built around Elasticsearch and Kibana may have to port to Solr or OpenSearch.  The risk involves balancing OpenSearch’s long-term viability versus the reduced popularity of Solr and vendor lock-in (and possibly higher costs) from working with Elastic or their partners. The market, again, will dictate what happens.

OpenSearch also benefits from the weight of Amazon’s PR machine. It could falter if Amazon loses interest, and community support fizzles.  But it is off to a strong start with roots dating back to 2019 with Open Distro, the first significant branch of Elasticsearch and Kibana.  Open Distro supporters included Red Hat, Netflix, and Expedia.  The OpenSearch announcement quotes heavyweights like SAP and Capital One. Just as Solr and Elasticsearch benefited from building on Lucene, OpenSearch builds on Open Distro and the established success of Elasticsearch and Kibana.

OpenSearch reached its version 1.0 milestone and promises a production-quality release by the end of 2021. It is also possible, though unlikely, that Elastic could reverse directions on licensing. In any case, the next 6-12 months will be very interesting.

Elasticsearch vs OpenSearch: How Things Got Ugly

Pureinsights has always maintained vendor neutrality in the solutions we recommend or build.  This goes back to our history at Search Technologies and our belief in customers having the ultimate choice.  We are not taking sides in this Elasticsearch vs OpenSearch battle, but we do see growing confusion and concern among the user and vendor community.  How did things get this ugly?

It may go back to February 2019, with Amazon’s support for Open Distro, including security and management enhancements. Open Distro became the open-source community’s response to X-Pack (or ELK Stack), Elastic’s commercial bundling of Elasticsearch, Logstash, Kibana and Beats.  Amazon then launched the “Amazon Elasticsearch Service” without collaborating with Elastic. Elastic’s stock took a hit and Elastic sued AWS for trademark infringement in October 2019.

Much of all this is summarized in this excellent summary blog by David Tippett, a DevOps Engineer with the PRA Group: “The Difference Between Elasticsearch, Open Distro and OpenSearch.”  As Tippett notes, trying to get a new branch of Elasticsearch and Kibana in working condition is a messy affair. According to Tippett and other sources, Elastic added checks to slow down or prevent users from using Open Distro.  The problems eventually plagued OpenSearch, in the form embedded “phone home” code Elastic ostensibly uses to track user and application metrics. A team at OpenSearch spent weeks gutting the code to remove mentions of Elasticsearch and Kibana and get the software to work.

Escalation and Response

Elasticsearch then made changes in its downloadable client libraries, causing more problems for OpenSearch. Tim Ryan notes in an article in The Register that “Elastic modified the official Python client for its Elasticsearch database to not work with forked versions and closed the GitHub issue to comments.”  Elastic viewed the changes as enhancements to ensure that users know they are using officially supported Elasticsearch client libraries.   OpenSearch users viewed this as sabotage.   Amazon announced that OpenSearch will address the issue by committing to developing a whole new set of client libraries for OpenSearch.

Could this mess have been avoided before the “cold war” between Elastic and Amazon escalated?  It’s hard to say.  Perhaps Amazon could have worked more closely with Elastic on “Amazon for Elasticsearch”.  Or perhaps as one poster joked on Twitter, Amazon should have named it “RubberBandSearch”.  A pragmatic conclusion, though, is that Elastic could have found a better way than licensing to address a business dispute with Amazon.

The Death of Solr? or The Revenge of Solr?

In all of this mess we can’t forget that Apache Solr is still out there, in production in many applications.  Does the advent of OpenSearch accelerate the slow death of Solr?  Or is this more like a Star Wars trilogy, “The Revenge of Solr”?  Is Amazon, of all people, trying to convince everyone in the open-source community that Elastic is the evil Empire everyone should be drawing their light sabers against?

With Elastic’s tremendous success and IPO, it was inevitable they would lose some of the “charm” of their early days.  I still have these old ELK logo stickers on my laptop.

Original Elasticsearch Logstash and Kibana logos

Nostalgia aside, reaction from the open-source community has been mixed, as documented by InfoQ.

“Elasticsearch is a fork of Elasticsearch because they’re the ones who changed the license. Amazon is just continuing the original open-source project which Elasticsearch abandoned.” – Colin Percival on Twitter

“Amazon isn’t doing this for the community. They’re doing it for themselves – they’ve made billions already from Amazon Elasticsearch service and don’t want the money to stop with the new license.” – Reddit User Proton

Solr remains a very capable search engine for basic search applications.  Our engineers at Pureinsights have successfully deployed and supported Solr in many large-scaled search applications and Solr deserves consideration, at least until the viability of OpenSearch is no longer in question.

Practical Recommendations: What Should I Do?

You can trust Pureinsights to help you evaluate and choose whether Elasticsearch / Kibana, OpenSearch, Solr, or some other combination of technologies is best for your search-based applications.  What we’d like to offer here is an appetizer to what your decision-making process might be like.  The first thing to figure out is which of the following three “buckets” you fall into, as an Elasticsearch and Kibana user:

Three types of Elasticsearch users

In a nutshell:

- If you are a regular user of Elasticsearch and Kibana and you develop, manage and support your own application using the open-source versions, the new licensing probably works for you fine and you can continue with Elastic’s official distributions.

- For users of Elastic and Kibana as a managed service, you will need to find out what the vendor roadmap looks like and decide whether that impacts your choice of cloud or service providers in the future, and what a migration path would look like.  Your decision might be most complicated if you service provider is Amazon.

- Providers of managed services or products with Elasticsearch or Kibana embedded in their offerings will have a business decision to make. Migrate to OpenSearch only, or invest in giving customers a choice between the Elastic or OpenSearch distributions.

We have documented a more complete set of  decision trees in a PDF that may be useful.

The Ultimate Impact on our Customers

While choice can be daunting, we believe it is generally always a good thing for our customers. Vendor-neutrality is in our DNA, and we are committed to that whether you are talking about Elasticsearch vs OpenSearch, or any commercial or open-source technologies.

Our fully managed services will always offer customers a choice when it comes to search engine technologies. That could mean using Solr, Elasticsearch, OpenSearch, or solutions from commercial vendors like Coveo, Yext, Google, Sinequa, and Lucidworks.

Customer needs always drive the technology mix we recommend for each bespoke solution, including when our own Pureinsights Discovery Platform is suitable. And we will ensure that any technology we use in your search application architecture will comply to the licensing terms from the original source.

Up Next in the Series...

If you enjoyed this post, please consider sharing it using the social media buttons below.

In future blogs on Elasticsearch vs OpenSearch, we’ll cover the Elastic point-of-view and the Amazon (and OpenSearch) point-of-view.  This includes the business reasons behind each company’s actions, as well as the license models at the center of the dispute.

For a free 1:1 consultation to further discussion the evaluation of Elasticsearch vs OpenSearch, please feel free to CONTACT US.

Best Regards,

The Pureinsights Team

Blog

/

Elasticsearch vs OpenSearch : The Elastic View (Part 2)

- OCTOBER 14, 2021

Graham Gillen

Graham Gillen

VP of Marketing for Pureinsights

In early 2021, on the heels of a major licensing change by Elastic, Amazon announced the OpenSearch project, a code branch of Elasticsearch and Kibana under the Apache 2.0 open-source license. In the second of a three-part Elasticsearch vs OpenSearch blog series, we will examine Elastic’s point-of-view and reactions. Other blogs in the series cover the User point-of-view and the Amazon point-of-view.

Elasticsearch vs OpenSearch: Origins and Milestones

To understand Elastic’s reaction to the Elasticsearch vs. OpenSearch saga, you have to start with the company’s origins and early cult-like following. And we do mean “cult” in the best possible sense.

Shay Banon created Elasticsearch in 2010 and formed Elasticsearch Inc. in 2012, near the height of the enterprise search market. At the time, Apache Solr reigned as the open-source search engine king. But how did Elasticsearch usurp the throne in such short order?

Elasticsearch (the product) was the foundation upon which Elastic (the company) was built. Elastic features a colorful origin story on their website and we will cover some important milestones illustrated in the timeline below.

Elasticsearch vs OpenSearch Key Milestones

Elasticsearch Crashes Three Parties: Search, Analytics, and Security

There were a lot of very good search engines available in 2012 (and we had worked with most of them). Autonomy was the most hyped, Google’s brand recognition translated into success for the Google Search Appliance, and SharePoint benefited from Microsoft’s huge user base.

But Elasticsearch made an early big impression in two ways:

- First, it ticked a lot of checkboxes. It was very good, very scalable, very fast, and relatively easy to deploy. Elasticsearch downloads quickly reached millions. You have to credit Shay Banon with masterful coding in the early versions.

- Second – and very important – Elasticsearch paired itself with two other very good open-source projects, Logstash and Kibana (ELK). The “ELK stack” or “Elastic Stack” use cases went beyond enterprise search to log analytics, just when “Big Data” hype was about to explode.

Our experience at the first Elasticon in 2015 was a revelation. Shay Banon received a rockstar-like reception at the keynote and took the time to introduce us to a prospect from Disney. There was palpable excitement in the air that we were all at the early stage of something big.

From an enterprise search perspective, we were also surprised at how many use case presentations there were about search and analysis of log data, including one about the Mars Rover. But despite Elasticsearch’s millions of downloads, neither Gartner nor Forrester paid much attention to Elastic in their research on the enterprise search space. Elastic didn’t seem to care.

After the summit, it dawned on us: “they’re going after Splunk.”

Enterprise search is a multi-billion-dollar industry, but the “Big Data” / log analytics market that Splunk dominated was worth perhaps ten times that. This market incorporates analytics for business transactions, the emerging IoT (Internet of Things) market, and security-based use cases like SIEM (Security Information and Event Management).

Big Profits from Big Data

This was the first time that David was taking on Goliath, though you will never hear Elastic say this explicitly. They were taking on Splunk, the log analytics “gorilla”, armed with a great technology stack and the halo effect of being open source. Better, sexier, and cheaper.

Fast-forward six years, and a lot has changed. Elastic received $70m in funding, launched an IPO, and in 2021, annual revenues exceeded $600 million, a staggering 48% increase over 2020. With the growth, some of the halo effect wore off. In the open-source community, there’s almost an unwritten commandment that says “thou shalt not make TOO much money.” Elastic’s success certainly came with growing pains, and managing a public company with demanding shareholders is no picnic.

But a disruptive trend in IT loomed: everything was moving to “the cloud”. Technology executives everywhere scrambled to develop a cloud strategy, including how to deal with the leading vendors in the market. If you liken the cloud market to our solar system, Alibaba, Oracle, IBM would be smaller planets and asteroids, Google would be Saturn, Microsoft is Jupiter. And shining bright and smack in the middle is the Sun – Amazon.

Elastic, The Cloud and World Domination

Everything in IT is now about the cloud. Everything.

Elastic offers many of its services as cloud-based offerings, and while some of those services are proprietary, the dominant Elastic Stack is still freely available. Most companies today look to deploy managed services versions of Elasticsearch and Kibana with one of the three top cloud providers: Google, Microsoft, or Amazon Web Services (AWS).

Looking to capitalize on this, Elastic announced the Elasticsearch Service for Google Cloud and Elastic Stack for Microsoft Azure partner solutions. Presumably, Elastic benefits from some revenue stream and visibility into the deployment of their technologies with these partners. Conspicuously absent was any collaboration with AWS.

AWS has always leveraged open-source technologies to improve the range of services available on its cloud.  Amazon launched CloudSearch in 2012, starting with its own A9 technology, but quickly switching to Solr, the leading open-source search engine at the time. In 2015, with the increasing popularity of Elasticsearch, AWS launched the Amazon Elasticsearch Service, without collaborating with Elastic. Banon and Elastic management were probably incensed, but Elastic was focused on other things, and the AWS relationship took a back seat.

In 2016 Elastic announced the launch of several commercial packages of its technology, including Elastic Cloud and X-Pack. X-Pack was a commercial packaging of Elasticsearch, Logstash, Kibana, and Beats. To justify its pricing, X-Pack included proprietary features like security and management, to help Elastic monetize their open-source assets. Elastic revenues grew to $160 million culminating in a successful IPO in 2018.

Elasticsearch vs OpenSearch : The Last Straw

The straw that broke the camel’s back came in February 2019. Amazon announced support for Open Distro, the open-source community’s response to X-Pack. Open Distro was a branch of Elasticsearch and Kibana, and Amazon contributed security and management enhancements, making it a direct competitor to X-Pack. As documented in our first blog in this series, things got ugly quickly with Elastic launching a lawsuit claiming copyright infringement.

In early 2021, Elastic finally felt compelled to protect its business and shareholder interests by changing its licensing model. Amazon responded by morphing Open Distro into the OpenSearch project. Elasticsearch vs OpenSearch and the rift between Elastic and Amazon became very public, and blog posts and tweets from Shay Banon told you this didn’t feel like business. It felt personal.

From Banon’s s point of view, it must feel like you opened a great restaurant and even shared your best recipes. Your restaurant became a hit, and some chefs came to dine. Then one day, you find out that one of the chefs has added your recipes to their menu without asking. That would make anyone go on an expletive-filled Gordon Ramsey rant, wouldn’t it? Maybe not a perfect analogy, but probably close.

The last questions to examine relate to Elastic’s licensing change. What is the licensing model, and who is impacted? Is Elastic still an open-source technology company?

What is SSL and Elastic License v2?

Elastic seemed to be targeting Amazon’s “misbehavior” when it changed its licensing model in 2021. Instead of the permissive Apache 2.0 license, Elastic is giving users the option of choosing Elastic License 2.0 (ELv2) or Server-Side Public License 1.0 (SSPL). Elastic explains the licensing changes on a purpose-built FAQ page on their website.

ELv2 is a brief license that clearly spells out that Elastic IP cannot be used to provide managed services that include Elastic software functionality to third parties (customers). This clearly targets SaaS and IaaS providers, including dominant platforms like AWS.

SSPL is a “source-available” (vs. “open-source”) software license model introduced by MongoDB in 2018 to protect its ability to profit from its intellectual property while facilitating a community model for code base contributions. SSPL stipulates that any third-party service provider that incorporates SSPL-licensed software must also release the entirety of their source code under SSPL.

If you are a SaaS or IaaS provider that embeds Apache 2.0 Elastic code or products, you face two unpleasant choices. ELv2 forces you to migrate away from Elasticsearch, and SSPL would force you to open up your entire solution’s code base. Negotiating a business relationship with Elastic is also a viable, if complicated option.

As pointed by Technology Analyst Christopher Tozzi in this article in ITPro Today:

“That’s a big deal for public cloud providers like AWS, which offers a managed service based on Elasticsearch. The licensing change means that AWS can no longer use Elastic’s version of the Elasticsearch platform on its cloud.”

Christopher Tozzi, ITPro Today Tech Analyst

To protect its now substantial business, Elastic was willing to suffer any short-term adverse PR while inconveniencing many service providers that represent little if any revenue. One gray area is large corporations like Netflix, Expedia, and Capital One, who use Elasticsearch and may be broadly considered as SaaS providers. They probably consider AWS a more strategic vendor, and the Elastic licensing changes seems to have pushed them further into the Amazon / OpenSearch camp.

Is Elasticsearch still Open Source?

Technically, no. The real question, though, is “does it matter”?

SSPL is not recognized by the Open Source Initiative (OSI), and Apache 2.0 is the accepted standard. No matter how Elastic tries to spin it, that’s a fact. But now that business is booming, Elastic no longer needs the “halo” of open source. With a successful IPO, it also no longer needs to appeal to VC firms looking for “the next Red Hat”.

Elastic is doing what most successful companies that started as open source are doing: evolving. An article in the COSS Community site outlines the evolution of companies from fully open source to more protected community-driven models. Anyone can join and contribute to the “community”, but you have to abide by the rules. And Elastic owns and writes the rules for its community.

Rationalizing Elastic’s Actions

Someone once said that in politics, you can question someone’s actions, but not their motives. Taken as a whole, Elastic’s actions are easy to rationalize.

- Elasticsearch was created using a fully open-source model that made it wildly popular, both with developers and VC firms. When its assets grew to encompass Logstash and Kibana, the company changed its name to Elastic, and targeted the huge emerging “Big Data” market.

- The expanded target market helped Elastic raise over $70 million in funding and gave it much larger revenue potential (on the scale of Splunk). Elastic conducted a successful IPO and grew revenues substantially by offering training, support, and value-added products and services to their open-source assets.

- Like every technology company today, Elastic had to address the “megatrend” of everything moving to cloud-based service models. They established relationships with Google and Microsoft, offering the Elastic technology stack as cloud services. There was no deal with AWS, but given Elastic’s incredible recent growth rate, perhaps they feel they don’t need Amazon.

- Amazon’s support for Open Distro (and now OpenSearch) clearly threatened Elastic’s growth potential and fueled the Elasticsearch vs OpenSearch feud. Elastic changed its software licensing model simply to defend the business. After serving Elastic during its early growth period, the Apache 2.0 licensing model had outlived its usefulness.

Follow The Money

In the end, if you put aside the altruistic intentions of any open-source project, Elasticsearch vs. OpenSearch comes down to clashing business models on how to make money.

Amazon has always taken their cues from Walmart: offer quality products and beat the competition on volume and price. For AWS, this strategy includes leveraging IP from successful free open-source projects. The challenge for any open-source company like MongoDB or Elastic is to grow profitably in the long run. Both companies had to evolve from a pure open-source model to an open community-based model. This strategy is meant to please the majority of users, but most importantly, to please shareholders.

Wrapping Things Up…

In the next and last blog on Elasticsearch vs OpenSearch, we’ll cover the Amazon (and OpenSearch) point-of-view. If you enjoyed this post, please consider sharing it using the social media buttons below.

If you are struggling with deciding whether to use Elasticsearch or OpenSearch for your search-based applications, please CONTACT US for a free 1:1 consultation or explore our range of search application services.

Share on twitter

Twitter

Share on linkedin

LinkedIn

- OCTOBER 28, 2021

Graham Gillen

Graham Gillen

VP of Marketing for Pureinsights

In early 2021, on the heels of a major licensing change by Elastic, Amazon announced the OpenSearch project, a code branch of Elasticsearch and Kibana under the Apache 2.0 open-source license. In the third and last of a three-part OpenSearch vs Elasticsearch blog series, we examine Amazon’s point-of-view and reactions. Other blogs in the series cover the User point-of-view and the Elastic point-of-view.

Amazon’s Role in Fueling OpenSearch vs Elasticsearch

There are two ways to view the OpenSearch vs Elasticsearch debate. One is an evaluation of two search platforms, based on their features, functionality, and technical merits. Another is to view the two companies backing these platforms, making this an Elastic vs Amazon / AWS debate. That is because it’s questionable if OpenSearch would have gotten off the ground without Amazon behind the launch.

OpenSearch can trace its origins to Open Distro, which was a branch of Elasticsearch announced in 2019. There have been other middling attempts to branch Elastic code, such as Banana, a branch of Kibana that is meant to be paired with Solr. Open Distro had the advantage of launching with the support of AWS which lent much more weight to the open-source project. Amazon also contributed security, monitoring and management code to Open Distro, to try to make it comparable to Elastic’s X-Pack offering at the time.

One can speculate whether Amazon’s support for Open Distro was a hedge against a tumultuous relationship, or some distaste for how quickly Elastic cozied up to Microsoft and Google. “The friend of my enemy is my enemy”? Publicly, AWS wore a white hat and stated publicly that Open Distro was started in support of keeping the code fully open source.

In any case, Open Distro did not make a lot of waves in the market when it launched. If you were an AWS customer, your preferred option was still to use Amazon Elasticsearch Service – the “original” distribution of the code. That is, until Elastic’s license changes forced Amazon’s hand, leading to a “relaunch” of Open Distro as OpenSearch. As Elastic and Amazon’s lawyers racked up legal fees, Amazon was ultimately forced to drop its “pure” Elasticsearch service and create the Amazon OpenSearch Service. This move – with the full weight of Amazon’s backing – is what truly gave life to OpenSearch vs Elasticsearch.

Amazon’s History with Open Source

There are many examples of tech behemoths learning to “playing nice” with open source, most notably IBM’s acquisition of Red Hat, and Microsoft’s pivot to being more open source friendly. On the one hand, these were PR-driven moves to combat the “evil empire” image that these companies might have developed, but on the other hand, it was also a move to attract engineering talent that wanted more open, less “toxic” work environments.

There are parallels between these examples and AWS, but Amazon’s ultimate business strategy has always made it supportive of open source.  When your core business is running a massive cloud compute platform – much like a utility – it benefits you to support customers’ ability to run a low-cost / no-cost software stacks on top of your cloud to keep operating costs to a minimum. It would be like Elon Musk selling cars below cost to make money from Tesla charging networks.

Amazon Web Services (AWS) statement on open source

It’s Not Personal, It’s Just Business

In a recent interview with InfoWorld, it’s obvious that Elastic CEO Shay Banon still takes the feud with Amazon very seriously – and personally. He blames Amazon for forcing the Elastic license change and adds a personal anecdote.

“At a very high level, our approach—and Cloudflare’s approach and a few other companies’ approach—is similar, which is like if there’s a bully in the schoolyard… At some point you need to stand up and say enough is enough.”

Shay Banon, Elastic CEO

Banon may feel justified in calling Amazon a “bully”, but being much bigger than a foe doesn’t automatically make you a bully. Amazon is just leveraging the considerable influence it has in the market. A tiger can’t change its stripes.

This reminds me of a scene in the classic movie Casablanca. Nefarious character Ugarte (played by the brilliant Peter Lorre) says to our hero Rick (played by Humphrey Bogart): “You despise me, don’t you?” Rick’s response? “If I ever gave you a thought, I probably would.”  Amazon doesn’t seem bothered by what Banon thinks or what Elastic does. AWS is clearly focused on trying to make OpenSearch a successful open source branch of Elasticsearch (and Kibana).

In the article, it seems even Banon is somewhat relieved, now that Amazon had to change the name of their Elasticsearch service to the Amazon OpenSearch Service. The battle lines are very clearly drawn in OpenSearch vs Elasticsearch. There may never be a clear “winner”, but the market wins when there is choice.

Closing Advice for Our Customers on OpenSearch vs Elasticsearch

Pureinsights prides itself in being a technology-agnostic firm. We always let a customer’s technical and business needs dictate how we deliver a solution.

- If a client is struggling to choose between different search engine platforms, we usually advise anecdotally that there is an 80 percent overlap in functionality between the top solutions. We can always work with the one you choose that best fits your needs.

- In addition to analyzing the technical merits of Elasticsearch vs. OpenSearch, it’s also important to ask yourself “who do I consider my most strategic IT vendors?” Is it AWS? Or do I lean towards Elastic (and maybe Google or Microsoft)? Our first blog in this series provided a rudimentary set of decision trees for OpenSearch vs Elasticsearch.

In the end, we can help our customers with either Elasticsearch or OpenSearch in their search-based applications.

Concluding the Series…

This concludes our three-part blog series on OpenSearch vs Elasticsearch. We’ll cover Elasticsearch and OpenSearch in more depth as well as latest developments in future blogs. If you enjoyed this post, please consider sharing it using the social media buttons below.

For a free 1:1 consultation to further discussion the evaluation of OpenSearch vs Elasticsearch, please feel free to CONTACT US or explore our range of search application services.

Table of Contents

Elasticsearch vs OpenSearch : The Elastic View (Part 2)