|By Jason Bloomberg||
|June 2, 2014 06:13 AM EDT||
My five months with EnterpriseWeb have run their course, and I’m returning to the world of advisory, analysis, and architecture training with my new company, Intellyx, and this, the inaugural issue of our Cortex newsletter. After a dozen years with ZapThink, doing my best to help organizations around the globe get architecture right, you might wonder why I took a detour as Chief Evangelist for a vendor. The answer: EnterpriseWeb has brought technology to market that can upend the entire Agile Architecture discussion. They have set the bar for what it means to build a platform that can enable organizations to achieve the elusive business agility benefits that SOA promised but never delivered. And if a five-person company out of upstate New York can do that, then anybody can.
As of today I return full time to being a chief evangelist for the style of Enterprise Architecture I refer to as Agile Architecture in my book, The Agile Architecture Revolution. In that book I talk about REST-Based SOA, Cloud Computing, mobile technologies, and a host of other modern enterprise technology trends that are shaking up IT departments as they try to get a handle on the business value such technologies promise. And yet, I’ll be the first to admit that the book didn’t go far enough. You could take every word I wrote to heart and still not know how to architect agility in your organization. There were pieces missing from the story – and all these missing elements centered on the fundamental challenge of distributed computing.
The central challenge of distributed computing, of course, is how to get your various distributed bits to communicate with each other properly. Since those distributed components are typically heterogeneous, we must somehow come up with a common means of establishing interaction among components everybody can agree on. Yet, once we do that, we’ve necessarily compromised on flexibility, because changing how our components interact is a difficult, complex endeavor. Agile Architecture must solve this problem.
This problem pervades the entire history of APIs, from remote procedure calls to Web Services to RESTful APIs and everything in between. We must somehow contract interfaces in order to abstract the underlying functionality, thus providing loose coupling and with it, some measure of flexibility within the underlying code. Yet the very act of introducing such contracts (including REST’s uniform interface) is a compromise, since the interface itself now lacks flexibility. Basically, we look at the world of distributed computing and convince ourselves that the only way to get this stuff to work at all is to give up agility. The end result? Instead of being an enabler of business agility, enterprise IT is now cast in the role of limiter of business agility.
The central technical challenge for Agile Architecture, therefore, is how to achieve functionality and performance without having to trade off flexibility. This central compromise of distributed computing is the nut that EnterpriseWeb has been able to crack by adding an additional layer of abstraction over the entire distributed environment, coupled with an agent-oriented runtime engine that resolves abstracted references dynamically in real time. The bottom line: at least one vendor in the marketplace has shown that it is possible to deliver on the promise of Agile Architecture. And if one can, so can others.
The Four Central Patterns of Agile Architecture
Now it’s time for me to take off my EnterpriseWeb hat and put it in a drawer. In its place goes the Intellyx hat, blue brain and all. After all, the point of this article isn’t to talk about what a single vendor has accomplished. Rather, my goal is to lay out the essential patterns of Agile Architecture that heretofore have been difficult or impossible to implement in practice.
The context for these central patterns of Agile Architecture is the concept of architecting at the “meta” level I discuss in my book – the higher level of abstraction that EnterpriseWeb has been able to implement. At this meta level, there are four central patterns of Agile Architecture that are essential to resolving the fundamental compromise of distributed computing:
- Dynamic Coupling. Tightly coupled interfaces require detailed knowledge of both sides of a distributed computing interaction, and any change on one side might break the other. Contracted interfaces introduce loose coupling, implementing an abstraction that separates interface from implementation, thus allowing changes to the implementation, but at the expense of a static interface. With dynamic coupling, interface differences are resolved dynamically at run time. The underlying integration engine must be able to find all relevant metadata and resolve any interaction issues in real time in order to allow the metadata to change from one request to the next.
- Dynamic Schemas. Neither the WSDL files that specify Web Services, nor the URIs, HTTP verbs, and Internet Media Types that specify RESTful APIs adequately contract the message semantics for any interaction. As a result, metadata describing such semantics are scattered about in XML schemas or Custom Media Types or other arbitrary places, leading to the reintroduction of tight coupling and inflexibility. Dynamic schemas abstract all such semantic metadata in a consistent way, relying once again upon the integration engine to resolve these dynamic schemas for each interaction at run time.
- Extreme Late Binding. Remember the original promise of SOA registries and the ungainly UDDI standard? The idea was that a Service consumer could automatically look up a Web Service at run time, and based upon the WSDL file it found as a result, bind to the newly discovered service in real time, potentially choosing a different Web Service for each interaction. Unfortunately, Web Services rarely if ever worked this way. Registries ended up doing little more than resolving endpoint references at run time, similar to the way DNS resolves domain names – in other words, they provided late binding. Such late binding adds some flexibility to an interaction, but typically at the expense of performance. Today, however, dynamic coupling and dynamic schemas enable any client to discover at run time all the metadata it requires to interact with any endpoint, without sacrificing performance – what I call extreme late binding.
- Dynamic Constraint Satisfaction. The publication of Services at design time for later discovery shifted SOA’s focus from integration to governance. How are you going to manage all the Services in your directory – let alone actually reuse any of them – unless you are able to create and enforce policies across your organization for how to do so properly? Yes, SOA management tools (helpfully renamed API management tools for the 2010s) provide some measure of API governance, but typically constrained to the technical context of software interactions. However, ask a business stakeholder what governance means to them, and you’ll get an entirely different context for the word. While some policies are technical in nature and apply narrowly to specific APIs or applications, others are more business-centric and apply broadly across departments or even entire organizations. To enforce the full breadth of such policies properly, your run time environment must essentially solve for the combination of all applicable policies dynamically at run time across the entire application environment – a classic dynamic constraint satisfaction problem.
If you believe any of these patterns is nothing more than an old pattern warmed over with a new name, you may be missing something important. True, each of these patterns builds upon patterns that came before, but they all advance the discussion of Agile Architecture to a new level. On the other hand, if you think any of the above patterns are too difficult to implement – if it sounds like you need some kind of magic wand to make this vision work – then I’m here to tell you, I’ve seen a platform that can implement all four patterns, and furthermore, can do so without sacrificing performance. Thus we know they are possible. The question now is, why isn’t everyone doing them?
You may, however, believe that you’re actually implementing some or all of these patterns, either as an architect or as a vendor whose product supports such patterns for your customers. If so, I want to hear from you. Intellyx wants to tell your story.
The Intellyx Take
The Agile Architecture bar is set. Vendors should know what their products must do. Architects have some insight into the patterns they must follow. And business stakeholders can finally rest assured that at least it’s possible to achieve technology-enabled business agility. True, it’s difficult. Many of the pieces are only just now falling into place. Levels of maturity are low across the board. But we’re on our way.
I’m looking forward to helping organizations like yours by leading the Agile Architecture story. I hope to see you in one of my all-new Bloomberg Agile Architecture courses, the sequel to my popular Licensed ZapThink Architect course, coming to Seattle, Dubai, Sydney, Washington DC, and London in the next few months. Or perhaps I can present a keynote at your corporate event or conference, or if you’re a vendor or service provider, consider an Intellyx unlimited advisory subscription or participating in our upcoming Agile Architecture Vendor Landscape Report. You can also join our LinkedIn group or subscribe to the Cortex newsletter. And don’t forget to see me speak on Breaking Down Enterprise Silos in the Cloud next week at Cloud Expo in New York City, where I’ll be giving away a copy of my book. I’m looking forward to working with you again!
DevOps tends to focus on the relationship between Dev and Ops, putting an emphasis on the ops and application infrastructure. But that’s changing with microservices architectures. In her session at DevOps Summit, Lori MacVittie, Evangelist for F5 Networks, will focus on how microservices are changing the underlying architectures needed to scale, secure and deliver applications based on highly distributed (micro) services and why that means an expansion into “the network” for DevOps.
Jul. 1, 2015 07:15 PM EDT Reads: 2,532
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of...
Jul. 1, 2015 05:00 PM EDT Reads: 2,233
Conferences agendas. Event navigation. Specific tasks, like buying a house or getting a car loan. If you've installed an app for any of these things you've installed what's known as a "disposable mobile app" or DMA. Apps designed for a single use-case and with the expectation they'll be "thrown away" like brochures. Deleted until needed again. These apps are necessarily small, agile and highly volatile. Sometimes existing only for a short time - say to support an event like an election, the Wor...
Jul. 1, 2015 05:00 PM EDT Reads: 1,667
The cloud has transformed how we think about software quality. Instead of preventing failures, we must focus on automatic recovery from failure. In other words, resilience trumps traditional quality measures. Continuous delivery models further squeeze traditional notions of quality. Remember the venerable project management Iron Triangle? Among time, scope, and cost, you can only fix two or quality will suffer. Only in today's DevOps world, continuous testing, integration, and deployment upend...
Jul. 1, 2015 03:00 PM EDT Reads: 1,962
Discussions about cloud computing are evolving into discussions about enterprise IT in general. As enterprises increasingly migrate toward their own unique clouds, new issues such as the use of containers and microservices emerge to keep things interesting. In this Power Panel at 16th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the state of cloud computing today, and what enterprise IT professionals need to know about how the latest topics and trends affect t...
Jul. 1, 2015 02:30 PM EDT Reads: 1,209
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Arch...
Jul. 1, 2015 02:21 PM EDT Reads: 687
Summer is finally here and it’s time for a DevOps summer vacation. From San Francisco to New York City, our top summer conferences list is going to continuously deliver you to the summer destinations of your dreams. These DevOps parties are hitting all the hottest summer trends with Microservices, Agile, Continuous Delivery, DevSecOps, and even Continuous Testing. Move over Kanye. These are the top 5 Summer DevOps Conferences of 2015.
Jul. 1, 2015 01:00 PM EDT Reads: 1,021
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
Jul. 1, 2015 12:00 PM EDT Reads: 1,715
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
Jul. 1, 2015 11:45 AM EDT Reads: 1,050
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at DevOps Summit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
Jul. 1, 2015 10:30 AM EDT Reads: 867
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
Jul. 1, 2015 10:00 AM EDT Reads: 1,927
Data center models are changing. A variety of technical trends and business demands are forcing that change, most of them centered on the explosive growth of applications. That means, in turn, that the requirements for application delivery are changing. Certainly application delivery needs to be agile, not waterfall. It needs to deliver services in hours, not weeks or months. It needs to be more cost efficient. And more than anything else, it needs to be really, dc infra axisreally, super focus...
Jul. 1, 2015 10:00 AM EDT Reads: 1,992
The most often asked question post-DevOps introduction is: “How do I get started?” There’s plenty of information on why DevOps is valid and important, but many managers still struggle with simple basics for how to initiate a DevOps program in their business. They struggle with issues related to current organizational inertia, the lack of experience on Continuous Integration/Delivery, understanding where DevOps will affect revenue and budget, etc. In their session at DevOps Summit, JP Morgenthal...
Jul. 1, 2015 09:32 AM EDT Reads: 677
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction. ...
Jul. 1, 2015 09:00 AM EDT Reads: 897
Many people recognize DevOps as an enormous benefit – faster application deployment, automated toolchains, support of more granular updates, better cooperation across groups. However, less appreciated is the journey enterprise IT groups need to make to achieve this outcome. The plain fact is that established IT processes reflect a very different set of goals: stability, infrequent change, hands-on administration, and alignment with ITIL. So how does an enterprise IT organization implement change...
Jun. 29, 2015 12:45 PM EDT Reads: 2,822
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations migh...
Jun. 28, 2015 05:00 PM EDT Reads: 2,052
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Jun. 28, 2015 01:00 PM EDT Reads: 1,922
Mashape is bringing real-time analytics to microservices with the release of Mashape Analytics. First built internally to analyze the performance of more than 13,000 APIs served by the mashape.com marketplace, this new tool provides developers with robust visibility into their APIs and how they function within microservices. A purpose-built, open analytics platform designed specifically for APIs and microservices architectures, Mashape Analytics also lets developers and DevOps teams understand w...
Jun. 27, 2015 11:00 AM EDT Reads: 1,951
Buzzword alert: Microservices and IoT at a DevOps conference? What could possibly go wrong? In this Power Panel at DevOps Summit, moderated by Jason Bloomberg, the leading expert on architecting agility for the enterprise and president of Intellyx, panelists peeled away the buzz and discuss the important architectural principles behind implementing IoT solutions for the enterprise. As remote IoT devices and sensors become increasingly intelligent, they become part of our distributed cloud envir...
Jun. 26, 2015 12:00 PM EDT Reads: 2,264
Sumo Logic has announced comprehensive analytics capabilities for organizations embracing DevOps practices, microservices architectures and containers to build applications. As application architectures evolve toward microservices, containers continue to gain traction for providing the ideal environment to build, deploy and operate these applications across distributed systems. The volume and complexity of data generated by these environments make monitoring and troubleshooting an enormous chall...
Jun. 26, 2015 12:00 PM EDT Reads: 1,565