{"id":1019,"date":"2016-06-18T08:44:32","date_gmt":"2016-06-18T08:44:32","guid":{"rendered":"https:\/\/blog.ngocha.biz\/?p=1019"},"modified":"2016-06-18T08:44:32","modified_gmt":"2016-06-18T08:44:32","slug":"managed-service-providers-devops","status":"publish","type":"post","link":"https:\/\/blog.ngocha.biz\/?p=1019","title":{"rendered":"Are Managed Service Providers About to Put DevOps Out to Pasture"},"content":{"rendered":"

People are still wrapping their heads around the \u201cDevOps<\/a>\u201d concepts of automated, continuous development, deployment, and maintenance, yet some analysts are already forecasting that DevOps will soon be eclipsed by managed services.<\/p>\n

The names may change, but the principles of customer-driven app development and support will survive long into IT\u2019s future, whether cloud-based, in-house, or a combination of the two.<\/p>\n

In the beginning, there were developers and operators (a.k.a. sysadmins): The first group wrote the code and tossed it over the wall to the second group, who installed and ran the programs, and supported the people who used the programs. Every so often, perhaps a few times a year, the developers sent over an update, which operators implemented. And so it went for years and years.<\/p>\n

But those pesky users kept demanding more features and functions, faster speeds, and simpler interfaces. Occasional software updates simply wouldn\u2019t do. The arrival of agile development and continuous deployment led to the creation of DevOps, an amalgam that puts developers in the operations realm and operators in the development mix. And so it went for\u2026 months and months?<\/p>\n

Hold onto your hats, folks. The Golden Age of DevOps appears to be ending almost as quickly as it began. As Smartling co-founder and CTO Andrey Akselrod writes in an April 6, 2016, article on TechCrunch, code happens so quickly these days that you don\u2019t have time to treat development, testing, implementation, and maintenance as separate, distinct activities.<\/p>\n

From day one, DevOps was criticized for failing to maximize people\u2019s strengths. After all, developers know development, and operators know administration. Would a restaurant ask its chefs to serve and its servers to cook? There\u2019s no quicker way to alienate employees than to give them tasks and responsibilities for which they are unsuited.<\/p>\n

However, there are other problems with the DevOps model. For one thing, sysadmins still have a heck of a lot of infrastructure to manage. Another obstacle to the smooth merger of formerly distinct operations is the traditional QA function, which creates a bottleneck in the continuous deployment model. Agile development requires that testing is baked into all stages: development, deployment, and maintenance\/updates.<\/p>\n

Converting in-house infrastructure into an on-demand utility<\/h2>\n

Despite these shortcomings, what truly put the stake in the heart of DevOps is the cloud \u2013 specifically, managed services. Amazon Web Services, Google Compute Engine, Microsoft Azure, and other managed services simplify development by allowing developers to focus on code rather than database deployment, backups, and uptime monitoring, all of which are automated by the services.<\/p>\n

As implementation and management become automated, the \u201cOps\u201d side of DevOps focuses on security, compliance, and cost management. Once again, the roles of your IT staff are clearly defined.<\/p>\n

What many organizations fail to consider is how the role of the IT department itself becomes more prominent within and without the company as a result of agile development. Today, nearly all firms are software-driven. Increasingly, that software has migrated to the \u201cflexible technology stack,\u201d as explained in Chef Software\u2019s Automation and the DevOps Workflow (pdf). Yet IT must continue to support legacy software and meet regulatory requirements, neither of which port easily to agile workflows and rapid-deployment models.<\/p>\n

Full-stack automation extends application quality and manageability practices to your entire infrastructure as well as all individual services.<\/p><\/blockquote>\n

One of the defining characteristics of DevOps is increased reliance on service-oriented architectures, which offer \u201cstable, independent services that use web protocols and associated architectural patterns.\u201d Each service can be implemented, deployed, and scaled independently, which makes it easier for teams to align apps with business functions. Similarly, automation is a keystone of DevOps that encompasses the development\/test\/production environment, deployment and management of cloud resources, and release pipelines.<\/p>\n

The benefits of such an \u201cautomation platform\u201d are a clear view of the entire network state, support for complex dependencies between network nodes, scalability, fault tolerance, security, workflow automation, and the ability to accommodate multiple platforms and legacy systems.<\/p>\n

DevOps principles permeate managed services<\/h2>\n

As with other tech buzzwords, there is no single, consistent definition of \u2018DevOps.\u2019 The concepts of agility, scalability, speed, and efficiency were adopted first by developers migrating to AWS and other cloud platforms-as-a-service (PaaS). The challenge for operations staff was to apply the same tried-and-true disciplines of in-house IT management to public, private, and hybrid clouds based on managed services.<\/p>\n

All the components of today\u2019s virtual environments need to be tracked, managed, secured and terminated when they\u2019re no longer needed. Along with \u201cwriting bug-free and effective code as quickly as possible,\u201d as Computerworld\u2019s David Braue explains in a March 22, 2016, article, you have to work closely with the business side to ensure the apps meet customers\u2019 needs efficiently and profitably. Bringing developers closer to customers may be the lasting legacy of the short-lived DevOps era.<\/p>\n

Meet your customers\u2019 needs for frequent, automatic application updates by converting from internal-driven IT to a customer-driven, mobile-supporting operation.<\/p>\n

Managed services now work more closely with internal DevOps teams via such programs as the AWS OpsWork toolkit and IBM\u2019s BlueMix cloud platform. As more organization-wide discipline and policy are applied through service providers, DevOps concentrates on compliance, security, and cost management. Yet making DevOps work in your company is more challenging now than ever. On April 14, 2016, an article, Braue lists nine characteristics of a successful DevOps strategy:<\/p>\n

    \n
  1. A well-defined strategy and objectives<\/li>\n
  2. Business stakeholder education<\/li>\n
  3. IT-business alignment of priorities<\/li>\n
  4. Relevant IT knowledge and skills<\/li>\n
  5. Cross-functional IT processes<\/li>\n
  6. Cultural harmony within IT<\/li>\n
  7. The right infrastructure and tooling<\/li>\n
  8. The right suppliers and support<\/li>\n
  9. Security and compliance measures<\/li>\n<\/ol>\n

    The term \u201cDevOps\u201d may become an anachronism before the decade (or the year) is out, but the concept\u2019s customer focus, integration, automation, speed, and scalability will serve as the foundation of the managed services that will dominate IT operations in the future. When you\u2019re asked to decide between DevOps and managed services, the best response for your organization will likely be \u201cboth.\u201d<\/p>\n

    \n

    Ngu\u1ed3n:<\/strong> Are Managed Service Providers About to Put DevOps Out to Pasture \u2014 DevOpsCube<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    Source: https:\/\/devopscube.com\/managed-service-providers-devops\/<\/p>\n","protected":false},"author":1,"featured_media":1020,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1019","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/1019","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1019"}],"version-history":[{"count":0,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/1019\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/media\/1020"}],"wp:attachment":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1019"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1019"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1019"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}