Welcome!

Microservices Expo Authors: Elizabeth White, Pat Romanski, AppDynamics Blog, Liz McMillan, APM Blog

Related Topics: @CloudExpo, Java IoT, Microservices Expo, Linux Containers, Containers Expo Blog, @BigDataExpo

@CloudExpo: Article

What We Really Mean by Digital Transformation

Agile Architecture is the key to Digital Transformation

Want to know a secret? I loathe the phrase Digital Transformation. Not only is the word Digital silly and misleading, but Transformation ain’t much better. The mere act of naming a business initiative Digital Transformation suggests to people that once the transformation is complete, we’ll be done. Look at us! We’re Digitally Transformed!

Hogwash. A single transformation is better than nothing, but what we really want is the ability to transform our business as needed. Furthermore, we need to be agile with our transformation initiative itself. The last thing we want is to institute, say, a three-year transformation effort, only to find at the end of the three years that the world changed a year into the initiative, rendering it a useless waste of money and effort.

So, who are the right people in the organization to address this sorry state of affairs? Driving the change needed to make our organizations more successful at such ongoing transformation should ideally fall to the Enterprise Architects. Unfortunately, the way Enterprise Architecture (EA) is done today falls well short of this mark.

Traditional EA starts with documenting the initial state of an enterprise. Then Enterprise Architects document the final state as required by the business. Finally, they help the organization plan how to get from one state to the other.

There are only three things wrong with this way to think about EA: The initial state. The final state. And yes, the plan to get from one to the other. It’s no wonder most organizations who were fool enough to sink money into EA believe EA is completely broken. Even EAs think EA is broken, and they do it for a living!

But no matter how fun it is to bemoan this sorry state of affairs, this Cortex must help point the direction to a better way of thinking about – and doing – Enterprise Architecture. The success of any Digital Transformation effort hangs in the balance.

What’s Wrong with Point A to Point B?
It seems so intuitive that the way to solve a problem is first, understand the problem, second, understand the solution, and third, solve the problem. Unfortunately, many EA initiatives don’t get past step one. Documenting the initial state of an enterprise – or even simply documenting the initial state of an enterprise’s IT environment, which is usually where EAs focus their efforts – is an exercise in futility. There are simply way too many bits and pieces, moving parts made of people and technology, for such an activity to ever complete, let alone provide sufficient detail to add clarity to the situation. Remember, the organization is always in flux. Even if you could take a snapshot of everything, it would be out of date a moment later.

What about the final state? That’s the nirvana situation where all your problems are solved, right? OK, raise your hand if there was ever a time in your career where all the problems were solved, all the bugs were fixed, all the projects were complete. Anybody? Sounds rather unrealistic, wouldn’t you say? Even if you narrow your scope to a single aspect of your business or even a single project, there is nothing final about a final state, if you could even refer to such an implausible scenario as a state, which is asking a lot. Remember, everything is connected to everything else, and everything is always changing. The notion of a “final state” is an unrealistic simplification that misleads people into thinking the approach they’re taking will actually solve problems.

Very well, let’s say you’ve still reading, in spite of thinking my comments on initial and final state are a bunch of hogwash. Certainly, you may ask, the EAs can at least concoct some kind of plan for getting from point A to point B? Sorry to disappoint. If what you mean by a “plan” is a description of the steps you must take that you can put together before you take those steps, then no. You’ll never come up with such a plan that ends up having any relationship to reality by even the halfway mark. There are simply too many unknowns, and too many things can change along the way.

Moving Up a Level
The core problem with this traditional approach to architecture is that it is simply too literal. It deals with things as they are and things as you desire them to be, without dealing with the fact that everything is subject to change. But the good news is, we architects have a wonderful tool in our box of tricks for dealing with excess literalness: the tool of abstraction. If we move up a level of abstraction, we’re no longer thinking about initial and final state. Instead, we’re thinking about moving from being less agile to being more agile.

Literal-minded thinkers (and I know you’re out there) will be protesting at this point that “being less agile” is our initial state and “being more agile” is our final state, so we’re just playing word games. And if you squint and hold your nose, there is a minuscule portion of truth in that overly literal perspective – but you’re missing the point here. “Being less agile” describes any number of possible initial states we may find ourselves in, and “being more agile” means being able to deal with change better, no matter which state we started at or where we happened to end up.

Put another way: moving from A to B describes a change (or actually, a set of changes) in the organization. Moving from less agile to more agile describes a change in how the organization deals with change, from being less able to deal with change to being more able to deal with change. In other words, we’re now thinking at the Meta level. We’re not doing architecture any more, oh no. We’re doing meta-architecture: we’re architecting our architecture.

Introducing the Bloomberg Agile Architecture™ Maturity Metamodel
Time to put some meat on these bones. As I’ve explained before, the Bloomberg Agile Architecture (BAA) Technique is a particular approach to implementing EA that is business agility driven. It’s not a framework you need to subtract from but a technique that complements other architectural efforts. Today I’m rolling out a core BAA artifact: the BAA Maturity Metamodel.

Try as I might, I couldn’t fit the entire chart into this article, so instead, I’ve linked to a pdf version of the Metamodel. Click here or the image below to download the pdf.

Unfortunately, there isn’t room in this Cortex to fully explain the BAA Maturity Metamodel (for that, take one of our classes to learn all the details, or drop me a line). But there is room here for a few of the highlights.

First, notice the four levels: Chaotic State, First-Gen SOA/Centralized, Next-Gen SOA/Cloud-Centric, and Agile Architecture. These designations refer to the organization’s context for architecture as it matures from less agile to more agile. In other words, it maps how your architecture is evolving – and thus the chart represents an aspect of your meta-architecture.

Second, note the twelve dimensions (rows), sorted neatly into four areas: Organization, Process, Information, and Technology. This organization of dimensions is more a matter of convenience than anything else. Feel free to rearrange the dimensions as you see fit.

In fact, feel free to change anything in the metamodel you see fit, based upon your situation – and always be willing to change it as your architecture evolves. Remember, there are two sides to being agile: the core driver of business agility (increasing in the metamodel from left to right) and the fact that BAA is Agile in approach (in other words, generally follows the principles of the Agile Manifesto). And as ye old Manifesto sayeth, thou shalt respond to change over following a plan. Even if the plan is to be Agile!

Finally, never forget what this diagram is for. It’s for helping architects coordinate change across the organization as driven by business needs. The metamodel – or any other aspect of the architecture – never tells the business what it should do. In the immortal words of a well-known sage: “business needs drive the architecture, and architecture drives the technology. Never let technology drive the architecture or the architecture drive the business.” Couldn’t have said it better myself.

The Intellyx Take
I know that many of you who took the time to download the Maturity Metamodel will have many questions about it – and over time, I’ll get to the answers. But just to whet your appetite a wee bit further, let’s take a moment to discuss the first dimension: Business Transformation.

The starting point for business transformation, of course, must be “no transformation.” As the organization gets a handle on their architecture and moves to first-generation SOA, IT moves into the role of service provider – not simply IT services, but also Web Services that automate the interaction with existing systems of record. Instead of simply integrating those systems, now the IT organization publishes interfaces that can be consumed as needed, transforming the relationship between IT and the business (which was always easier said than done, hence the relegation of first-generation SOA to Level One).

As the architecture matures to next-generation, Cloud-friendly SOA (which in many cases loses the “SOA” name, but is Service-oriented nevertheless), the transformation story centers on the move to the Cloud. Cloud Computing, you see, is far more than a change in technology deployment. It represents a force for transforming the business.

But even Cloud-driven transformation isn’t the end of the story. The move to Agile Architecture is a move to continuous business transformation – where the organization is as agile as it wants to be, and is able to deal with change as a routine part of how it does business. Continuous business transformation, of course, has always been the center of the Agile Architecture story – and is what we really mean when we say we want Digital Transformation.

More Stories By Jason Bloomberg

Jason Bloomberg is the leading expert on architecting agility for the enterprise. As president of Intellyx, Mr. Bloomberg brings his years of thought leadership in the areas of Cloud Computing, Enterprise Architecture, and Service-Oriented Architecture to a global clientele of business executives, architects, software vendors, and Cloud service providers looking to achieve technology-enabled business agility across their organizations and for their customers. His latest book, The Agile Architecture Revolution (John Wiley & Sons, 2013), sets the stage for Mr. Bloomberg’s groundbreaking Agile Architecture vision.

Mr. Bloomberg is perhaps best known for his twelve years at ZapThink, where he created and delivered the Licensed ZapThink Architect (LZA) SOA course and associated credential, certifying over 1,700 professionals worldwide. He is one of the original Managing Partners of ZapThink LLC, the leading SOA advisory and analysis firm, which was acquired by Dovel Technologies in 2011. He now runs the successor to the LZA program, the Bloomberg Agile Architecture Course, around the world.

Mr. Bloomberg is a frequent conference speaker and prolific writer. He has published over 500 articles, spoken at over 300 conferences, Webinars, and other events, and has been quoted in the press over 1,400 times as the leading expert on agile approaches to architecture in the enterprise.

Mr. Bloomberg’s previous book, Service Orient or Be Doomed! How Service Orientation Will Change Your Business (John Wiley & Sons, 2006, coauthored with Ron Schmelzer), is recognized as the leading business book on Service Orientation. He also co-authored the books XML and Web Services Unleashed (SAMS Publishing, 2002), and Web Page Scripting Techniques (Hayden Books, 1996).

Prior to ZapThink, Mr. Bloomberg built a diverse background in eBusiness technology management and industry analysis, including serving as a senior analyst in IDC’s eBusiness Advisory group, as well as holding eBusiness management positions at USWeb/CKS (later marchFIRST) and WaveBend Solutions (now Hitachi Consulting).

@MicroservicesExpo Stories
The Internet of Things will challenge the status quo of how IT and development organizations operate. Or will it? Certainly the fog layer of IoT requires special insights about data ontology, security and transactional integrity. But the developmental challenges are the same: People, Process and Platform and how we integrate our thinking to solve complicated problems. In his session at 19th Cloud Expo, Craig Sproule, CEO of Metavine, will demonstrate how to move beyond today's coding paradigm ...
Digitization is driving a fundamental change in society that is transforming the way businesses work with their customers, their supply chains and their people. Digital transformation leverages DevOps best practices, such as Agile Parallel Development, Continuous Delivery and Agile Operations to capitalize on opportunities and create competitive differentiation in the application economy. However, information security has been notably absent from the DevOps movement. Speed doesn’t have to negat...
With the rise of Docker, Kubernetes, and other container technologies, the growth of microservices has skyrocketed among dev teams looking to innovate on a faster release cycle. This has enabled teams to finally realize their DevOps goals to ship and iterate quickly in a continuous delivery model. Why containers are growing in popularity is no surprise — they’re extremely easy to spin up or down, but come with an unforeseen issue. However, without the right foresight, DevOps and IT teams may lo...
In his general session at 18th Cloud Expo, Lee Atchison, Principal Cloud Architect and Advocate at New Relic, discussed cloud as a ‘better data center’ and how it adds new capacity (faster) and improves application availability (redundancy). The cloud is a ‘Dynamic Tool for Dynamic Apps’ and resource allocation is an integral part of your application architecture, so use only the resources you need and allocate /de-allocate resources on the fly.
Your business relies on your applications and your employees to stay in business. Whether you develop apps or manage business critical apps that help fuel your business, what happens when users experience sluggish performance? You and all technical teams across the organization – application, network, operations, among others, as well as, those outside the organization, like ISPs and third-party providers – are called in to solve the problem.
Information technology is an industry that has always experienced change, and the dramatic change sweeping across the industry today could not be truthfully described as the first time we've seen such widespread change impacting customer investments. However, the rate of the change, and the potential outcomes from today's digital transformation has the distinct potential to separate the industry into two camps: Organizations that see the change coming, embrace it, and successful leverage it; and...
The Jevons Paradox suggests that when technological advances increase efficiency of a resource, it results in an overall increase in consumption. Writing on the increased use of coal as a result of technological improvements, 19th-century economist William Stanley Jevons found that these improvements led to the development of new ways to utilize coal. In his session at 19th Cloud Expo, Mark Thiele, Chief Strategy Officer for Apcera, will compare the Jevons Paradox to modern-day enterprise IT, e...
As applications are promoted from the development environment to the CI or the QA environment and then into the production environment, it is very common for the configuration settings to be changed as the code is promoted. For example, the settings for the database connection pools are typically lower in development environment than the QA/Load Testing environment. The primary reason for the existence of the configuration setting differences is to enhance application performance. However, occas...
SYS-CON Events announced today the Kubernetes and Google Container Engine Workshop, being held November 3, 2016, in conjunction with @DevOpsSummit at 19th Cloud Expo at the Santa Clara Convention Center in Santa Clara, CA. This workshop led by Sebastian Scheele introduces participants to Kubernetes and Google Container Engine (GKE). Through a combination of instructor-led presentations, demonstrations, and hands-on labs, students learn the key concepts and practices for deploying and maintainin...
More and more companies are looking to microservices as an architectural pattern for breaking apart applications into more manageable pieces so that agile teams can deliver new features quicker and more effectively. What this pattern has done more than anything to date is spark organizational transformations, setting the foundation for future application development. In practice, however, there are a number of considerations to make that go beyond simply “build, ship, and run,” which changes ho...
While DevOps promises a better and tighter integration among an organization’s development and operation teams and transforms an application life cycle into a continual deployment, Chef and Azure together provides a speedy, cost-effective and highly scalable vehicle for realizing the business values of this transformation. In his session at @DevOpsSummit at 19th Cloud Expo, Yung Chou, a Technology Evangelist at Microsoft, will present a unique opportunity to witness how Chef and Azure work tog...
When scaling agile / Scrum, we invariable run into the alignment vs autonomy problem. In short: you cannot have autonomous self directing teams if they have no clue in what direction they should go, or even shorter: Alignment breeds autonomy. But how do we create alignment? and what tools can we use to quickly evaluate if what we want to do is part of the mission or better left out? Niel Nickolaisen created the Purpose Alignment model and I use it with innovation labs in large enterprises to de...
SYS-CON Events announced today that Numerex Corp, a leading provider of managed enterprise solutions enabling the Internet of Things (IoT), will exhibit at the 19th International Cloud Expo | @ThingsExpo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Numerex Corp. (NASDAQ:NMRX) is a leading provider of managed enterprise solutions enabling the Internet of Things (IoT). The Company's solutions produce new revenue streams or create operating...
If you’re responsible for an application that depends on the data or functionality of various IoT endpoints – either sensors or devices – your brand reputation depends on the security, reliability, and compliance of its many integrated parts. If your application fails to deliver the expected business results, your customers and partners won't care if that failure stems from the code you developed or from a component that you integrated. What can you do to ensure that the endpoints work as expect...
SYS-CON Events announced today that Tintri Inc., a leading producer of VM-aware storage (VAS) for virtualization and cloud environments, will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Tintri VM-aware storage is the simplest for virtualized applications and cloud. Organizations including GE, Toyota, United Healthcare, NASA and 6 of the Fortune 15 have said “No to LUNs.” With Tintri they mana...
Analysis of 25,000 applications reveals 6.8% of packages/components used included known defects. Organizations standardizing on components between 2 - 3 years of age can decrease defect rates substantially. Open source and third-party packages/components live at the heart of high velocity software development organizations. Today, an average of 106 packages/components comprise 80 - 90% of a modern application, yet few organizations have visibility into what components are used where.
Throughout history, various leaders have risen up and tried to unify the world by conquest. Fortunately, none of their plans have succeeded. The world goes on just fine with each country ruling itself; no single ruler is necessary. That’s how it is with the container platform ecosystem, as well. There’s no need for one all-powerful, all-encompassing container platform. Think about any other technology sector out there – there are always multiple solutions in every space. The same goes for conta...
Let's recap what we learned from the previous chapters in the series: episode 1 and episode 2. We learned that a good rollback mechanism cannot be designed without having an intimate knowledge of the application architecture, the nature of your components and their dependencies. Now that we know what we have to restore and in which order, the question is how?
Enterprise IT has been in the era of Hybrid Cloud for some time now. But it seems most conversations about Hybrid are focused on integrating AWS, Microsoft Azure, or Google ECM into existing on-premises systems. Where is all the Private Cloud? What do technology providers need to do to make their offerings more compelling? How should enterprise IT executives and buyers define their focus, needs, and roadmap, and communicate that clearly to the providers?
SYS-CON Events announced today that Commvault, a global leader in enterprise data protection and information management, has been named “Bronze Sponsor” of SYS-CON's 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Commvault is a leading provider of data protection and information management solutions, helping companies worldwide activate their data to drive more value and business insight and to transform moder...