Background/Goal

The current API Gateway is a proof of concept/alpha piece of infrastructure maintained by a single SRE. It is not known if it will be able to scale to meet the needs required by services that will migrate off RESTbase T262315: <CORE TECHNOLOGY> API Migration & RESTbase Sunset. The goal is to get the API Gateway ready to route RESTbase services with full production traffic.

Use Case

Sunsetting RESTbase T262315: <CORE TECHNOLOGY> API Migration & RESTbase Sunset requires that the services have an infrastructure to route through.

An architectural solution for external client calls (including WMF mobile and web apps) routing to services deprecated off RESTbase is required to unblock the overall RESTbase deprecation process.

User Story/ies

As a developer working on RESTbase sunset, I need a reliable API Gateway, so I can confidently reroute services away from RESTbase.

Outcome

API Gateway can support all of RESTbase services needs once they are migrated out of RESTbase.

Objective(s)

O: API consumers receive equitable and secure access to data for their projects.

Key Result(s)

KR: Decrease time and effort required to create and deploy new APIs
KR: Consumers understand all throttling and rate limits at the API and database levels [decrease in 429 errors]
KR: Consumers see a continuous stream of  XX# per /month improvements & fixes that meet new and existing use case requirements
KR: Consumers can see and understand real time usage, issues, and analytics for 6 APIs

Acceptance Criteria

• To be discovered
• Deadline: End of February/Early March

Key Tasks & Dependencies

• TKTK

Artifacts & Resources

Link to diagrams TKTK
Link to PRD TKTK