Welcome!

SDN Journal Authors: Destiny Bertucci, Liz McMillan, Pat Romanski, Elizabeth White, Amitabh Sinha

Related Topics: @CloudExpo, Java IoT, Microservices Expo, Containers Expo Blog, @DXWorldExpo, SDN Journal

@CloudExpo: Article

The Other Agile Architecture

Building software in an Agile way doesn’t guarantee the software will be agile

Ever since my new book, The Agile Architecture Revolution hit the streets, I've been following the keywords "Agile Architecture" on Twitter. Sure enough, there are plenty of conversations on Agile Architecture - but to my disappointment, most of them aren't about my book, or even what I mean by "Agile Architecture" in my book.

The focus of my book is on architectural approaches to delivering business agility for the enterprise - in essence, taking Enterprise Architecture (EA) to the next level, where constant business transformation is the goal, rather than a fixed end-state. The more common definition of Agile Architecture, however, is applying Agile (Agile-with-a-capital-A) principles to software architecture - a very different perspective.

I discuss the Agile Manifesto in the book, of course - I could hardly put the word Agile in the title without doing so - but these two definitions of Agile Architecture are quite different. However, it's not a question of which is right and which is wrong. Rather, the central question of this ZapFlash is how the two senses of Agile Architecture are related to each other.

Agile Software Architecture
Agilemodeling.com
is a great resource for learning the basics of Agile Software Architecture. There is far more detail there than we can cover here, but in summary, here's how ZapThink interprets the principles of Agile Architecture, according to this site:

  • Everyone on the software team can pitch in and improve the architecture, just as everyone is responsible for all the code in a traditional Agile project. However, not everyone on the development team is equally competent at software architecture, so there should be an owner of the architecture in case of disagreements.
  • Avoid ivory tower architectures, where the architects handing down architecture artifacts from on high rather than being directly involved in development, through constant feedback among architects, developers, and the rest of the team.
  • Don't overdo the architecture. Simple software requires simple architectures which don't require complicated architectural efforts. Even a doghouse needs a plan, but it's vastly simpler than the plan for a large building.
  • Architecture helps Agile software scale, which also means that architecture helps Agile software be more Cloud friendly.
  • Base your architecture on the requirements for your software. Solicit active stakeholder participation, as with any Agile project. Think about future possible requirements, but don't overbuild in anticipation of as-yet undefined needs. In other words, defer commitment on design decisions.

All of the above principles follow basic common sense, and any development team that follows them is bound to have better architected software. But thinking about Agile Architecture as an approach to architecting software leads to a central paradox: building software in an Agile way doesn't guarantee the software will be agile, as we discussed in a ZapFlash in May 2012. The fundamental problem: requirements continue to evolve, but even the most Agile of software development approaches builds to the current requirements. In fact, the final bullet above even exhorts the development team to avoid overbuilding.

We've written about the overbuilding trap before in a pair of blog posts. If we simply demand the developers build code to meet future requirements, without specifying what those requirements might be, we've just sent them down a rabbit hole. Fundamentally, if you look at the problem of building software that provides business agility as nothing more than how to build software to meet future requirements, you'll never find your way out of this hole.

How, then, do we get out of this pickle? How to we build software that responds to changing requirements, without overbuilding our software? Agilemodeling.com discusses the notion of change case modeling, where change cases describe potential new or changed requirements for a software system. In fact, ZapThink has been discussing change case modeling since we introduced the Agility Model back in 2008, although the change cases we discussed go beyond a particular software system to include processes, policies, and other elements of the Enterprise Architecture.

Solutions vs. Tools
The enterprise context for software development focuses on solutions: the stakeholder has a problem, so you build a solution to that problem. Hence when the problem changes, you need a new or different solution. However, not all software development focuses on solutions. For example, many software vendors build and sell software tools.

The most important feature of a tool is that you can use it for different things, even when it is fit for a particular purpose. Even if you limit your hammer to only hammering nails, you can still hammer many different kinds of nails into many different materials, and the hammer manufacturer doesn't have to know any of the specifics. So too with software tools. A software vendor who publishes, say, an Integrated Development Environment (IDE) need have no knowledge about the type of software that users of that IDE might use it for. The tool may be fit for certain types of development, but it's entirely agnostic as to the code its users call upon the tool to build.

The overbuilding problem tends to rear its ugly head when development teams should be building a tool, but focus on building a solution instead. Now it seems that every nail requires a different kind of hammer, where you should really be focusing on building a versatile hammer in the first place. This mistake is very common on SOA initiatives when the SOA team is trying to sort out the agnostic context for its Services: which Services are built for particular purposes (i.e., solutions) vs. Services built for reuse (in other words, tools). After all, the whole idea behind a reusable Service is that it is agnostic with respect to how people might use it in the future, a characteristic such Services share with hammers or any other kind of tool.

Declarative Programming: Configuration over Code
The primary technique software tool vendors use to support different customer requirements with the same tools is to allow customers to configure the tools to meet their needs. In other words, separate the configuration from the code, where the configuration consists of metadata that describe how the software should behave, and the code reads the config files and behaves the way the config files say to behave.

Creating such a configuration file is a classic example of declarative programming. Describe how the software is supposed to work without having to delineate the control flow that instructs the underlying processor what to execute. Declarative programming has been around for years, of course; SQL and HTML are two familiar examples of languages that support this approach. When you write SQL, you expect your database management system to understand it and behave accordingly. Similarly, writing HTML instructs your browser how to behave, while coding the software for the browser itself takes place independent of the Web pages it will be expected to render.

Unfortunately, while declarative programming separates configuration from code, not all configuration leads to agility. After all, dinosaur enterprise application packages like ERP have been configurable for years, but simply separating the behavior of the software from the underlying code is no guarantee of agility, just as defining the behavior of a Web Service by specifying its Service contract in WSDL and XSD files doesn't guarantee the Service will be reusable. Something is still missing from this picture.

To see what's missing, let's take an example of a software-based tool that does provide business agility: Amazon's IaaS tools (or any other Cloud provider's tools that rise to Amazon's standard). The coding wizards back at Amazon HQ have built interfaces that allow anyone with a credit card to provision and configure all manner of compute resources, without ever having to monkey around with the underlying code that makes the Cloud magic work. Supporting declarative configuration is merely the price of admission here. What the Cloud has done is connect people and process to the technology, empowering end users to handle the configuration themselves.

In the enterprise context, then, the missing piece of Agile Software Architecture is Agile Enterprise Architecture, where EA brings together the organization, the processes, the technology, and the information in a consistent, business-driven whole. Configurability alone doesn't provide this consistency. Instead, true Agile Architecture - that is, architecture that supports the business agility requirement - must tie these concerns together using a balanced combination of Enterprise Architecture, governance, and Agile Software Architecture.

ZapThink Take
In the Cloud example above, Cloud users may interact with the Cloud via a browser-based user interface, or they may choose to use the Cloud's APIs. APIs are unquestionably an important part of the Cloud story, but the mere fact we're calling them APIs - application programming interfaces - belies their significance. Turning the Cloud into a massive piece of software we have to program will defeat the agility benefit the Cloud provides, after all.

Fortunately, today's APIs are misnamed. We moved from tightly coupled procedure call interfaces (which were truly APIs) to contracted interfaces we called Services to the interfaces we have now, which we once again call APIs. But just as a Cloud API should provide a declarative, scriptable interface to the same capabilities the browser-based user interface exhibits, today's modern APIs should be user-empowering interfaces.

The movement toward Hypermedia-Oriented Architecture, what some people call REST, is part of this story. Remember, the programmable Web is meant to make software more Web-like, rather than make the Web more programmable. We have all the pieces of Agile Architecture: Agile Software Architecture; declarative, configuration-based programming; hypermedia-based APIs; and Enterprise Architecture to tie everything together. All we need to do know is get the architecture right.

Photo credit: Nadya Peek

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).

@CloudExpo Stories
Digital transformation is about embracing digital technologies into a company's culture to better connect with its customers, automate processes, create better tools, enter new markets, etc. Such a transformation requires continuous orchestration across teams and an environment based on open collaboration and daily experiments. In his session at 21st Cloud Expo, Alex Casalboni, Technical (Cloud) Evangelist at Cloud Academy, explored and discussed the most urgent unsolved challenges to achieve f...
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
The 22nd International Cloud Expo | 1st DXWorld Expo has announced that its Call for Papers is open. Cloud Expo | DXWorld Expo, to be held June 5-7, 2018, at the Javits Center in New York, NY, brings together Cloud Computing, Digital Transformation, Big Data, Internet of Things, DevOps, Machine Learning and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding busin...
In a recent survey, Sumo Logic surveyed 1,500 customers who employ cloud services such as Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). According to the survey, a quarter of the respondents have already deployed Docker containers and nearly as many (23 percent) are employing the AWS Lambda serverless computing framework. It’s clear: serverless is here to stay. The adoption does come with some needed changes, within both application development and operations. Tha...
SYS-CON Events announced today that Synametrics Technologies will exhibit at SYS-CON's 22nd International Cloud Expo®, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Synametrics Technologies is a privately held company based in Plainsboro, New Jersey that has been providing solutions for the developer community since 1997. Based on the success of its initial product offerings such as WinSQL, Xeams, SynaMan and Syncrify, Synametrics continues to create and hone in...
Smart cities have the potential to change our lives at so many levels for citizens: less pollution, reduced parking obstacles, better health, education and more energy savings. Real-time data streaming and the Internet of Things (IoT) possess the power to turn this vision into a reality. However, most organizations today are building their data infrastructure to focus solely on addressing immediate business needs vs. a platform capable of quickly adapting emerging technologies to address future ...
In his general session at 21st Cloud Expo, Greg Dumas, Calligo’s Vice President and G.M. of US operations, discussed the new Global Data Protection Regulation and how Calligo can help business stay compliant in digitally globalized world. Greg Dumas is Calligo's Vice President and G.M. of US operations. Calligo is an established service provider that provides an innovative platform for trusted cloud solutions. Calligo’s customers are typically most concerned about GDPR compliance, application p...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
In his session at 21st Cloud Expo, Michael Burley, a Senior Business Development Executive in IT Services at NetApp, described how NetApp designed a three-year program of work to migrate 25PB of a major telco's enterprise data to a new STaaS platform, and then secured a long-term contract to manage and operate the platform. This significant program blended the best of NetApp’s solutions and services capabilities to enable this telco’s successful adoption of private cloud storage and launching ...
The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Nordstrom is transforming the way that they do business and the cloud is the key to enabling speed and hyper personalized customer experiences. In his session at 21st Cloud Expo, Ken Schow, VP of Engineering at Nordstrom, discussed some of the key learnings and common pitfalls of large enterprises moving to the cloud. This includes strategies around choosing a cloud provider(s), architecture, and lessons learned. In addition, he covered some of the best practices for structured team migration an...
With tough new regulations coming to Europe on data privacy in May 2018, Calligo will explain why in reality the effect is global and transforms how you consider critical data. EU GDPR fundamentally rewrites the rules for cloud, Big Data and IoT. In his session at 21st Cloud Expo, Adam Ryan, Vice President and General Manager EMEA at Calligo, examined the regulations and provided insight on how it affects technology, challenges the established rules and will usher in new levels of diligence arou...
Most technology leaders, contemporary and from the hardware era, are reshaping their businesses to do software. They hope to capture value from emerging technologies such as IoT, SDN, and AI. Ultimately, irrespective of the vertical, it is about deriving value from independent software applications participating in an ecosystem as one comprehensive solution. In his session at @ThingsExpo, Kausik Sridhar, founder and CTO of Pulzze Systems, discussed how given the magnitude of today's application ...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
As you move to the cloud, your network should be efficient, secure, and easy to manage. An enterprise adopting a hybrid or public cloud needs systems and tools that provide: Agility: ability to deliver applications and services faster, even in complex hybrid environments Easier manageability: enable reliable connectivity with complete oversight as the data center network evolves Greater efficiency: eliminate wasted effort while reducing errors and optimize asset utilization Security: imple...
Mobile device usage has increased exponentially during the past several years, as consumers rely on handhelds for everything from news and weather to banking and purchases. What can we expect in the next few years? The way in which we interact with our devices will fundamentally change, as businesses leverage Artificial Intelligence. We already see this taking shape as businesses leverage AI for cost savings and customer responsiveness. This trend will continue, as AI is used for more sophistica...
In his Opening Keynote at 21st Cloud Expo, John Considine, General Manager of IBM Cloud Infrastructure, led attendees through the exciting evolution of the cloud. He looked at this major disruption from the perspective of technology, business models, and what this means for enterprises of all sizes. John Considine is General Manager of Cloud Infrastructure Services at IBM. In that role he is responsible for leading IBM’s public cloud infrastructure including strategy, development, and offering m...
In his session at 21st Cloud Expo, Raju Shreewastava, founder of Big Data Trunk, provided a fun and simple way to introduce Machine Leaning to anyone and everyone. He solved a machine learning problem and demonstrated an easy way to be able to do machine learning without even coding. Raju Shreewastava is the founder of Big Data Trunk (www.BigDataTrunk.com), a Big Data Training and consulting firm with offices in the United States. He previously led the data warehouse/business intelligence and B...