|By Patrick Carey||
|October 21, 2013 02:17 PM EDT||
A few weeks ago I was trying to update some files I have stored on a cloud storage service (that will remain nameless). I had moved my files there a while back as a way to make it easier to access them from my various devices and to avoid losing them during the next inevitable hard drive failure. For the most part I've been happy with the service, but on this day, I was unable to access the site.
Not good, as I was rushing to make some changes and send the files to a colleague.
Frustrated by my situation, I asked a co-worker to see if he was also having problems. He was, so we did the next logical thing you would expect. We went to the service provider's status page to see what they had to say. According to it, the service was healthy and there were no current service or maintenance notices.
Twitter! Of course. Whenever services like YouTube or Hulu have outages, users light-up Twitter with comments and laments. Sure enough, a quick Twitter search showed that, yes, there was a widespread problem that had started only a few minutes prior, and already there was a trending hashtag.
This example shows what's great about Twitter. It is an immensely powerful platform for creating instant virtual communities sharing information and opinion around a topic of common interest. The Twitter community as a group was able to do a better job than the service provider itself of informing users that there was a problem with the service. I and the other storage service users -- at least the ones also on Twitter -- had formed an impromptu global network of monitors, watching the service from hundreds of thousands of access points. Together could confirm for each other that there was a service-wide outage.
Well, not really. Yes, I could see a number of people on Twitter reporting that they couldn't access the service, but this was all anecdotal information (along with a fair amount of opinion). I had no idea who these other users were or where they were located. For all I knew we might all be customers of the same internet service provider and maybe the problem was there and not with the storage service itself. In addition, while I could go to Twitter to confirm that I wasn't the only one experiencing an outage -- even as the service provider's status dashboard said everything was okay -- I was still searching for evidence after the fact. There was no practical way for me to be notified proactively, nor was I able to reliably see service performance degrading prior to the outage.
Herein lies the problem for manufacturers, or any organization, looking to leverage SaaS applications -- particularly mission critical email, collaboration, and document storage -- as part of their IT infrastructure. While it may be okay for me to use Twitter to monitor Hulu, you obviously can't operate a business this way. Organizations need the same level of visibility and troubleshooting capability for SaaS apps that they've come to rely on for traditional on-premise applications. This includes:
- Proactive issue detection and alerting
- Quantitative data on application performance
- Ability to accurately measure service level attainment v. target goals
- Ability to identify problem sources so the time to isolate and fix is minimized
That last one is particularly tricky for SaaS since most of the datacenter and network infrastructure is outside organizations' IT perimeters. You can't directly see or touch the server or network equipment and neither can your traditional monitoring and management tools. It's not surprising, then, that we often hear from IT admins that they have had to resort to using Twitter because otherwise they are flying completely blind. It's not enough, but at least it's something.
Despite its shortcomings, there is a lot to be said for the "power of the crowd" that is so fundamental to Twitter. What if we could take that same model and use it to proactively monitor our SaaS applications? First, it would require some type of active monitoring behind your firewall at the locations where users access their SaaS applications. These "sensors" could act like Twitter users, constantly running transactions against the service and collecting data on transaction and network node performance. They would also allow you to proactively detect and notify an IT Admin of any outages or performance anomalies BEFORE they impact your users.
Then, what if we could collect and share real-time performance data from those sensors (yours as well as other users' sensors) into a global database maintained as part of your cloud service. You'd then be able to access this data to gain visibility into the health of the complete service delivery chain between you and the SaaS provider. For example, you could:
- View current status, alerts, network statistics, and performance trends for one or more of your own sensors to determine if you have service issues affecting a particular location or subnet, so you can point and fix faults in your own infrastructure and get users back online quickly
- Analyze your sensor data with the rest of the crowd to determine whether service issues are systemic to the application provider or the result of downstream internet service provider problems; you may not be able to fix these directly, but with this information you would know which service provider to call and could provide them with details to speed their time to resolution
- Confirm exactly what service levels you are getting from your application service providers, with detailed outage data needed both for internal reporting and for provider service level guaranty refund requests
The goal of every IT shop is to keep their application users online and happy. But with SaaS, that's more difficult to do because administrators do not have the same visibility that they do with on-premise applications. We, as a community, need to come up with ways to change that. Taking a cue from Twitter, and leveraging the crowd - seems like a great place to start.
As the world moves towards more DevOps and microservices, application deployment to the cloud ought to become a lot simpler. The microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. In his session at 17th Cloud Expo, Raghavan "Rags" Srinivas, an Architect/Developer Evangeli...
Oct. 9, 2015 11:45 AM EDT Reads: 169
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, will explore HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
Oct. 9, 2015 11:30 AM EDT Reads: 161
Docker is hot. However, as Docker container use spreads into more mature production pipelines, there can be issues about control of Docker images to ensure they are production-ready. Is a promotion-based model appropriate to control and track the flow of Docker images from development to production? In his session at DevOps Summit, Fred Simon, Co-founder and Chief Architect of JFrog, will demonstrate how to implement a promotion model for Docker images using a binary repository, and then show h...
Oct. 9, 2015 11:15 AM EDT Reads: 118
The web app is agile. The REST API is agile. The testing and planning are agile. But alas, data infrastructures certainly are not. Once an application matures, changing the shape or indexing scheme of data often forces at best a top down planning exercise and at worst includes schema changes that force downtime. The time has come for a new approach that fundamentally advances the agility of distributed data infrastructures. Come learn about a new solution to the problems faced by software organ...
Oct. 9, 2015 11:00 AM EDT Reads: 885
Our guest on the podcast this week is Jason Bloomberg, President at Intellyx. When we build services we want them to be lightweight, stateless and scalable while doing one thing really well. In today's cloud world, we're revisiting what to takes to make a good service in the first place. Listen in to learn why following "the book" doesn't necessarily mean that you're solving key business problems.
Oct. 9, 2015 11:00 AM EDT Reads: 2,229
Achim Weiss is Chief Executive Officer and co-founder of ProfitBricks. In 1995, he broke off his studies to co-found the web hosting company "Schlund+Partner." The company "Schlund+Partner" later became the 1&1 web hosting product line. From 1995 to 2008, he was the technical director for several important projects: the largest web hosting platform in the world, the second largest DSL platform, a video on-demand delivery network, the largest eMail backend in Europe, and a universal billing syste...
Oct. 9, 2015 10:45 AM EDT Reads: 158
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.
Oct. 9, 2015 10:15 AM EDT Reads: 149
In their session at DevOps Summit, Asaf Yigal, co-founder and the VP of Product at Logz.io, and Tomer Levy, co-founder and CEO of Logz.io, will explore the entire process that they have undergone – through research, benchmarking, implementation, optimization, and customer success – in developing a processing engine that can handle petabytes of data. They will also discuss the requirements of such an engine in terms of scalability, resilience, security, and availability along with how the archi...
Oct. 9, 2015 10:00 AM EDT Reads: 404
Containers are revolutionizing the way we deploy and maintain our infrastructures, but monitoring and troubleshooting in a containerized environment can still be painful and impractical. Understanding even basic resource usage is difficult - let alone tracking network connections or malicious activity. In his session at DevOps Summit, Gianluca Borello, Sr. Software Engineer at Sysdig, will cover the current state of the art for container monitoring and visibility, including pros / cons and li...
Oct. 9, 2015 10:00 AM EDT Reads: 230
Any Ops team trying to support a company in today’s cloud-connected world knows that a new way of thinking is required – one just as dramatic than the shift from Ops to DevOps. The diversity of modern operations requires teams to focus their impact on breadth vs. depth. In his session at DevOps Summit, Adam Serediuk, Director of Operations at xMatters, Inc., will discuss the strategic requirements of evolving from Ops to DevOps, and why modern Operations has begun leveraging the “NoOps” approa...
Oct. 9, 2015 10:00 AM EDT Reads: 152
The last decade was about virtual machines, but the next one is about containers. Containers enable a service to run on any host at any time. Traditional tools are starting to show cracks because they were not designed for this level of application portability. Now is the time to look at new ways to deploy and manage applications at scale. In his session at @DevOpsSummit, Brian “Redbeard” Harrington, a principal architect at CoreOS, will examine how CoreOS helps teams run in production. Attende...
Oct. 9, 2015 10:00 AM EDT Reads: 1,257
For it to be SOA – let alone SOA done right – we need to pin down just what "SOA done wrong" might be. First-generation SOA with Web Services and ESBs, perhaps? But then there's second-generation, REST-based SOA. More lightweight and cloud-friendly, but many REST-based SOA practices predate the microservices wave. Today, microservices and containers go hand in hand – only the details of "container-oriented architecture" are largely on the drawing board – and are not likely to look much like S...
Oct. 9, 2015 10:00 AM EDT Reads: 496
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....
Oct. 9, 2015 10:00 AM EDT Reads: 233
With containerization using Docker, the orchestration of containers using Kubernetes, the self-service model for provisioning your projects and applications and the workflows we built in OpenShift is the best in class Platform as a Service that enables introducing DevOps into your organization with ease. In his session at DevOps Summit, Veer Muchandi, PaaS evangelist with RedHat, will provide a deep dive overview of OpenShift v3 and demonstrate how it helps with DevOps.
Oct. 9, 2015 09:00 AM EDT Reads: 664
What Is Emergent About Emergent Architecture? By @TheEbizWizard | @DevOpsSummit #DevOps #BigData #API
All we need to do is have our teams self-organize, and behold! Emergent design and/or architecture springs up out of the nothingness! If only it were that easy, right? I follow in the footsteps of so many people who have long wondered at the meanings of such simple words, as though they were dogma from on high. Emerge? Self-organizing? Profound, to be sure. But what do we really make of this sentence?
Oct. 9, 2015 08:00 AM EDT Reads: 400
Application availability is not just the measure of “being up”. Many apps can claim that status. Technically they are running and responding to requests, but at a rate which users would certainly interpret as being down. That’s because excessive load times can (and will be) interpreted as “not available.” That’s why it’s important to view ensuring application availability as requiring attention to all its composite parts: scalability, performance, and security.
Oct. 9, 2015 06:00 AM EDT Reads: 429
Last month, my partners in crime – Carmen DeArdo from Nationwide, Lee Reid, my colleague from IBM and I wrote a 3-part series of blog posts on DevOps.com. We titled our posts the Simple Math, Calculus and Art of DevOps. I would venture to say these are must-reads for any organization adopting DevOps. We examined all three ascpects – the Cultural, Automation and Process improvement side of DevOps. One of the key underlying themes of the three posts was the need for Cultural change – things like t...
Oct. 9, 2015 05:00 AM EDT Reads: 337
In today's digital world, change is the one constant. Disruptive innovations like cloud, mobility, social media, and the Internet of Things have reshaped the market and set new standards in customer expectations. To remain competitive, businesses must tap the potential of emerging technologies and markets through the rapid release of new products and services. However, the rigid and siloed structures of traditional IT platforms and processes are slowing them down – resulting in lengthy delivery ...
Oct. 9, 2015 05:00 AM EDT Reads: 1,012
There once was a time when testers operated on their own, in isolation. They’d huddle as a group around the harsh glow of dozens of CRT monitors, clicking through GUIs and recording results. Anxiously, they’d wait for the developers in the other room to fix the bugs they found, yet they’d frequently leave the office disappointed as issues were filed away as non-critical. These teams would rarely interact, save for those scarce moments when a coder would wander in needing to reproduce a particula...
Oct. 9, 2015 05:00 AM EDT Reads: 301
It is with great pleasure that I am able to announce that Jesse Proudman, Blue Box CTO, has been appointed to the position of IBM Distinguished Engineer. Jesse is the first employee at Blue Box to receive this honor, and I’m quite confident there will be more to follow given the amazing talent at Blue Box with whom I have had the pleasure to collaborate. I’d like to provide an overview of what it means to become an IBM Distinguished Engineer.
Oct. 9, 2015 04:00 AM EDT Reads: 252