GitHub’s Migration to Microservices: Insights and Recommendations from Former CTO Jason Warner

Former GitHub CTO Jason Warner recently shared on Twitter that the biggest architectural mistake of the past decade was the blanket adoption of microservices, recommending a migration path of monolith → application → service → microservice.

Warner emphasizes that this guidance is a mindset, not a rule, and that company size matters: small teams (5‑50 people) should stick with monoliths, while larger organizations may benefit from microservices.

He defines services as core infrastructure components maintained by infrastructure teams, whereas microservices are small, often one‑off codebases that could be libraries or SDKs. Warner lists several reasons why microservices can fail, including difficulty in reasoning about large numbers of services, the overhead of managing sprawl, and the debt incurred by each custom service.

Warner also points out that scaling to dozens or hundreds of microservices introduces organizational challenges such as lack of infrastructure prioritization, ownership and boundary issues, and the need for additional tooling, increasing product and experience risk.

His recommendations for enterprises are:

Extend the life of monolithic applications as much as possible.

Start building services from infrastructure, not from applications.

When breaking monoliths, target large applications rather than small services.

Treat each new application as a virtual wall for the company.

Prefer libraries over microservices whenever possible.

The article then details GitHub’s migration process: identifying feature boundaries in the existing database schema, grouping tables into “schema domains” recorded in YAML files, selecting partition keys to split data, and using a query monitor to detect cross‑domain queries.

GitHub extracted core authentication and authorization services first, using Twirp (a gRPC‑style framework) for service‑to‑service communication, and then moved simpler features like webhooks and syntax highlighting to independent services.

To support the transition, GitHub built a self‑service runtime platform to reduce operational burden for teams creating microservices, resulting in a hybrid “monolith‑microservice” environment today.

Warner’s perspective is echoed by other developers who note that poorly designed microservices can be riskier than a well‑designed monolith, and that many companies have abandoned microservices in favor of larger, more manageable services.

References: InfoQ article, The New Stack interview, and Warner’s Twitter thread.