> On the other hand, when you are the one to implement the Graphql server, it feels like writing your own database. You have to create a query plan, handle opti

> On the other hand, when you are the one to implement the Graphql server, it feels like writing your own database. You have to create a query plan, handle optimizations, corner cases, etc. I know right. It's best to just push all that to the front end where other people have to do that. Where a 2 year junior devs has to create a saga framework to speak to the 52 web services on the backend because they need a First Name along side an account number. Then we can complain that the front end is a crazy mess and they don't know what they are doing. If I don't understand the problem, it's not my problem! Plus uncle bob and martin fowler haven't written a book about it so it must not work. /salty