This happened when I was working for one of my previous employers. I had just joined the company and was working on a microservice that was consuming a REST api exposed by another microservice. There was this JIRA ticket I was working on and I was not sure about the data model exposed by this REST api call. At this point in time the adoption to OpenAPI / Swagger / RAML was just beginning. I was new and was... - Source: dev.to / over 2 years ago

Provide consistent and easy-to-use documentation. Provide an OpenAPI or RAML file that describes your API and the endpoints. Also, provide easy-to-use interactive online API documentation like Swagger if possible. - Source: dev.to / almost 3 years ago

Interesting the article jumps straight from REST to GraphQL and forgets Falcor[0] - Netflix's alternative vision for federated services. For a while it looked like it might be a contender to GraphQL but it never really seemed to take off despite being simpler to adopt. [0] https://netflix.github.io/falcor/. - Source: Hacker News / 8 months ago

- obviously netflix with falcor, EVCache and hundreds of other projects. Source: almost 2 years ago

I pushed for Falcor over GraphQL in 2016. I still think Falcor was a more elegant core idea, but the implementation, tooling, and community never materialized like it did with GraphQL, and now Falcor is relatively niche and obscure. Netflix wasn't willing or able to promote it like Facebook did with GraphQL. That was beginning to be apparent in 2016, but I liked the concept too much. Source: over 2 years ago

Netflix has two amazing aspects I think. One is obviously the movie infrastructure and the other the way they do data and state management. I would read up on https://netflix.github.io/falcor to get an idea what is involved here.to be honest I dont get the point of rebuilding the visual aspects of their web app, that part is trivial and also completely useless without the parts that matter. Source: almost 3 years ago