1. Resources
1.1. GraphQL | A query language for your API
1.2. MicroProfile Spec
1.3. MicroProfile GraphQL Examples
2. Demo
3. MicroProfile GraphQL
3.1. Handles all of the plumbing required to implement GraphQL in Microprofile apps
3.1.1. Code-first programming model and CDI integration
3.2. 1.0 - Feb 2020
3.2.1. Server
3.2.1.1. Queries
3.2.1.2. Mutations
3.3. 1.1 - Jun 2021
3.3.1. Minor changes
3.4. 2.0 - Soon
3.4.1. MicroProfile 5
3.5. Implementations
3.5.1. SmallRye
3.5.1.1. Quarkus
3.5.1.2. Open Liberty
3.5.1.3. WildFly
3.5.1.4. KumuluzEE
3.5.1.5. ?
3.5.2. Helidon
3.6. 2.1 and later
3.6.1. Client API
3.6.2. Subscriptions
3.6.3. Prototyped in SmallRye
4. Kito D. Mann
4.1. @kito99 https://virtua.tech Principal Consultant at Virtua: Consulting, training, mentoring on web dev and back-end Java
4.2. Java Champion
4.3. Google Developer Expert on Web Technologies
4.4. Co-host of Stackd Podcast (stackdpodcast.com)
5. What is GraphQL?
5.1. Alternate approach to client/server communication
5.2. Simple example
5.3. Does not use REST
5.4. Origins
5.4.1. Created by Facebook in 2012
5.4.2. Open sourced in 2015
5.4.3. Started in 2017
5.4.4. Used by many large companies
6. Why GraphQL?
6.1. Drawbacks of REST
6.1.1. Endpoint decides what data is returned
6.1.2. Data can be split amongst several calls
6.1.3. No specific data format
6.1.3.1. Layout of the data is up to the endpoint
6.1.4. No push standard
6.2. Benefits of GraphQL
6.2.1. Client decides what data it wants
6.2.1.1. Server decides where to get it
6.2.1.1.1. Well suited for BFFs
6.2.2. Single consolidated, dynamic endpoint
6.2.3. Subscriptions
6.2.4. Defined data format
6.2.4.1. Typed schemas