> Markdown version of [/videos/100135-the-new-shiny-syndrome-how-to-avoid-tech-hype-traps?t=808](https://www.wearedevelopers.com/videos/100135-the-new-shiny-syndrome-how-to-avoid-tech-hype-traps?t=808). 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).

---

# The New Shiny Syndrome: How to Avoid Tech Hype Traps

Stop falling for the new shiny syndrome. Discover how to handle three million requests per second by ditching microservices hype and embracing delightfully boring architecture.

- **Speakers:** [Josip Stuhli](https://www.wearedevelopers.com/@josip-stuhli)
- **Event:** World Congress 2026 Europe
- **Published:** July 9, 2026
- **Duration:** 31:27
- **URL:** https://www.wearedevelopers.com/videos/100135-the-new-shiny-syndrome-how-to-avoid-tech-hype-traps

## Summary

The tech industry is famously susceptible to “New Shiny Syndrome,” frequently adopting massive-scale architectures like NoSQL, microservices, and Kubernetes simply because tech giants popularized them. Drawing from experience scaling SofaScore to 40 million monthly users and peak loads of 3 million requests per second, this talk dissects the reality of hype-driven development. Scaling successfully relies on assessing actual business needs rather than inheriting the overwhelming complexity of trendy, hyperscale tools.

Blindly migrating to NoSQL databases like MongoDB to achieve "web scale" often introduces silent replication failures, denormalization headaches, and data analysis roadblocks. Conversely, a well-tuned PostgreSQL relational database paired with PgBouncer for connection pooling and ZFS for rapid snapshots can easily handle massive transaction volumes. Similarly, microservices introduce severe debugging, serialization, and maintenance overhead for small teams. The golden rule of distributed systems is highlighted: "If your microservices use the same database, you're doing it wrong." Instead, utilizing a modular monolith linked to a lightweight job queue like NATS—avoiding the heavy complexity of Apache Kafka—yields better developer velocity and operational stability.

Infrastructure choices require the same pragmatism. Kubernetes offers profound orchestration flexibility, but running it on bare metal exposes a steep learning curve where a clean deployment slowly devolves into a fragile jungle of interdependent services. Meanwhile, cloud computing and serverless platforms (such as AWS Lambda or Aurora Serverless) efficiently abstract away server management but abstract away the consumption costs just as effectively, occasionally resulting in catastrophic "bill shock" when uncontrollable stacking occurs.

The core architectural lesson is to "keep it stupid simple" for as long as possible. Complexity is not a virtue; it is a tax that should only be levied when a specific bottleneck demands it. By embracing "boring" technology and scaling infrastructure dynamically based on real traffic constraints, engineering teams can stop firefighting architectural debt and maintain their focus on delivering tangible business value.

**Keywords:** tech hype cycles, nosql vs postgresql, pgbouncer connection pooling, microservices architecture traps, modular monoliths, database denormalization issues, kubernetes cluster management, bare metal infrastructure, cloud computing costs, serverless bill shock, aws lambda scaling, nats message queue, apache kafka alternatives, architectural debt management, longhorn storage replication

## Chapters

1. **Understanding system scale and tech hype traps** (00:00) — How operating a sports application with millions of concurrent users exposes the pitfalls of blindly chasing new technologies.
1. **Choosing relational databases over NoSQL for most workloads** (01:26) — Why abandoning schema-less NoSQL storage for tuned PostgreSQL with connection pooling restores performance and structural consistency.
1. **The hidden operational costs of microservices architecture** (07:19) — How arbitrarily dividing backend components into microservices fragments databases and creates complex debugging dependencies for smaller teams.
1. **Building scalable backends with a modular monolith** (13:28) — Why combining a modular monolithic codebase with asynchronous background job workers solves scaling bottlenecks without microservice overhead.
1. **Managing the complexity of bare metal Kubernetes deployments** (17:06) — How self-hosting Kubernetes on bare metal introduces critical learning curves and dangerous operational risks alongside its orchestration benefits.
1. **Evaluating the high financial costs of cloud computing** (21:50) — Why migrating intensive traffic workloads from fully managed clouds to on-premise hardware drastically slashes monthly infrastructure spending.
1. **Controlling billing spikes in serverless and AI adoption** (24:01) — How dynamically auto-scaling serverless database instances and experimental generative AI loops can trigger uncontrolled cloud billing spikes.
1. **Replacing complex Kafka deployments with NATS** (26:17) — How embracing lightweight, single-binary alternatives like NATS maintains high-performance pub/sub messaging while dodging overwhelming Kafka configurations.
1. **Prioritizing simplicity over technology hype cycles** (27:45) — Why keeping technological architecture persistently simple delays unnecessary abstraction debt and redirects software engineering focus toward generating business value.

## Related Moments

- [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")
- [Modern application stacks and real-time data requirements](https://www.wearedevelopers.com/videos/806-leveraging-real-time-data-in-fsis) (from "Leveraging Real time data in FSIs")
- [Debunking common cloud-native application architecture myths](https://www.wearedevelopers.com/videos/55-cloud-nativeapplications-what-s-the-buzz-about) (from "Cloud-nativeApplications- What’s the buzz about")
- [Historical examples of hype in software architecture](https://www.wearedevelopers.com/videos/1136-resistant-to-hype-how-to-avoid-being-deceived-by-technological-trends) (from "Resistant to hype: How to avoid being deceived by technological trends?")
- [Evaluating the hidden costs and false promises of microservices](https://www.wearedevelopers.com/videos/1817-how-to-avoid-tech-hype-traps-josip-stuhli) (from "How to Avoid Tech Hype Traps - Josip Stuhli")
- [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 ")

## Related Articles

- [Ignore the Hype: How to Avoid Being Deceived by Technological Trends](https://www.wearedevelopers.com/magazine/528-ignore-the-hype-how-to-avoid-being-deceived-by-technological-trends)
- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)
- [MLops – Deploying, Maintaining And Evolving Machine Learning Models in Production](https://www.wearedevelopers.com/magazine/115-mlops-deploying-maintaining-and-evolving-machine-learning-models-in-production)
- [Dev Digest 139 - Soft and hard queries](https://www.wearedevelopers.com/magazine/487-dev-digest-139-soft-and-hard-queries)

## Related Jobs

- [Principal Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1465908-principal-software-engineer-database-infrastructure) at **GitHub**
- [Staff Software Engineer](https://www.wearedevelopers.com/jobs/ext/1425755-staff-software-engineer) at **GitHub**
- [Senior Software Engineer, Client Apps Platform](https://www.wearedevelopers.com/jobs/ext/1773893-senior-software-engineer-client-apps-platform) at **GitHub**
- [Staff Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1470125-staff-software-engineer-database-infrastructure) at **GitHub**
- [Agile Full Stack Engineer](https://www.wearedevelopers.com/jobs/48325-agile-full-stack-engineer) at **synava GmbH**
- [Senior Backend Engineer, Blockchain (Smart Contracts)](https://www.wearedevelopers.com/jobs/ext/1940851-senior-backend-engineer-blockchain-smart-contracts) at **Bitpanda**