|By Patrick Carey||
|March 16, 2014 03:00 PM EDT||
There's been plenty written and predicted about the future of cloud and Software-as-a-Service, and it's hard to argue with its benefits - for both organizations and users. If our cloud-based future is to come true though, we must pay closer attention to the service levels users are getting from Software-as-a-Service (SaaS) applications.
Obvious? Maybe not.
As many organizations make their first big move to the cloud with services like Office 365, a few common misconceptions - grounded in the general belief that once we move to the cloud, IT no longer owns direct responsibility for service levels - threaten to put them on a path to protracted outages and frustrated users.
The fact is that if your users can't access a cloud-based service, they are not going to call the service provider. They are going to call the IT help desk (maybe you) directly and the IT team will be expected to fix whatever problem exists, ASAP. Users don't care whether or not the problem is located in infrastructure owned and operated by their IT department, the ISP, or the cloud service provider. If they aren't having a good experience, IT will take the heat.
How do you avoid this? Here are six myths that can derail your use of the cloud. Falling for them can put you on a path to protracted service outages and frustrated users. In addition, I try to shed light on what's needed to fill in some of the gaps that exist when it comes to monitoring SaaS applications.
1. "I don't need to monitor. I have a guaranteed SLA from the provider."
Your SaaS service provider is likely able to run their datacenters with higher availability than most IT organizations, but they are not 100%. Service level guarantees are great, but if you aren't monitoring your SaaS service, how do you know your SLA is actually being met? In addition, service level guarantees only cover outages that the provider can control, i.e., their own networks, servers, and applications, not any of your infrastructure and not the Internet service providers that connect you. You're on your own to monitor and manage those.
2. "I don't need my own monitoring tools. I use the service provider dashboard."
As with the guarantees themselves, service health dashboards only cover the service provider's infrastructure, not the end-to-end service. These dashboards provide generic information that may or may not be relevant to your users and may not be up to date. Remember, they are built to be general status communication tools, not real-time monitoring solutions.
3. "I didn't monitor your previous hosted email service. Why monitor Office 365 now?"
Consuming apps from the cloud is not the same as consuming managed/hosted services. Managed Service Providers (MSPs) and Hosters are often running dedicated infrastructure for you and monitor those services on your behalf. Those services often extend to provide monitoring and management of your on-premise infrastructure as well. While there are managed service providers offering value-added services around Office 365, if you buy directly or through a reseller, you have to monitor the solution yourself.
4. "My existing tools monitor my cloud apps as well as my on-premise apps."
Not really. Most traditional systems management solutions (e.g., CA, BMC, Tivoli, System Center) are designed to monitor systems where they have direct access to the applications, servers, log files, and SNMP messages. They are not built to monitor services where the majority of the service infrastructure lies outside the IT periphery. Network management tools tend to focus on low-level protocol and network device monitoring and diagnostics, and are not built to monitor user experience. Both of these tools can be difficult and costly to use.
On the other end of the spectrum, web monitoring solutions often either run generic protocol tests or run from the providers' locations rather than within your own network.
None of these solutions can provide active, end-to-end monitoring of service performance and user experience from behind your firewall to the service provider and back.
5. "I don't need to monitor. My users tell you when they are having problems."
This may be okay for some less critical applications, but for most organizations these days, communication and collaboration apps, like email, are mission critical. If the service is down, so is your company. What happens when the users report a problem? Where do you start to look? Do you immediately get on hold with the Office 365 support line? It's probably not even a Microsoft problem.
Speed to resolution is key. You want to be notified before users are impacted and when an issue is identified you want to isolate it and get it resolved as quickly as possible.
6. "Moving to the cloud means monitoring is someone else's problem, right?"
The cloud provides many CapEx and OpEx benefits for IT, e.g., fewer servers and apps to directly manage and house. It also provides built-in world-class features, service, and security, regardless of budget and staffing. However, local IT is still on the hook for the quality of service realized by users. When a user has an issue they will call you, not Microsoft.
Moving to the cloud, doesn't mean monitoring goes away, but it does fundamentally change the requirements. You need to monitor these solutions, but you need to look at different approaches, ones that are designed to meet the needs of the cloud. You have to be able to monitor and troubleshoot infrastructure you cannot touch - the end-to-end service delivery chain from your premises, through the various Internet service providers, to the application provider and back. To do this you need to take a global view of the cloud service, tracking performance measurements from multiple access points. By comparing these measurements, you have the ability to quickly detect, isolate, and resolve issues affecting cloud application performance before they negatively impact your users and your organization. The more monitoring points you have the better your ability to do this. It's difficult for smaller organizations to accomplish this level of visibility on their own, but as adoption of cloud applications grows, you'll begin to see new solutions that pool resources across multiple customers, and provide this level of visibility to any SaaS consumer.
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...
May. 6, 2016 03:00 AM EDT Reads: 915
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 ...
May. 6, 2016 02:45 AM EDT Reads: 523
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...
May. 6, 2016 01:30 AM EDT Reads: 1,161
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 ...
May. 6, 2016 12:30 AM EDT Reads: 766
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...
May. 5, 2016 11:30 PM EDT Reads: 1,068
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.
May. 5, 2016 07:45 PM EDT Reads: 1,646
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...
May. 5, 2016 05:15 PM EDT Reads: 1,736
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...
May. 5, 2016 05:00 PM EDT Reads: 604
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...
May. 5, 2016 05:00 PM EDT Reads: 1,379
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...
May. 5, 2016 02:30 PM EDT Reads: 1,213
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...
May. 5, 2016 02:30 PM EDT Reads: 1,494
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...
May. 5, 2016 01:30 PM EDT Reads: 1,156
Last week I had the pleasure of speaking on a panel at Sapphire Ventures Next-Gen Tech Stack Forum in San Francisco. Obviously, I was excited to join the discussion, but as a participant the event crystallized not only where the larger software development market is relative to microservices, container technologies (like Docker), continuous integration and deployment; but also provided insight into where DevOps is heading in the coming years.
May. 5, 2016 09:45 AM EDT Reads: 254
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.
May. 5, 2016 05:45 AM EDT Reads: 1,036
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...
May. 5, 2016 04:00 AM EDT Reads: 2,085
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...
May. 5, 2016 03:15 AM EDT Reads: 1,519
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.
May. 4, 2016 09:00 PM EDT Reads: 2,269
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...
May. 3, 2016 07:30 PM EDT Reads: 1,963
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...
May. 3, 2016 04:45 PM EDT Reads: 1,170
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.
May. 3, 2016 12:15 PM EDT Reads: 1,664