Kyle Brown

Grand Hallway of the Library of Congress
Grand Hallway of the Library of Congress
The Great Hall at the Library of Congress: an example of repeating patterns

I’ve written before about how I’ve been involved with writing and using Software Patterns for well over twenty-five years now. But even with that amount of experience, one of the things that keeps me excited about the field is that I found that I can always learn new things and new approaches by reading patterns written by others and by writing my own.

One of the more unusual projects I’ve been involved with has also been one of the longest patterns projects that I’ve been involved with. It all started back in early 2016 when several things came together all…


Kyle Brown, IBM Fellow, CTO Cloud Architecture

No matter how you accumulate your debt, it has to be paid back

Let’s face it, 2020 was a weird year. One of the smaller oddities was that for the first time since 2012, the U.S. Personal savings rate grew (and at a phenomenal rate) rather than holding roughly steady [1]. While most of this is pandemic-related, it may partially be a sign that consumers have begun to realize that you can’t just keep borrowing without repaying debts you have incurred. What I wish would occur is that businesses would realize that the same principle applies to technical debts just as much as it does to…


Kyle Brown and Kim Clark

One of the most common features of Cloud Native development that we constantly hear touted as being of supreme importance is elastic scaling. Many companies have told us that they see taking advantage of Elastic Scaling as being a key requirement for their teams evaluating cloud platforms. However, we rarely hear those same teams tell us why they need elastic scaling.

In fact, we might go so far as saying Elastic scaling is one of the hallmarks of “being on the cloud”. All cloud platforms that bear up under the name have some sort of…


Kyle Brown and Kim Clark

Note: This is part 5 of five-part series. For the first article in the series, start here or jump to Part 2, Part 3, Part 4

In our past articles, we’ve established “what” cloud native refers to and even “how” cloud native works. However, there’s a bigger, more fundamental question we haven’t addressed. Why should anyone care? …


Kyle Brown and Kim Clark

Note: This is part 4 of a multipart series. For the first article in the series start here or jump to Part 2, Part 3, Part 5.

While the people, process, architecture and design issues we covered in the last two articles are all critical enablers for cloud native, cloud native solutions ultimately sit upon technology and infrastructure, which is what we’re going to cover in this article.

Ingredients of cloud native — Technology and Infrastructure

Cloud infrastructure is all about abstracting away the underlying hardware to enable solutions to be rapidly self-provisioned and scaled. It should enable administration of different language and…


By Kyle Brown and Kim Clark

Note: This is part 3 of a multipart series. For the first article in the series, start here, or jump to Part 2, Part 4, Part 5.

In our previous article in this series we discussed how a move to a cloud native approach might affect how you organize your people and streamline your processes. In this post we will drill down on how it relates to architecture and design principles.

Ingredients of cloud native — Architecture and Design

It is the architectural approach that brings the technology to life. It is possible to deploy traditional, siloed, stateful, course-grained application components onto…


Kyle Brown and Kim Clark

Note, this is part 2 of a multipart series. You can find part 1 here , or jump to Part 3, Part 4, Part 5.

In the previous article, where we discussed what cloud native actually means, we established that to achieve the desired benefits from a cloud native approach you needed to look at it from multiple perspectives. It is about not only what technology you use and where your infrastructure is located, but also how you architect your solutions. But perhaps most importantly, it is about how you organize your people and what…


Kyle Brown and Kim Clark

Note: This is part 1 of a multipart series You can jump to Part 2, Part 3, Part 4, or Part 5.

All too often, conversations around cloud native dive straight into technology choices like containerization and microservices. These are definitely potential ingredients of a cloud native project, but they are most certainly not the whole picture. Across this article series we will explore cloud native from several different angles, including technology and infrastructure of course, but also architecture, design, and perhaps most overlooked, people and processes. …


Kyle Brown, IBM Fellow, IBM Garage

One of the most depressing parts of my job is doing postmortems on failed cloud adoption projects. This happens fairly regularly; we get called in to a client to help them understand why the steps they’ve taken toward cloud adoption have not lived up to their expectations. There is often recrimination and finger-pointing all around, and the most important thing I can do in a situation like that is remain calm and help the client arrive at a conclusion based on facts and not supposition. …


Kyle Brown, IBM Fellow, CTO Cloud Architecture, IBM Cloud and Cognitive Software

The last year has not been kind to a book that I believe to be one of the classic, and most important works of computer science — the book Design Patterns: Elements of Reusable Object Oriented Design. This is unfortunate, because the preceding year had been the 25th anniversary of the book’s publication and it’s odd that a book that old can generate such vitriol. …

Kyle Gene Brown

IBM Fellow, CTO for Cloud Architecture for the IBM Garage, author and blogger

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store