express-gateway VS stepzen-datalayer-microservices

Express Gateway: A microservices API Gateway built on Express.js. It's entirely extensible and framework agnostic, delivering robust, scalable solutions in no time.

Next, review deployment complexity such as DB-less versus database-backed deployments. For example, Kong does require running Cassandra or Postgres. Apigee requires Cassandra, Zookeeper, and Postgres to run, while other solutions like Express Gateway and Tyk only require Redis. Apache APISIX uses etcd as its data store, it stores and manages routing-related and plugin-related configurations in etcd in the Data Plane.

This post will show you how to build a policy (middleware) for your express gateway. Before creating a policy, we need to create a plugin.

For a complete example of using StepZen to combine microservices, look at this example repository. It shows more complex relations between types and microservices using, for example, the @sequence directive. In contrast to schema stitching and Federation, StepZen eliminates the need to write resolver code or edit your underlying microservices. But it doesn't stop there. You can deploy any GraphQL schema as a fully performant GraphQL server to StepZen. It takes the custom directives in your schema and transforms them into a data layer deployed in the cloud. No longer do you need to worry about how your gateway or data layer performs or scales, as no infrastructure needs to be managed by your team.