How to Protect Existing GraphQL Endpoints using an API Gateway

You’ve spent months building a GraphQL API. The schema is just right, and your front-end developers are thrilled with it. At first it’s only exposed internally, so you’re not that worried about security, but then as different clients find out that you have this awesome API out there, they want to start using it as well. And oh, the mobile team wants to start taking advantage of this thing, which will introduce clients from all over the world.
As what was initially an internal/hobby project turns into an enterprise API that has a need for enterprise-grade security, you decide to harness the power of an API gateway and Arvata GraphQL Security Proxy to give you the confidence you need to ensure your endpoint isn’t at risk. While the gateway and the proxy work their magic to keep you protected, you get to focus on doing what you do best: developing an awesome API for your clients.

This video uses Layer7 API Management to demonstrate how to protect your endpoints.

Andrew Messer

Andrew Messer

Andrew is a 20+ year veteran of Enterprise Software with about half of his career spent in technical capacities and the balance in Sales, M&A, Global Services Leadership, Sales Strategy, and Portfolio Management. Andrew has been deeply entrenched in the API Management space since 2014 starting with CA Technologies acquisition of Layer7, followed by running the CA Global API Management Services practice and is now the CEO of a software startup focused on building innovative API security and integration solutions. Andrew's base of operations is Carolina Beach, NC. In his downtime, he enjoys spending time with his family in all things “beach” related, barbecuing and photography.

Share With Your Network

Share on twitter
Twitter
Share on linkedin
LinkedIn
Share on facebook
Facebook
Share on email
Email
Share on print
Print