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 elastic scaling support. Whether that be Horizontal Pod Autoscalers in Kubernetes (which will automatically scale the number of Pods based on observed CPU utilization) or vendor features such as AWS Autoscaling, which will automatically scale EC2 instances, Dynamo DB tables and many other resource types, elastic scaling is often viewed as being the single most desirable feature of the cloud. …

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.

Image for post
Image for post
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 product runtimes using the same operational skills. Furthermore it should promote automation of operations, and provide a framework for observability. …

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.

Image for post
Image for post
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 a modern container-based cloud infrastructure. For some, that’s a way to start getting their feet wet with cloud, but it should only be a start. If you do so, you will experience hardly any of the advantages of cloud native. In this section we will consider how to design an application such that it has the opportunity to fully leverage the underlying cloud infrastructure. It should quickly become apparent how well-decoupled components, rolled out using immutable deployments, is just as essential as embracing the agile methods and processes discussed already. …

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 processes you follow. In this and the next two articles we are going to walk through what we have seen to be the most important ingredients of successful cloud native initiatives, taking a different perspective in each. …

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 Brown, IBM Fellow, CTO Cloud Architecture, IBM Cloud and Cognitive Software

E. G. Nadhan, Chief Architect and Strategist, North America, Red Hat

Image for post
Image for post
Reopening after a long closure is an opportunity (Image: Wikimedia commons)

Thousands of businesses in the US and around the world are starting the process of bringing back their furloughed IT staff and getting back to business. However, the process of reopening creates a unique opportunity for reinvention that many large enterprises rarely get. Especially considering that the current economic models indicate a slow, prolonged recovery (it may be late 2021 or even 2022 before the world returns to pre-COVID levels of economic activity) businesses should take this opportunity to reassess how IT will operate once they reopen. …

Kyle Brown

In a prior article, we touched upon a few of the different aspects that can lead you to refactor your code to a Microservices-based approach. One of the last aspects we touched upon was the question of what to do with your data — in large-scale enterprise applications that is often the thorniest issue — and one that is worth a more in-depth treatment. What we have seen is that sometimes it’s hard to determine when you are looking at a coding issue, or a data modeling issue that is masquerading as a coding issue. We’ll look at several of these cases, and talk about data modeling choices you can make to simplify and improve your refactored code. …


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