Open andymc12 opened 3 years ago
I wonder if this should align with what we have for MP GraphQL guide itself.
Tagging @gkwan-ibm @AustinSeto to chime in.
@yeekangc My thinking was that we might want a separate guide to focus on the relationship between MP GraphQL and JPA. It's also a nice value proposition for using Open Liberty - which allows mixing of features that are specific to MicroProfile (MP GraphQL) and Jakarta EE (JPA). That way, the original MP GraphQL guide can focus on only MP features, while the new guide could highlight how the different technologies can work together.
Spring has a really nice guide for making JPA database data available as a RESTful service. What is cool about it is that it is pretty simple to put together an app that frontends the database.
MicroProfile GraphQL should be even simpler to frontend JPA entities - even from different data sources - and should have more compelling use cases. While REST is great for accessing data, it is subject to over-fetching and under-fetching where GraphQL gives the client exactly the data it needs. Effectively, GraphQL extends the database to the web.
@WhiteCat22 from my team is working on a sample that shows how a user could build a MP GraphQL service that frontends a database via JPA. I think a guide that builds on this (still under development) sample would go a long ways.