> Markdown version of [/videos/1206-single-server-global-reach-running-a-worldwide-marketplace-on-bare-metal-in-a-cloud-dominated-world?t=1373](https://www.wearedevelopers.com/videos/1206-single-server-global-reach-running-a-worldwide-marketplace-on-bare-metal-in-a-cloud-dominated-world?t=1373). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Single Server, Global Reach: Running a Worldwide Marketplace on Bare Metal in a Cloud-Dominated World

Can a global marketplace thrive on bare-metal monoliths rather than complex microservices? Discover how Chrono24 handles 9 million users effortlessly by mastering boring technology and modular architecture.

- **Speakers:** [Jens Happe](https://www.wearedevelopers.com/@jens-happe)
- **Event:** WeAreDevelopers LIVE
- **Published:** September 11, 2024
- **Duration:** 50:06
- **URL:** https://www.wearedevelopers.com/videos/1206-single-server-global-reach-running-a-worldwide-marketplace-on-bare-metal-in-a-cloud-dominated-world

## Summary

Chrono24 scales a global marketplace with 9 million monthly active users and 43,000 requests per minute using a contrarian approach: bare-metal monolithic application servers instead of cloud-native microservices. Relying on massive dual-EPYC hardware instances with 256GB of RAM and an ultra-fast in-memory caching layer built on Data Access Objects (DAOs), the engineering team averts the operational complexity, sprawling expenses, and distributed debugging nightmares inherent in modern cloud deployments. They strategically embrace a hybrid model to optimize load, utilizing Cloudflare for CDN and edge security, AWS S3 for 24TB of image storage, AWS Lambdas for on-the-fly scaling, and LLMs for catalog SEO, proving that bare metal and hyper-scale cloud features can effectively coexist.

The foundation of this system rests on stringent engineering principles prioritizing "boring technology" and strict interpretability, opting entirely out of opaque frameworks like Hibernate to ensure code is reliably debuggable. However, endlessly extending a monolithic codebase eventually leads to high cognitive load and tightly coupled "big balls of mud." To resolve the technical debt dilemma without sacrificing feature velocity, development teams bridge immediate product demands with continuous system architectural improvements.

To safely modernize the monolith, the engineering organization utilizes domain-driven design to untangle organizational borders and separate logic into a well-structured modular monolith. Developers extract legacy functionality using the strangler fig architecture pattern while maintaining the discipline of the scout rule to leave code cleaner than they found it. Recognizing that human discipline alone cannot prevent architectural regression, the team codifies system boundaries using automated ArchUnit tests in Java, permanently freezing legacy violations while mandating that every new feature adhere securely to collaborative design standards.

**Keywords:** bare metal server hosting, monolithic architecture scaling, cloud computing cost reduction, in-memory caching layer, data access objects, hybrid cloud deployment, AWS lambdas image scaling, domain-driven design, strangler fig pattern, scout rule code refactoring, modular monolith transition, archunit architecture testing, technical debt management, distributed system debugging, boring technology principle

## Chapters

1. **Marketplace structure and scaling to millions of users** (00:02) — An overview of the application scale and user demographics handled by the engineering teams.
1. **Evaluating bare metal versus cloud computing costs** (03:16) — Why managing physical servers avoids the complexity and high expenses of cloud-hosted microservices.
1. **Guiding principles and utilizing boring technology** (07:41) — Employing simple architectures and proven technologies minimizes unexpected production failures and maintenance headaches.
1. **Bare metal architecture and in-memory caching system** (13:23) — Handling massive request volumes using a replicated single application server backed by an ultra-fast caching layer.
1. **Integrating cloud capabilities in a hybrid architecture** (22:53) — Leveraging external cloud solutions for image storage, dynamic scaling, and machine learning features where bare metal struggles.
1. **Trade-offs of a monolithic bare metal system** (26:28) — Balancing the low operational costs and simplicity of a monolith against its deployment rigidity and regional latency.
1. **Recognizing the dangers of high code entanglement** (30:45) — Identifying when a highly coupled monolithic code base begins slowing down future product development and increasing cognitive load.
1. **Balancing technical debt reduction with feature delivery** (33:30) — Applying continuous refactoring and the strangler fig pattern to improve code health without halting business priorities.
1. **Restructuring the monolith using domain-driven design** (40:15) — Creating a modular monolith by defining specific sub-domains and enforcing structural rules with automated architectural testing.
1. **Minimizing systemic complexity for long-term scalability** (48:29) — Continually resisting unnecessary technical complexity by relying on strict engineering conventions and simpler operational cultures.

## Related Moments

- [Exploring hybrid models, monoliths, and serverless computing](https://www.wearedevelopers.com/videos/261-why-you-shouldn-t-build-a-microservice-architecture) (from "Why you shouldn’t build a microservice architecture ")
- [Comparing centralized mainframe history to modern cloud architectures](https://www.wearedevelopers.com/videos/797-cloud-as-the-new-mainframe-why-the-cloud-hype-does-not-reflect-the-dev-reality) (from "Cloud as the new mainframe: why the cloud hype does not reflect the dev reality")
- [Building scalable backends with a modular monolith](https://www.wearedevelopers.com/videos/100135-the-new-shiny-syndrome-how-to-avoid-tech-hype-traps) (from "The New Shiny Syndrome: How to Avoid Tech Hype Traps")
- [Managing high-traffic infrastructure without chasing technology hype](https://www.wearedevelopers.com/videos/1817-how-to-avoid-tech-hype-traps-josip-stuhli) (from "How to Avoid Tech Hype Traps - Josip Stuhli")
- [Modernizing legacy applications through proactive leadership](https://www.wearedevelopers.com/videos/1223-coffee-with-developers-babette-wagner) (from "Coffee with Developers - Babette Wagner")
- [Architecting the platform with modern cloud and mobile technologies](https://www.wearedevelopers.com/videos/64-shared-mobility-for-everyone) (from "Shared mobility for everyone!")

## Related Articles

- [Why Event-Driven Architecture Isn’t About Speed (and When You Actually Need It)](https://www.wearedevelopers.com/magazine/745-why-event-driven-architecture-isn-t-about-speed-and-when-you-actually-need-it)
- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)
- [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix)
- [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss)

## Related Jobs

- [Mid/Senior Full-Stack Engineer (Web-first)](https://www.wearedevelopers.com/jobs/ext/1210833-mid-senior-full-stack-engineer-web-first) at **SMG Swiss Marketplace Group**
- [Senior Backend Engineer (Java)](https://www.wearedevelopers.com/jobs/ext/19369-senior-backend-engineer-java) at **Bonial International GmbH**
- [Cloud Foundations Team](https://www.wearedevelopers.com/jobs/ext/1483289-cloud-foundations-team) at **GitHub**
- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**
- [Senior Software Engineer, Client Apps Platform](https://www.wearedevelopers.com/jobs/ext/1773893-senior-software-engineer-client-apps-platform) at **GitHub**
- [Senior Backend Developer — AI: MCP & Agent Engine](https://www.wearedevelopers.com/jobs/48297-senior-backend-developer-ai-mcp-agent-engine) at **basebox GmbH**