In this workshop, you'll learn how to take your API strategy and connect it into your internal developer portal with GraphOS. We'll cover the important workflows in your API strategy and how they can be made self-service with GraphOS.
What you'll learn:
- Administering your API Platform
- Architecture patterns with federated GraphQL
- Integrating GraphOS into your developer workflows
- For API creators, self-service motions for shipping new features to production
- For API consumers, self-service motions for discovering and consuming APIs
⚠️ Before the workshop...
Helpful links
📖 How to use this companion course
You can use this course as a reference throughout the workshop. Here you'll find instructions, code snippets and exercise solutions that we'll be going through in the workshop.
Follow-along: Lessons starting with Follow-along are designed for you to follow along with the instructor! Do what they're doing, but on your own machines.
Exercise: Lessons starting with Exercise are designed to be an individual exercise for you to try your best to solve on your own! If you need help, you can pair with someone beside you, flag down a mentor or consult the solution in that same lesson.
What we're building
You may or may not have an internal developer portal, but the spirit of these efforts is to make your developers more efficient. Using the proper API strategy can increase the efficiencies you see and this is one of the many reasons enterprises have utilized federated GraphQL.
When using federated GraphQL for your API strategy, you can enable workflows for self-service contribution and consumption of your platform APIs. GraphOS makes this easy and gives the flexibility to integrate into whatever internal developer portal you have, whether it's backstage or a custom React app.
Introducing the Acephei API Platform! 🚀
The Acephei API Platform has the main purpose of helping developer create new experiences faster with minimal friction in deploying to production. It's a platform that allows developers to create, manage, and deploy APIs in a self-service manner.
We haven't decided on the exact internal developer portal yet, but we know of a few things we need to provide to developers of the organization:
- Centralized security rules and enforcement that developers don't have to think about
- Self-service motions for shipping new features to production
- Self-service capabilities for discovering and consuming APIs
GraphOS helps enables all of this and gives us the flexibility to integrate into our developer workflows in a way that makes sense for our organization.
You can join the workshop's GraphOS organization by clicking here.
Workshop goals
Throughout this workshop, we'll build our understanding of critical workflows in your platform APIs and how GraphOS can be integrated to enable those workflows.
By the end of our time together, you'll be able to:
- Explain the architecture you plan to use for your Platform APIs
- Establish workflows to support developers to contribute to your platform APIs
- Enable API creators to have ownership of the features they create
- Integrate GraphOS into your API platform, whether that's an internal developer portal or a devops strategy
Share your questions and comments about this lesson
Your feedback helps us improve! If you're stuck or confused, let us know and we'll help you out. All comments are public and must follow the Apollo Code of Conduct. Note that comments that have been resolved or addressed may be removed.
You'll need a GitHub account to post below. Don't have one? Post in our Odyssey forum instead.