Daniel Ben-Shoushan

I Build Infrastructure Where Adding New Clusters/Regions/Products Requires Predictable, Minimal Effort

Most teams nail auto-scaling within their existing infrastructure. Where they struggle is provisioning new infrastructure and avoiding architectural pitfalls that cause catastrophic downtime. I design systems where infrastructure provisioning is fully automated and spot the anti-patterns that will break you at scale.

Let's Solve Your Impossible Problem

The Real Story

Most teams nail auto-scaling within their existing infrastructure - Karpenter handles that beautifully. Where they struggle is provisioning new infrastructure: new clusters, new regions, new environments. These operations are still treated as complex, manual projects.

"I build provisioning automation so reliable that spinning up entire new infrastructure becomes as predictable as deploying an application. This isn't just about speed - it's about disaster recovery. When you can provision your entire infrastructure from scratch automatically, you can recover from any catastrophe."

But here's what's equally important: I spot the architectural anti-patterns that will kill your system at scale, before they kill your system.

I've seen teams use Kafka incorrectly and watch their systems collapse when disk usage peaks. I've seen relational databases used as queues, caches used as primary storage, and "scalable" microservices architectures that created more problems than they solved. These aren't just performance issues - they're reliability time bombs.

How I Think Differently

I Automate Infrastructure Provisioning, Not Just Scaling

Auto-scaling is table stakes. I build systems where provisioning entire new clusters, regions, or product environments is a single, predictable operation. This means fast disaster recovery and zero-drama expansion into new markets.

I Spot Anti-Patterns Before They Become Disasters

Using Kafka incorrectly causes system collapse when disk usage peaks. Using relational databases as queues creates bottlenecks. I've seen these patterns kill systems at scale - I identify them early and fix the architecture before the crisis.

I Know When "Scalable" Architecture Actually Isn't

Microservices and event-driven architecture can create more problems than they solve when implemented incorrectly. I've built these systems under real constraints - I know which patterns work and which ones will hurt you later.

I Design for Catastrophic Recovery

When your entire infrastructure can be provisioned automatically from scratch, you're not just faster - you're disaster-proof. I've built systems that can recover from complete regional failures because the provisioning process is bulletproof.

I Choose the Right Tool for the Actual Problem

Wrong database choices, misused caches, over-engineered messaging - these decisions compound into system-wide problems. I've lived through the consequences of these choices and learned to spot them before they're implemented.

I've Built This Under Real Constraints

Multi-product environments, air-gapped deployments, bare-metal Kubernetes - I've solved these problems with actual deadlines and actual consequences. I know what works when the theory meets reality.

Ready to Think Differently About Your Infrastructure?

Tell me about the problem that's making your team grow but your systems harder to manage

I'll respond within 24 hours with specific questions about your architecture