Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document API Umbrella developer integraiton options #133

Closed
1 task
brylie opened this issue May 8, 2015 · 3 comments
Closed
1 task

Document API Umbrella developer integraiton options #133

brylie opened this issue May 8, 2015 · 3 comments

Comments

@brylie
Copy link
Contributor

brylie commented May 8, 2015

There may be multiple options for developing custom code based on, and/or extending, API Umbrella functionality. Document available options including risks and benefits for each.

Deliverable

User Stories

As a developer
I need to know options available to integrate my code with API Umbrella
so that I can decide on which strategy to take when extending API Umbrella functionality

As a project manager
I need to understand how to integrate custom code with API Umbrella
so that I can create a development plan and specification

@brylie
Copy link
Contributor Author

brylie commented May 8, 2015

@GUI will you validate my assertions in the Integration options wiki document, and possibly expand a bit on the possibilities?

@GUI
Copy link
Member

GUI commented May 14, 2015

This all looks good, except I made a couple small adjustments, since our configuration is stored in Mongo, not Redis. Assuming I understand what config you're talking about, most everything like API backend configuration and API user accounts gets stored in Mongo. Redis is only used for tracking rate limits.

In terms of overall integration, though, if you're looking to build a dashboard on top of API Umbrella, then I think you'll predominantly be interacting with APIs exposed by the api-umbrella-web component. The APIs the web component provides should facilitate reading or writing the various bits of config out of the entire API Umbrella system. So while the APIs live in the web component, they typically have an effect on the other components, since all the components read and write out of Mongo for shared configuration. So for example, the web component provides APIs to read or write API users or API backends, but both of those end up impacting the router and gatekeeper components automatically, since those other components read config immediately from the Mongo database when changes are detected.

Does all that make sense and help with your integration planning? If not, definitely feel free to give me a holler, and I'd be glad to talk about things in more detail.

@brylie
Copy link
Contributor Author

brylie commented May 28, 2015

This looks good. I am interested in learning more about how to access the Gatekeeper directly, if possible. We also need to access analytics data (#140), and are not sure how to do that.

@brylie brylie closed this as completed Jun 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants