4 ms·
GraphQL should have been called FacebookQL and microservices should have been called Netflix-services. Otherwise hype-following developers think it's a good id
by nodejs_rulez_1 5y ago
GraphQL should have been called FacebookQL and microservices should have been called Netflix-services.
Otherwise hype-following developers think it's a good idea to just go ahead and use them, despite not having the unique needs and resources of neither of those megacorps.
- jmondi 5y agoWith GraphQL, I can generate most of my client libraries while, and when I am writing a web client using typescript, I have full type checking on my apps. This makes me as a solo developer so much faster than using rest, with 0 client library generators, and 0 type safety. If my API changes response, my front end generated library will fail compilation with a type error. Moral of the ramble, new tech is great – sometimes. https://www.graphql-code-generator.com https://www.graphql-code-generator.com
- alephu5 5y ago> With GraphQL, I can generate most of my client libraries while, and when I am writing a web client using typescript, I have full type checking on my apps. This makes me as a solo developer so much faster than using rest, with 0 client library generators, and 0 type safety. If my API changes response, my front end generated library will fail compilation with a type error. > Moral of the ramble, new tech is great – sometimes. > https://www.graphql-code-generator.com https://www.graphql-code-generator.com You can do this with a boring REST API too. Most frameworks can automatically generate a swagger file, and there is a tool to generate clients from this in lots of different languages.