Welcome!

Microservices Expo Authors: Jason Bloomberg, AppDynamics Blog, Robert Reeves, Automic Blog, PagerDuty Blog

Related Topics: Microservices Expo

Microservices Expo: Article

What's the Only Thing Worse...?

One thing that often gets missed in the acronym SOA is Architecture

If you work in the IT industry long enough, you're bound to hear one particular joke (well, you'll hear a number, I want to focus on this one) - "What's the only thing worse than no architect on a project?" The answer of course is "Two or more". And of course that's true, since when you put four architects in a room, you get five opinions (at least one is schizophrenic) on anything.

Nevertheless, as the joke does make clear, architecture is important. Without it, projects flounder, or worse yet succeed in a dizzying display of spaghetti code and cowboy heroics. When it does, the mess it creates comes back to roost in the future. I've visited shops where they can't make changes to their main business processes, because the COBOL code that runs it no longer even exists in source form - so they have to make changes at the compiled code level. In a very real sense, that's an architecture failure - they haven't kept up with the times, assured a realistic software portfolio management program, and maintained good software development life-cycle practices. This is not uncommon.

One thing that often gets missed in the acronym SOA is Architecture. It's fairly easy to service-enable code in this day and age - most modern solutions and platforms give you basic Web services capabilities out of the box. I even know multiple ways to reach the COBOL code (although I shudder at the thought of people writing Web services in COBOL, but even that is happening) and make it play nice in a services environment.

The point though is that service enablement is not service-oriented architecture. Architecture discusses various dimensions of software, such as how to build it, how to re-use it, how fast it needs to be, how much downtime it can have, and a number of other topics. Some folks divide architecture into business, application, and technical (or infrastructure). Others look at different levels - conceptual, logical, and physical. People with specialties (such as security) see the world as a combination of both sets, all slanted toward what is important to them. Enabling services is a good thing for many environments, but for each Service, the management, the SLAs and QoSs, the security and the transactionality of the Service must be considered. And not in a vacuum. That's where Architecture participates in the conversation. A good architecture forms a basis for the development of Services in a structured organized fashion with clean demarcations of responsibility and attention to the various performance characteristics that make a Service really work.

Realistically, that is the broadest definition of Architecture - practices that enable software to work. And practices definitely include process and not just the technical aspects of software development. In any large shop, the process of accomplishing software development is a critical part of architecture. If the enterprise concepts developed by an architecture group aren't driven into the development organization and monitored, the benefits of architecture can't be realized. That's process, not technology, but it's certainly still in the domain or architecture.

Service-oriented architecture emphasizes application delivery via discrete services over monolithic applications. Every type of architecture has its own challenges, but SOA in particular places a great deal of emphasis on layers of services and the ability to apply services discretely. Responsibilities are encapsulated outside of the services - there's usually no need for the service to understand security or service-level agreements as someone else manages that above or around them. Because each service is discrete, and to a certain extent can ignore the impact of other services, the Architecture becomes even more important, as it is the glue that holds the whole thing together and makes it function.

While two or more architects may be the worse thing in the world, remember, no architects (and by extension, no Architecture) is the next worse thing.

More Stories By Sean Rhody

Sean Rhody is the founding-editor (1999) and editor-in-chief of SOA World Magazine. He is a respected industry expert on SOA and Web Services and a consultant with a leading consulting services company. Most recently, Sean served as the tech chair of SOA World Conference & Expo 2007 East.

Comments (1) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
SYS-CON India News Desk 05/09/06 01:21:57 PM EDT

If you work in the IT industry long enough, you're bound to hear one particular joke (well, you'll hear a number, I want to focus on this one) - 'What's the only thing worse than no architect on a project?' The answer of course is 'Two or more'. And of course that's true, since when you put four architects in a room, you get five opinions (at least one is schizophrenic) on anything.

@MicroservicesExpo Stories
The notion of customer journeys, of course, are central to the digital marketer’s playbook. Clearly, enterprises should focus their digital efforts on such journeys, as they represent customer interactions over time. But making customer journeys the centerpiece of the enterprise architecture, however, leaves more questions than answers. The challenge arises when EAs consider the context of the customer journey in the overall architecture as well as the architectural elements that make up each...
In a crowded world of popular computer languages, platforms and ecosystems, Node.js is one of the hottest. According to w3techs.com, Node.js usage has gone up 241 percent in the last year alone. Retailers have taken notice and are implementing it on many levels. I am going to share the basics of Node.js, and discuss why retailers are using it to reduce page load times and improve server efficiency. I’ll talk about similar developments such as Docker and microservices, and look at several compani...
From the conception of Docker containers to the unfolding microservices revolution we see today, here is a brief history of what I like to call 'containerology'. In 2013, we were solidly in the monolithic application era. I had noticed that a growing amount of effort was going into deploying and configuring applications. As applications had grown in complexity and interdependency over the years, the effort to install and configure them was becoming significant. But the road did not end with a ...
In 2006, Martin Fowler posted his now famous essay on Continuous Integration. Looking back, what seemed revolutionary, radical or just plain crazy is now common, pedestrian and "just what you do." I love it. Back then, building and releasing software was a real pain. Integration was something you did at the end, after code complete, and we didn't know how long it would take. Some people may recall how we, as an industry, spent a massive amount of time integrating code from one team with another...
Admittedly, two years ago I was a bulk contributor to the DevOps noise with conversations rooted in the movement around culture, principles, and goals. And while all of these elements of DevOps environments are important, I’ve found that the biggest challenge now is a lack of understanding as to why DevOps is beneficial. It’s getting the wheels going, or just taking the next step. The best way to start on the road to change is to take a look at the companies that have already made great headway ...
Much of the value of DevOps comes from a (renewed) focus on measurement, sharing, and continuous feedback loops. In increasingly complex DevOps workflows and environments, and especially in larger, regulated, or more crystallized organizations, these core concepts become even more critical. In his session at @DevOpsSummit at 18th Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, will show how, by focusing on 'metrics that matter,' you can provide objective, transparent, and meaningfu...
Many private cloud projects were built to deliver self-service access to development and test resources. While those clouds delivered faster access to resources, they lacked visibility, control and security needed for production deployments. In their session at 18th Cloud Expo, Steve Anderson, Product Manager at BMC Software, and Rick Lefort, Principal Technical Marketing Consultant at BMC Software, will discuss how a cloud designed for production operations not only helps accelerate developer...
In the world of DevOps there are ‘known good practices’ – aka ‘patterns’ – and ‘known bad practices’ – aka ‘anti-patterns.' Many of these patterns and anti-patterns have been developed from real world experience, especially by the early adopters of DevOps theory; but many are more feasible in theory than in practice, especially for more recent entrants to the DevOps scene. In this power panel at @DevOpsSummit at 18th Cloud Expo, moderated by DevOps Conference Chair Andi Mann, panelists will dis...
Struggling to keep up with increasing application demand? Learn how Platform as a Service (PaaS) can streamline application development processes and make resource management easy.
As the software delivery industry continues to evolve and mature, the challenge of managing the growing list of the tools and processes becomes more daunting every day. Today, Application Lifecycle Management (ALM) platforms are proving most valuable by providing the governance, management and coordination for every stage of development, deployment and release. Recently, I spoke with Madison Moore at SD Times about the changing market and where ALM is headed.
If there is anything we have learned by now, is that every business paves their own unique path for releasing software- every pipeline, implementation and practices are a bit different, and DevOps comes in all shapes and sizes. Software delivery practices are often comprised of set of several complementing (or even competing) methodologies – such as leveraging Agile, DevOps and even a mix of ITIL, to create the combination that’s most suitable for your organization and that maximize your busines...
The goal of any tech business worth its salt is to provide the best product or service to its clients in the most efficient and cost-effective way possible. This is just as true in the development of software products as it is in other product design services. Microservices, an app architecture style that leans mostly on independent, self-contained programs, are quickly becoming the new norm, so to speak. With this change comes a declining reliance on older SOAs like COBRA, a push toward more s...
I have an article in the recently released “DZone Guide to Building and Deploying Applications on the Cloud” entitled “Fullstack Engineering in the Age of Hybrid Cloud”. In this article I discuss the need and skills of a Fullstack Engineer with relation to troubleshooting and repairing complex, distributed hybrid cloud applications. My recent experiences with troubleshooting issues with my Docker WordPress container only reinforce the details I wrote about in this piece. Without my comprehensive...
Digital means customer preferences and behavior are driving enterprise technology decisions to be sure, but let’s not forget our employees. After all, when we say customer, we mean customer writ large, including partners, supply chain participants, and yes, those salaried denizens whose daily labor forms the cornerstone of the enterprise. While your customers bask in the warm rays of your digital efforts, are your employees toiling away in the dark recesses of your enterprise, pecking data into...
Small teams are more effective. The general agreement is that anything from 5 to 12 is the 'right' small. But of course small teams will also have 'small' throughput - relatively speaking. So if your demand is X and the throughput of a small team is X/10, you probably need 10 teams to meet that demand. But more teams also mean more effort to coordinate and align their efforts in the same direction. So, the challenge is how to harness the power of small teams and yet orchestrate multiples of them...
You deployed your app with the Bluemix PaaS and it's gaining some serious traction, so it's time to make some tweaks. Did you design your application in a way that it can scale in the cloud? Were you even thinking about the cloud when you built the app? If not, chances are your app is going to break. Check out this webcast to learn various techniques for designing applications that will scale successfully in Bluemix, for the confidence you need to take your apps to the next level and beyond.
SYS-CON Events announced today that Peak 10, Inc., a national IT infrastructure and cloud services provider, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Peak 10 provides reliable, tailored data center and network services, cloud and managed services. Its solutions are designed to scale and adapt to customers’ changing business needs, enabling them to lower costs, improve performance and focus inter...
With DevOps becoming more well-known and established practice in nearly every industry that delivers software, it is important to continually reassess its efficacy. This week’s top 10 includes a discussion on how the quick uptake of DevOps adoption in the enterprise has posed some serious challenges. Additionally, organizations who have taken the DevOps plunge must find ways to find, hire and keep their DevOps talent in order to keep the machine running smoothly.
Wow, if you ever wanted to learn about Rugged DevOps (some call it DevSecOps), sit down for a spell with Shannon Lietz, Ian Allison and Scott Kennedy from Intuit. We discussed a number of important topics including internal war games, culture hacking, gamification of Rugged DevOps and starting as a small team. There are 100 gold nuggets in this conversation for novices and experts alike.
Much of the discussion around cloud DevOps focuses on the speed with which companies need to get new code into production. This focus is important – because in an increasingly digital marketplace, new code enables new value propositions. New code is also often essential for maintaining competitive parity with market innovators. But new code doesn’t just have to deliver the functionality the business requires. It also has to behave well because the behavior of code in the cloud affects performan...