Anshulee Asthana shares some thoughts after researching GraphQL implementation details:
The Existing System
- SQL Server DB with SPs, functions, views, and queries. SPs are non-modular in the sense they join various tables and return values specific to the calls being made.
- Connection with the DB is using basic ADO.NET and not with EF/LINQ, etc.
- ASP.NET WebAPI2.0 (Not .NET Core) and Java-based APIs.
- Native Android, iOS and Web Clients. Some portion of the web clients bypasses the API and talks to the DB directly.
- WebClients: ASP.NET and React.
- A React Native-based app.
System Maturity
- System has been in production for few years now and is stable.
- As the system is in a competitive space, new features are always getting added apart from usual maintenance.
Customer Ask
Whether it makes sense to wrap our existing APIs into a GraphQL Endpoint.
For a new feature in the react app evaluate making the new .NET based APIs in GraphQL.
It’s nice that Anshulee shared this case study, especially because there’s relatively little involving GraphQL + .NET.