Welcome!

Microservices Expo Authors: Sujoy Sen, Liz McMillan, Pat Romanski, Derek Weeks, Jason Bloomberg

Related Topics: @DevOpsSummit, Microservices Expo, Agile Computing, @CloudExpo, Cloud Security, @BigDataExpo, SDN Journal

@DevOpsSummit: Article

Continuous Infrastructure

How IT Went from the Back of the Class to the Front of the Board Room

Businesses have IT because apps deliver value to their customers. This can be direct value - a user-facing app. Or it can be indirect - an internal app for managing sales, marketing, or even HR transactions. Either way, the idea is that the app will make the business more efficient and responsive.

The purpose of IT used to be to develop, purchase and operate these apps. But today, every team in the business is writing apps, and every part of the business depends on the apps that they run. These apps have gotten bigger. They have become more complex. There are more apps everywhere, and they are more mission critical than before.

In fact, we are long past the point where any modern application is a single piece of software. Most apps these days run on top of a collection of common services - such as web servers, database servers, queue servers - even the storage space and network connections are increasingly consumed as-a-service, by apps.

So the purpose of IT has been transformed from being an operator of apps, to an operator of services to power them. What's different about being a provider of IT services, rather than an operator of applications?

  1. It's about scale.
  2. It's about efficiency.
  3. It's about speed.

Explaining the difference between scale-up, and scale-out, is beyond the scope of this article. But I encourage you to read Maged Michael's excellent summary of the topic[1]. Whether we're scaling the number of users, the amount of data, or the complexity of calculations required (or even if you're scaling all three) - the era of scale-up is drawing to a close.

So if we can't scale UP, we have to scale OUT - which means building multi-server distributed systems. These are notoriously tricky. (In fact, Google famously considers their expertise in this to be a key competitive advantage.) So when we've invested the work in developing a system for delivering a particular service, we're likely to try and get as many different apps to share that service as possible. This is the same type of thinking that encouraged object-oriented programming and object reuse - if we're all sharing the same system, we can invest more in making it as reliable and efficient as possible. I like to call this the "Warren Buffet" approach to enterprise architecture - put all your eggs in one basket, and then watch that damn basket!

So we can see that, as our businesses have become more and more dependent on IT apps, those apps have in turn become more and more dependent on scalable, efficient services. And as applications have gotten both larger and more complex, IT has had to focus more on the services that can power these applications - rather than just the applications themselves.

Now, technology doesn't necessarily make life better. Nor does it reduce the number of mistakes we make. But it *does* help us go faster, which means we can make mistakes at a faster and faster rate. And this is what it's done in business, too - IT has sped everything up.

The pursuit of speed in IT has been transforming everything about how we develop software over the past ten years. It started with our project management methodologies, switching from traditional SDLC approaches to Agile ones such as Scrum or Kan-Ban. As we sped development up, we needed to integrate and test our systems earlier, and the Continuous Integration ecosystem was born, with tools such as Jenkins and Build Bot at the heart of it. Eventually, the need for speed broke through from development and testing, into the production operations environments, and the DevOps movement was born. We're starting to see a raft of tools and technologies to support Continuous Deployment now - the most mature form of DevOps.

The final step in this metamorphosis is a revolution in the delivery of the underlying infrastructure services - the push to API-driven, or software-defined, ...well, everything. Only when Continuous Infrastructure supports the Continuous Deployment of Continuously Integrated and Continuously Prioritized apps and features, will our work be complete.

For more of my thoughts on apps and services, open source software and how to manage your IT infrastructure like 400-head of Holsteins, check out my blog at http://www.pistoncloud.com/blog.

1. http://www.cecs.uci.edu/~papers/ipdps07/pdfs/SMTPS-201-paper-1.pdf

More Stories By Joshua McKenty

Prior to co-founding Piston Cloud Computing, Joshua McKenty was the Technical Architect of NASA's Nebula Cloud Computing Platform and the OpenStack compute components. As a board member of the OpenStack Foundation, Joshua plays an instrumental role in the OpenStack community. Joshua has over two decades of experience in entrepreneurship, management and software engineering and architecture. He was the team lead for the development of the Netscape Browser (vs. 8) as well as AOL's IE AIM toolbar, and a senior engineer at Flock.com. He also led the successful first release of OpenQuake, an open source software application allowing users to compute seismic hazard, seismic risk and the socio-economic impact of earthquakes. In his spare time, Joshua has crafted a handmade violin and banjo, fathered two children, and invented his own juggling trick, the McKenty Madness.

@MicroservicesExpo Stories
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...
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...
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...
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...
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...
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.
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 ...
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...
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.
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.
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...