12 ms·

How does this affect people providing “search” functionality of arbitrary items, but not Elasticsearch itself (AWS)? Where is the line drawn? Is the SSPL vague

• cduzz 6y ago
  So, let's say you've got a product catalog in some SQL database. Your business processes update inventory and availability and leadtime and such in that database. But you really like the lucene natural language search functionality, so you copy your database into a lucene database for searching. But hey, elasticsearch takes care of a bunch of tedious problems, so instead of using raw lucene, you use elasticsearch... So, you've got a PHP web application that queries this cache of the catalog stored in elasticsearch; what's your legal liability?
  • dhd415 6y ago
    None. That's clearly not offering Elasticsearch-as-a-service.
    • hbogert 6y ago
      how is that clearly? What if your UI over time provides the mechanisms which are isomorphic to the functionality provided by ES? This will be a nightmare if ever tried in court.
• EwanToo 6y ago
  This is the crux of the problem. If you're purely processing internal logs on an internal service, you're probably good. If you're exposing an API or a UI to paying customers which calls Elastic search to run a query, then it's maybe not great. Everything needs to be caveated with "maybe" or "possibly", because nobody knows how it'd go in court.