Exercise 1: What Triggered the 2021 License Change, and the MongoDB Precedent — Possible Solution
====================================================================

WHAT TRIGGERED ELASTIC NV'S 2021 LICENSE CHANGE
------------------------------
Per this chapter, "AWS began offering its own competing hosted 'Amazon
Elasticsearch Service,' built directly on the same open-source,
Apache-licensed code — competing with Elastic's own commercial
offering without contributing revenue back to Elastic." Elastic NV's
own business model depended on paid, hosted/managed Elasticsearch
offerings and paid proprietary features built on top of its own open
core. AWS, using the freely-available Apache-licensed Elasticsearch
code, offered a directly competing hosted version of the same
software, capturing real commercial value from the open-source project
without that revenue flowing back to Elastic, the company actually
building and maintaining the underlying software. Per this chapter,
"Elastic's own explicit stated reasoning [for the license change was]:
preventing cloud providers from offering the software as a competing
managed service without paying back into the project" — the license
change was a direct response to this specific competitive dynamic.

THE REAL, DIRECT PRECEDENT: MONGODB'S OWN 2018 SSPL MOVE
------------------------------
Per this chapter, "this specific tension... isn't unique to Elastic;
MongoDB made an almost identical move for the same reason a few years
earlier, in 2018, introducing the Server Side Public License (SSPL) it
created specifically for this situation. Elastic's own later move
explicitly followed that real, direct precedent." MongoDB faced the
exact same underlying problem years before Elastic did: cloud
providers offering competing hosted MongoDB services built on
MongoDB's own open-source code, without contributing back to MongoDB
Inc. MongoDB's own response was to create an entirely new license
(SSPL) specifically designed to prevent this exact pattern, and
Elastic's own 2021 decision to adopt SSPL (alongside the Elastic
License) as one of its own new licensing options was a direct,
explicit follow-on of MongoDB's own earlier solution to the identical
problem — not an independently invented response.

WHY THIS WORKS AS AN ANSWER
------------------------------
It identifies the specific competitive trigger (AWS's own competing
hosted service built on the open-source code) using the chapter's own
wording, and names MongoDB's own 2018 SSPL creation as the direct,
real-world precedent Elastic explicitly followed, rather than treating
the two companies' decisions as coincidentally similar or unrelated.