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

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.

Takeaways

1. 1

   Single-page applications require more efficient delivery of JavaScript and other assets, plus a publicly exposed API for dynamic data.

2. 2

   Apache Kafka, object storage, data warehouses, and visualization tools are presented as components for managing, storing, analyzing, and viewing streaming data.

3. 3

   Service-oriented architecture can separate concerns and enable parallel work, but the additional components introduce more scaling and operational levers.