Code GraphQL Application with Java Spring Boot & Netflix DGS

Learn how to use Java Spring Boot + Netflix DGS to build GraphQL backend : read, modify, and subscribe for data change

What you'll learn
What is GraphQL and how it stands with REST API
When to use GraphQL
Design GraphQL schema
Build GraphQL backend using Java Spring Boot + PostgreSQL
Using GraphQL client to read, modify, & subscribe for real time data change

Description
What Is Graph?

I am graph, I go to work on graph. It's everywhere, really. I have a sister. Both of us has same parents. Our mom has parents, which is our grandparents from mom's side. And so our dad, which means we have grandparents from dad's side. And together, this is he "myself" graph. Tweet something on twitter, and it's a graph. See: 8 people likes the tweet, and 3 people retweet my original tweet, so this is the graph.

What Is QL?

QL in GraphQL is shorthand for query language. If it seems familiar, you are right. SQL, or the structured query language, has the same shorthand. SQL used to read and manipulate data in database. During SQL read, we can select multiple columns as we need, from one table, or several connected tables, usually through foreign key. The same way with GraphQL. Like SQL, a single GraphQL query can return multiple columns from connected data. We can also use GraphQL to change or remove data.

So What is GraphQL?

GraphQL is a query language which uses graph concept. GraphQL is also a runtime that needs to be implemented on the backend, so the frontend application can use it as the query language.

To implement graphql, we need runtime frameworks, which each programming language has their own implementation. GraphQL itself is a specification, means whatever the framework, it must comply to the graphql specification, so the user can use GraphQL without even need to know what the GraphQL backend language is.

GraphQL is a service, where we need two items for creating Graphql backend. First, is the schema, which represents GraphQL structure. It is like database tables and relationships. Second is the resolver, which is logic for each field on schema to represents data. A resolver tells how and where to access certain field. For example, whether to get field's data from database, or text file.

Some says GraphQL is "REST API killer", "The next REST API", et cetera.

But what is GraphQL and why facebook, netflix, github, and some large names shift their technology to GraphQL? Is it true that GraphQL is "REST API killer"? Or the contrary, it is "REST API friend"?

In this course, we will learn the GraphQL fundamentals, including data types, schemas, and graphql operations. We will learn using Java Spring Boot and Netflix DGS framework to easily build GraphQL Java application. In this course, we will not only learn theories, but do a hands-on coding using PostgreSQL as database.

Complete source code is provided for the course, so you will always stay up-to-date and have reference in case you are having difficulty (believe me, GraphQL will not that hard). If you are new to GraphQL, or if you've been trying to find out how to implement your own GraphQL server (especally using Java), but sometimes feel like you still don't quite understand, then this GraphQL course is absolutely suitable for you!

In this course, we will learn:

What is GraphQL

GraphQL schema, data types, and relationships

Creating your own GraphQL backend using Java Spring Boot and PostgreSQL database

If you ever writing REST API before, this course will expand your knowledge and see how easy you can implement GraphQL fundamental. It's not very different with REST API implementation, but at some aspects, it's more powerful.