The new kinds of building blocks provided by these technologies are straight out revolutionary for backend development! I think this has a lot to do with the declarative programming model they are following.
Backend development in the way it was done using Ruby on Rails, Laravel or Express.js will become less and less appealing since the abstractions offered by the mentioned technologies are increasing development speed and generally very cost-efficient.
GraphQL minimizes the data transfer over the network by letting client applications ask for exactly the data they need, thus also making the life easier for frontend developers! Having productive engineers also makes product iteration a lot faster and cheaper, which directly results in business value!
Finally, Serverless enables great deployment workflows and minimizes the overhead companies need to invest in DevOps.
How do you do backend optimizations with GraphQL? For example can I limit the number of records someone can ask for from the backend? Can I limit the time the query runs on my database from the backed? Can I change the order of joins so that my indexed column is hit first? Or hard set what index is used for that rare case that the database tries to use the wrong one?
Backend development in the way it was done using Ruby on Rails, Laravel or Express.js will become less and less appealing since the abstractions offered by the mentioned technologies are increasing development speed and generally very cost-efficient.
GraphQL minimizes the data transfer over the network by letting client applications ask for exactly the data they need, thus also making the life easier for frontend developers! Having productive engineers also makes product iteration a lot faster and cheaper, which directly results in business value!
Finally, Serverless enables great deployment workflows and minimizes the overhead companies need to invest in DevOps.