I expect them either not to change their practice and be at risk of lawsuit or change them to avoid lawsuits that they weren't at risk of anyway. For all its claims of logic and fact-based rationality, tech regularly exhibits feelings-based gregarious behaviors.

> whether devs will just change software licenses or change their practice away from REST.

I've gone pretty hardcore to GraphQL over REST already

Pretty stoked on it tbh

Do these terms not designate two very different kind of concepts that aren't interchangeable and can even be combined?

apologies if im not reading your question clearly

but yeah, they're mostly incompatible protocols, but they CAN work together.

GraphQL doesn't care about the datasource, your resolver's are allowed to reach out to whatever source they need too to fulfill the expected schema, and that can include internal or external REST points

but if we're talking regulation/legislation/legal-whatever on REST APIs? SOAP and GraphQL and other protocols wouldn't be covered by it I wouldn't think

Thanks for the elaboration, I was confused about what GraphQL is. I thought it had more to do with data representation and storage, competing with relational and NoSQL databases, with neo4j as one of its implementation.

I understand the confusion for sure, for a while that's what I thought it was too.

But no it's a Schema + Query Language implementation. The layer is responsible for compiling the schema and parsing/reading submitted queries into execution plans.

From there it calls upon a series of resolvers. The resolvers are blank and you're free to do whatever you want in them :) (they can even be async!). Many implementations like Apollo even support WebSockets :)

Thanks for the details!