All right so i was a little confused on where exactly to put graphql because it is used by a lot of front-end developers um but ultimately if you’re going to create a graphql server it’s back-end it’s basically a data query language for apis so in many cases we create and consume data using restful apis where we send a specific http request to a specific endpoint to get a whole bunch of data now graphql is used in a similar way except instead of having all you know all these different endpoints that return all all this different data even stuff you don’t need graphql provides a single endpoint and you can make queries based on the data that you need so you don’t have to get  verything if it’s an api where you know it has a bunch of user information and all you need is the first and last name you can make a request or a query to get just the first and last name the queries that you send to a graphql server are formatted similar to json which is the format of the response as well so your request or your query looks like the response um if you already know javascript you already know json then making queries is really easy to learn there’s a popular client called Apollo that can be used on its own or with a framework like react to communicate with a graphql server which you can implement with you know node.js and other languages as well it’s more targeted than a traditional rest api and it saves you a bunch of trips to the server and it also works great with real-time applications so i wouldn’t call graphql something that is required to learn but it is pretty popular and i don’t see it going anywhere so once you learn you know the fundamental technologies that you need to learn graphql might be something that you want to look into. Learn web development. or higher The Digital IO.