Background

In order to T329419: Architect potential API Gateway Patterns in preparation for services migrated off RESTbase, we need to understand as much as possible about the current callers to the various services routed through RESTbase. As part of gathering requirements for T262315: <CORE TECHNOLOGY> API Migration & RESTBase Sunset, we need to separate the various use cases, so we can create a solution that solves for separation of concerns to the best of our ability.

This is a blocker for decision making on a solution as discussed in this conversation thread.

Product goal:
RESTbase deprecation is a use case that will help us define critical pieces of API infrastructure and prepare API Platform to support full production traffic across new and pre-existing services.

The goal is to have a routing solution in place for services migrated off RESTbase by end of March. This means the turnaround time for this data is a little less than a week (no later than Feb 22, 2023).

Collect data per service

In the webrequest dataset, what are the total number of hits for the past three months on api/rest_v1 URI path (segmented by all available endpoints) per: user_agent, user_agent_map, access_method, and ip?

Acceptance Criteria

• We have all available/discoverable data that will help us understand current client/caller requirements
• We can infer from this data a set of client/caller types
• We can infer the various config requirements these clients/caller types require in contrast to each other
• This data is collected on a per service level
• data is available in a a csv file, report, or visualization tool

Artifacts & Resources

Current API Gateway with Needs and Questions Diagram
RESTbase Routing Diagramming
Wikimedia REST API Swagger docs
Grafana: RESTBase external overview
https://www.mediawiki.org/wiki/Core_Platform_Team/Decisions_Architecture_Research_Documentation/Services_Architecture_Recommendations_(2019)#/media/File:Services_Architecture.png