> you have a full backend accessible via GraphQL. Add some event triggers and you can hit rest endpoints from changes in your db. Add some custom actions and yo

> you have a full backend accessible via GraphQL. Add some event triggers and you can hit rest endpoints from changes in your db. Add some custom actions and your fe can hit your rest api for more complex tasks without leaving gql land a) You're assuming everyone agrees GraphQL is always the way to go, which is far from common wisdom. Why is superior - especially for MVPs? b) You're assuming that create CRUD MVPS in something like Python/Ruby/Node is slower/more complicated than what you're describing here, which is also far from certain. If we're talking about Hackathon style level of code they are all perfectly capable in building CRUDs really quickly. I'm not saying you're necessarily wrong, I just think you haven't thought hard enough about the tradeoffs.