We all hear a lot of good things about GraphQl and we all are aware of the benefits which we get using that. In short, we can say GraphQl as the query language for APIs at runtime for fulfilling those queries with the existing data. Its kind of selective querying of data. If we use graphQl combined with the Typescript it provides a better type safety with your graphQl queries, giving us end to end type safety. I will further deep dive into the Type Generation on Front End later in the next blog. I got a chance to get hands on to all these professionally and I would say it has so much of a learning curve that I still get to learn a lot of stuff everyday

Image for post

So before continuing on the blog further, I want to call out one thing for the backend I am going with NodeJs, but GrapQL is a wrapper layer on top of our backend so we are free to go with creating our API’s in any other language.

So, just check for node installed in your machine by running — node -v

So the very first step would be itself a big one to Create an API in NodeJs and MongoDB this could be again a very big topic but will try to keep this not long

I personally feel Express is a really cool Node framework that’s designed to help JavaScript developers create servers really quickly on the fly.

So let me put out the basic use case I am trying to solve which is the restaurant’s list page

#apollo #nodejs #mongodb #web #graphql

Building Complex Web App Which Is Data and Assets Heavy with GraphQl, NodeJs and MongoDB (Backend)
2.00 GEEK