Few things to know
Once you done with development and publishing your APIs, then
How to secure this APIs
How to analyze usage of these APIs
Scale your APIs
Configure
to rate limit -> eg: 10 requests per minute
Internal(Private) and Public (APIs visible to others)
--
Public APIs need more
---
Due to visibility and scrutiny they have
If you have few, you may not bother
you might build embedding them with
security, logging , configuration, into actual API code
So when more and more requirements coming
Specially where micro service --> where APIs get broken
Note : Micro service are not APIs.
smaller APIs focus with specialized operations
Legacy APIs , what to do
API managment is a process of
- Building
- Publishing
- Securing
- Versioning
- Observing
- Scaling
- Cataloging
- Retiring
There can be more in future.....
We need to make a system to manage the lifecycle of APIs, so company can focus on adding value to core business (coding,..)
1. API Gateway
Handles the routing and management of all the APIs
through policies that apply to individual API or set of APIs
2. Developer portal
serves as self service hub - developers to access API documentation, sdks, and other resources needed for consuming APIs
3. API dashboard
Observe API usage
view key API metrics
manage variety of API analytics
4. Unified API central catalogue
organizing, cataloging, indexing and presenting all the public and Private APIs use in Organization
API management will add Flexibility and Power where
you are managing each API independently, to a Unified system where you are orchestrating a complete set of APIs as a product.
Create a API strategy align with your Companies goals - will save lot of resources and work efficiently
