MDB Weekly is a multi-format, weekly summary of information from the past week in Modern Digital Business. It's available as an article, an email newsletter, and as a LinkedIn newsletter. It will be published weekly on Mondays.
First up: New email course launched!
How do you keep your private data safe in the public cloud? Is it even possible? In fact, your data and your application are likely safer in the public cloud than in your private data center.
Introducing my new Basics of Cloud Security course!
This course will show you, at a high level, the guiding principles and policies you need to understand to keep your cloud-based and cloud-native application safe and secure.
This course is designed for technical executives, managers, and leaders who want to understand, at a high level, how to build a safe and secure cloud application. It’s also for cloud architects and senior developers who want to understand how to communicate basic cloud security principles to their company’s executives and leaders.
This is an email course, available from Atchison Academy. It is delivered as a series of emails, one lesson per email, one email per day until the course is complete.
Last week’s top story: Agility vs. Complexity in Cloud-Native Applications
One of the main motivations for using cloud-native application methodologies is to simplify our applications and their infrastructures. Cloud-native methodologies are designed around creating larger and more sophisticated applications without unduly increasing the application complexity.
And central to everything is agility. Our companies must be agile to meet and exceed the expectations of our customers, our shareholders, and the abilities of our competitors. Companies without agility are doomed competitively.
Simplicity and agility. We need them both—yet, there is a vicious cycle that works against this philosophy.
In a previous article, I discussed the tradeoffs between choice and complexity in building cloud-native applications. As a result, we tend to give our cloud-native service teams the ability to make their own decisions. By giving teams the ability to design, develop, and operate their services in ways that make sense to them, you increase their power. After all, teams that make their own decisions are innovative teams.
However, that increased choice came with a cost: complexity. As you enable teams to make independent decisions, they begin to make independent decisions—independently. The result is more complexity in your IT infrastructure. Complexity leads to a reduction in the ability to innovate rapidly. Complexity leads to stagnation. It’s the opposite of agility.
For a company to be agile, we must allow teams to make the necessary choices to accomplish their goals. Yet agility requires choice, which leads to complexity. As a result, complexity leads to reduced agility.
You can see how it’s a vicious cycle.
How can we keep agility in our company culture without it resulting in problematic IT and cloud-native application complexity?
Finally: Missing out on insights?
Are you subscribed to our email newsletter? If not, you miss some great insights—Modern Digital Business Insights. Thursdays are insights days. Every two weeks or so, on Thursdays, you’ll receive an article of interest to those building, operating, managing, scaling, and maintaining modern digital businesses based on modern applications at scale.
Plus, you’ll receive this newsletter — The MDB Daily Newsletter — delivered to your inbox each Monday morning.
Joining is absolutely free, plus you’ll receive a chance to win a free copy of one of my books, Architecting for Scale, or Overcoming IT Complexity, signed by me.