Does Moving Faster with Cloud and Analytics Make Systems Stronger, or Just More Fragile?
I’ve been part of projects where speed was the main goal: get into the cloud, adopt analytics, deliver results fast. And I’ve seen both sides of the outcome. Experienced architects usually know where cracks will appear. They design guardrails: cost controls, security measures, fallback plans. The systems may move fast, but they don’t break as easily.
But when less experienced teams push for velocity, it can get messy. You end up with fragile architectures, ballooning costs, and governance problems that only surface when it’s too late. Velocity without foresight usually leads to fragility.
That’s why I’m behind the State of the Database Landscape 2026 survey. It’s a way for the community to share what really happens when we chase speed - the successes and the failures. If you’ve lived this trade-off, I’d love to hear your story.
Share your thoughts - you'll also have a chance of winning a $250 gift card or the new SQL Prompt
