DEV Community

loading...

Discussion on: First hands on the new Twitter API

Collapse
forsakenharmony profile image
Leah

Kinda disappointed they didn't actually make it a graphql endpoint, I thought that was the plan

Collapse
frenchcooc profile image
Corentin Author

I totally agree

Collapse
rhymes profile image
rhymes

Honest question: why would you have cared for a GraphQL endpoint if the REST API contains what you need (I'm talking about content, not form, let's assume the new REST API is already satisfactory in its content) ?

Collapse
forsakenharmony profile image
Leah

It's not necessarily that it's not a GraphQL API, it's that they seemed to have explored it for a long time at least to my knowledge, but then release an adaptation of REST to the public

Don't know if they use it internally

Thread Thread
rhymes profile image
rhymes

Sure, that could be.

I was curious about your preference over having an external GraphQL API over a REST one moreso than their internal architecture.

After all, unless they tell us, we won't know if internally they use GraphQL or RPC or whatever to have microservices communicate