GraphQL for beginners with JavaScript - learn GraphQL смотреть онлайн

Link to this course(special discount)
https://www.udemy.com/course/graphql-for-beginners-with-javascript/?ranMID=39197&ranEAID=Gw%2FETjJoU9M&ranSiteID=Gw_ETjJoU9M-v0zslS7iBTqUHYX3zHadVA&LSNPUBID=Gw%2FETjJoU9M&utm_source=aff-campaign&utm_medium=udemyads
GraphQL for beginners with JavaScript - learn GraphQL
What you will learn in this course ?
What you'll learnWhat GraphQL is & why you should strongly consider using it instead of REST apisHow GraphQL eliminates many of the problems REST api's experienceHow GraphQL Avoids Overfetching DataHow GraphQL Avoids Underfetching DataHow you can avoid many concurrent REST/HTTP requests by using GraphQLWhat the N+1 Problem is, and how to avoid it with GraphQLHow a GraphQL API is easier to learn, because of it's Discoverability featuresHow to build GraphQL API's from scratch using JavaScriptHow to consume a GraphQL API in your applicationsHow GraphQL provides the best possible performance for applicationsHow GraphQL makes teams more AgileHow GraphQL helps you to avoid Duplicate Server-side codeShow moreShow less
""Why should I learn GraphQL?""Obviously, you should use the right tool for the job, right? ... but often, what was the “right” tool, becomes the inferior tool, and frequently you don't even notice...The most popular way of talking to servers today, is using REST. REST offers a nice, easy to understand way of interacting with other servers, but think about this: Rest was introduced about 2 decades ago… That’s a long time in our world!Let me ask you a question: how much has software development changed in 2 decades? Heck, how much has software development changed in 2 years? A LOT!So, I think it’s fair to ask the question:Do REST api’s still make sense, considering how we write software today?To answer this question, let’s look at some of the problems with REST API’s:Problem - Many Concurrent RequestsMost non-trivial applications, make many concurrent REST api calls, before the app can even render a view… Why is this a problem? It might not be a problem, if the app has an excellent network connection (like our dev machines do), but it can be a horrible problem, on mobile devices with weak connections.When mobile devices make many concurrent network requests, the response is often very slow, and the app might seem unresponsive... and it may not work at all. This can result in a dismal user experience.So, how much should you care about mobile devices?Well, the majority of web traffic, comes from mobile devices, which often have poor network connections… and the next Billion internet users, will primarily be smart phone users... are you thinking about them?""Does GraphQL suffer from this problem?""Nope, GraphQL allows you to avoid this connection heavy behavior, by combining all your data queries, into a single server request, which greatly improves real and perceived performance.Problem - Multiple round trips to the server (Under-fetching Data & N+1 Problem)Sometimes, apps needs to fetch some initial data from the server, then the app might need to make subsequent requests, based on the initially returned data. In other words, your app might need to make multiple round trips requests to the server... This results in a slow app, and it can be a real server performance killer.""Does GraphQL suffer from this problem?""Nope, with GraphQL, you avoid this type of “chatty” communication, because GraphQL allows you to perform rich/deep queries, that fetch exactly what you need, in one round trip, and you’ll avoid the N+1 problem, that can kill your servers performance.Problem - Over-fetching DataOften, REST apis give you more data, then you need. For example, imagine you're fetching some information about a book, but you only need the books title and description, there's a good chance a REST api gives you all 50+ properties of the book... You're over-fetching data and you end up taxing your servers and clients, dealing with unnecessary data/bandwidth, which results in degraded application performance.""Does GraphQL suffer from this problem?""Nope, with GraphQL, you won’t fetch data that you don’t need, instead you create explicit queries, asking for exactly what you need, and the graphQL server provides just what’s needed... Nothing more, and nothing less.Problem - Discoverability & DocumentationImagine you’re a new employee, and you’re trying to figure out what your companies existing REST api’s have to offer. This can be quite a challenge. If your lucky, people are maintaining documentation on the api, but more often, you’ll need to ask someone, and/or dig through the code, just to figure out what's available.""Does GraphQL suffer from this problem?""Nope, figuring out a GraphQL API is easy.How’s this possible?Many of the features in GraphQL, allow the creation of excellent developer tools such as GraphiQL and Insomnia. Tools like these greatly improve API discoverability, which you'll learn in this course.With Gr