---
title: "Beyond Web and Worker: Evolution of the Modern Web App on Heroku"
description: "Over a decade, the standard Heroku web application has expanded from a web process, database, worker, and Redis queue into a broader architecture for web, mobile, data, and operational demands. The post connects this shift to snappier single-page experiences, native smartphone apps, APIs as integration surfaces, growing streaming data, increasing system complexity, and scale. Its proposed components include a content delivery network, API Gateway, Apache Kafka, object storage, data warehouses, and query or visualization tools, alongside service-oriented architecture and scalable-first design. The architecture separates functionality into smaller services for adaptability, while acknowledging that more components create more scaling and operational levers. It presents Heroku’s PaaS and managed services as a way to reduce that burden, then leaves deployment, communication, CI/CD, monitoring, and security as topics for follow-up posts."
---

# Beyond Web and Worker: Evolution of the Modern Web App on Heroku

[Heroku](https://yomu.fyi/company/heroku) · Chris Castle · Aug 14, 2018

**Type:** Explainer

## Summary

Over a decade, the standard Heroku web application has expanded from a web process, database, worker, and Redis queue into a broader architecture for web, mobile, data, and operational demands. The post connects this shift to snappier single-page experiences, native smartphone apps, APIs as integration surfaces, growing streaming data, increasing system complexity, and scale. Its proposed components include a content delivery network, API Gateway, Apache Kafka, object storage, data warehouses, and query or visualization tools, alongside service-oriented architecture and scalable-first design. The architecture separates functionality into smaller services for adaptability, while acknowledging that more components create more scaling and operational levers. It presents Heroku’s PaaS and managed services as a way to reduce that burden, then leaves deployment, communication, CI/CD, monitoring, and security as topics for follow-up posts.

## Context

The standard web application architecture described for Heroku in 2008 consisted of a web process, database, worker process, and Redis queue. By 2018, richer browser experiences, native mobile apps, public APIs, rapidly growing data streams, increasing system complexity, and larger scale requirements created demand for a broader architecture.

## Approach / What changed

The proposed high-level architecture adds a content delivery network, API Gateway, Apache Kafka, object storage, data warehouses, and query or visualization tools. It also uses service-oriented architecture for adaptability and scalable-first design, while positioning Heroku’s PaaS and managed services as a way to reduce operational scaling complexity.

## Takeaways

- Single-page applications require more efficient delivery of JavaScript and other assets, plus a publicly exposed API for dynamic data.
- Apache Kafka, object storage, data warehouses, and visualization tools are presented as components for managing, storing, analyzing, and viewing streaming data.
- Service-oriented architecture can separate concerns and enable parallel work, but the additional components introduce more scaling and operational levers.

**Tags:** [API](https://yomu.fyi/topic/api), [Architecture](https://yomu.fyi/topic/architecture), [CDN](https://yomu.fyi/topic/cdn), [Kafka](https://yomu.fyi/topic/kafka), [Microservices](https://yomu.fyi/topic/microservices)

- Source: [Heroku](https://www.heroku.com/blog/modern-web-app-architecture)
- Source URL: https://www.heroku.com/blog/modern-web-app-architecture
- Ingested by Yomu: 2026-09-09T14:26:45.362Z

[Read original post](https://www.heroku.com/blog/modern-web-app-architecture)