“The platform my system runs on is out-of-date.”
It’s a common complaint — but is the real problem “my system” or “the platform”?
Here’s the hard truth: we often blame our tools when the real issue is how we’re using them.
As Pogo famously said, “We have met the enemy and he is us.”
Design patterns didn’t start with software. Before the Gang of Four introduced them to software engineering, Christopher Alexander used patterns to explain how to make cities and buildings more livable.
His 1977 book, A Pattern Language, revealed how timeless design principles create spaces where people thrive.
Microservices promise agility and scalability, but there's a hidden pitfall that can derail your chosen architecture: shared data.
Imagine forgetting your electric tea kettle was on. No big deal ... it shuts itself off when it senses danger, like potentially burning your house down. This is the circuit breaker pattern in action.
One valid use case for stored procedures in operational systems can be to reduce round trips to the database for some transactions. In (some) databases, it can also mean running compiled code close to the database.
Both are more efficient in some cases, but it can also be more difficult to debug stored procedures than normal code.