BROADCASTS.com

b"When companies migrate to the Cloud, they are literally changing how they do everything in their IT department. If lots of customers exclusively rely on a service, like us-east-1, then they are directly impacted by outages. There is safety in a herd and in numbers because everybody sits there, down and out. But, you don\\u2019t engineer your application to be a little more less than a single point of failure. It\\u2019s a bad idea to use a sole backing service for something, and it\\u2019s unacceptable from a business perspective.\\nToday, we\\u2019re talking to Chris Short from the Cloud and DevOps space. Recently, he was recognized for his DevOps\\u2019ish newsletter and won the Opensource.com People\\u2019s Choice Award for his DevOps writing. He\\u2019s been blogging for years and writing about things that he does every day, such as tutorials, codes, and methods. Now, Chris, along with Jason Hibbets, run the DevOps team for Opensource.com\\nSome of the highlights of the show include:\\n\\nChris\\u2019 writing makes difficult topics understandable. He is frank and provides broad information. However, he admits when he is not sure about something.\\nSJ Technologies aims to help companies embrace a DevOps philosophy, while adapting their operations to a Cloud-native world. Companies want to take advantage of philosophies and tooling around being Cloud native.\\nMany companies consider a Cloud migration because they\\u2019ve got data centers across the globe. It\\u2019s active-passive backup with two data centers that are treated differently and cannot switch to easily.\\nSome companies do a Cloud migration to refactor and save money. A Cloud migration can result in you having to shove your SAN into the USC1. It can become a hybrid workflow.\\nLift and shift is often considered the first legitimate step toward moving to the Cloud. However, know as much as you can about your applications and RAM and CPU allowances. Look at density when you\\u2019re lifting and shifting.\\nKnow how your applications work and work together. Simplify a migration by knowing what size and instances to use and what monitoring to have in place.\\nSome do not support being on the Cloud due to a lack of understanding of business practices and how they are applied. But, most are no longer skeptical about moving to the Cloud. Now, instead of \\u2018why cloud,\\u2019 it becomes \\u2018why not.\\u2019\\n\\n\\nDon\\u2019t jump without looking. Planning phases are important, but there will be unknowns that you will have to face.\\nDowntime does cost money. Customers will go to other sites. They can find what they want and need somewhere else. There\\u2019s no longer a sole source of anything.\\nThe DevOps journey is never finished, and you\\u2019re never done migrating. Embrace changes yourself to help organizations change.\\n\\nLinks:\\nChris Short on Twitter\\nDevOps'ish\\nSJ Technologies\\nAmazon Web Services\\nCloud Native Infrastructure\\nOracle\\nOpenShift\\nPuppet\\nKubernetes\\nSimon Wardley\\nRackspace\\nThe Mythical Man-Month\\nAtlassian\\nBuzzFeed\\nQuotes by Chris:\\n\\u201cLet\\u2019s not say that they\\u2019re going whole hog Cloud Native or whole hog cloud for that matter but they wanna utilize some things.\\u201d\\n\\u201cThey can never switch from one to the other very easily, but they want to be able to do that in the Cloud and you end up biting off a lot more than you can chew\\u2026\\u201d\\n\\u201cCreate them in AWS. Go. They gladly slurp in all your VM where instances you can create a mapping of this sized thing to that sized thing and off you go. But it\\u2019s a good strategy to just get there.\\u201d\\n\\u201cWe have to get better as technologists in making changes and helping people embrace change.\\u201d"