Cost Attribution in Discord’s API

Setting the stage, featuring: Features!

Before we get into inspecting our Python interpreter, let’s set the scene and spend a little time on how features are expressed within Discord’s codebase.

The engineering team put together a list of feature groups that cluster our API endpoints and background tasks by related functionality. An example of one such feature group is chat, which includes the functionality required for sending, viewing, and editing messages in multiple contexts. This categorization system doesn’t attempt to accurately represent all product features, as its goal is to provide an abstraction that is useful for cost and reliability tracking for subsets of the API.

Below are a few of the formal feature definitions that make up the