How to Set Up a GraphQL Endpoint on a Database

Introduction

I have been working around databases for about four decades (that does date me!). From the early days of System R and Ingres, through the commercial engines of DB2 and Oracle, the open sources of MySQL and Postgres, to the current generations of NoSQLs like MongoDB and Cassandra and scalable SQL like CockroachDB and Yugabyte, anyone who has predicted the demise of databases has proven to be wrong. SQL as the query language has persisted, evolved, and improved, but the basic select * from foo where x = 1 group by y  is the language known to hundreds of thousands of developers. Why is that? Because databases just work, and how can you say that about too many things?

As a frontend developer, you want to see data in logical business constructs. Say a customer has one or more addresses, then your React application would love to see data like this:

7 Key Considerations for Building and Running Your Frontend APIs

Frontend developers want to build awesome experiences. Yet they need data from the backends and perform actions against backends. The answer to their problem is APIs. Who builds those APIs? Are they built quickly or are the frontend developers left waiting? Who runs and manages the APIs? After all, the backends do not behave in uniform ways — they speak different languages, emit differently shaped data, have varying authentication requirements, and so on. So running and managing the frontend APIs is not a task to be taken lightly.

Can You Get the Data you Need for User Experiences?Here are some considerations as you think through the APIs that are the gearbox between the frontend and backends.