Title: Graphql is great, but is totally over hyped. This is probably more of a rant or a frustrated dev outburst.<p>but beginner to mid level developers are lead down the path of USE GRAPHQL especially on youtube... and this is just unfair and wrong.<p>The good:<p>- It makes working with describing the data you want easy<p>- It can save you bandwidth. Get what you ask for and no more<p>- It makes documentation for data consumers easy<p>- It can make subscription easier for you to use<p>- Can let you federate API calls<p>The bad<p>- It is actually a pain to use, depending on the backend you are using you&#x27;ll have to manage<p>two or more type systems if there are no code first generates in your language<p>- It doesn&#x27;t support map&#x2F;tables&#x2F;dictionaries. This is actually huge. I get that there might be<p>some pattern where you don&#x27;t want to allow this but for the majority of situations working with json api&#x27;s you&#x27;ll end up with a {[key: string] : T} somewhere<p>- No clear path for Api versioning you&#x27;ll end up with MyQueryV1.01 MyQueryV1.02 MyQueryV1.03<p>Don&#x27;t use Graphql unless you&#x27;re managing a solution&#x2F;problem set that facebook intended graphql for<p>Invest your time in a simpler solution then running to GraphQL first<p>thanks for reading my ted talk<p>please any senior dev&#x27;s drop your wise words so that any new dev&#x27;s can avoid tarpits
Upvote: