![]() ![]() ![]() They write the application business and technical needs are aligned. They recognize they don't have the deep understanding of the AWS platform internally. They may have some lower level environments up there, and they're ready to make a commitment to move production workload for an app, or a set of apps. Often, it's when they've done some experimentation on Amazon. Our clients come to us in a number of different stages. So when a company brings Logicworks in, what challenge are they facing? Short version: they want to get serious about AWS services. I won't get into the technical DevOps weeds in this piece, but it’s worth noting that LogicWorks is primarily a Puppet shop, though they can do Chef, etc. Given that DevOps has a do-it-yourself ethos within organizations, why do companies need external DevOps services? And how do DevOps projects play out, particularly in industries where compliance and regulatory hurdles tend to slow cloud initiatives? The skills tips were handy, but I saved two burning questions. In Finessing the DevOps transition, I delved into how Jason McKay, SVP and CTO,of Logicworks shifted from perceiving DevOps-as-a-threat to DevOps-as-a-core-service-offering. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |