I think you need to qualify this a little better. For example, 100GB data is relatively small. Would easily fit in a single AWS i3.large. But what's going to be your analytical load? How many queries

Is it ES [the software] that is bottlenecking, or could it be the HW you have it running on? If the HW isn't the issue, have you been able to trace where the issue is in ES? I hate to be "that guy," b

It would only affect the use of JanusGraph+Elastic if you were offering it in an -as-a-Service (-aaS) offering, like a commercial DBaaS. In which case the SSPL would require you to commit back to the