Operations | Monitoring | ITSM | DevOps | Cloud

DevOps has great potential; when it’s done right, it offers organizations improved collaboration, quick innovation, better quality, and shorter delivery cycles. But the reality is that some businesses don’t carry the DevOps process through to the data layer.

If you shudder thinking about compilation for different platforms, I know the feeling. One of the Java promises, the WORA (Write Once, Run Anywhere) principle, while revolutionizing platform independence, it stopped short of one more step – to be able to deploy anywhere. Personally, I think that WORADA sounds awesome, but I guess before Docker it didn’t occur to people that eliminating “works on my machine” is as simple as shipping your machine.

One of the advantages that Ubuntu brings to the cloud equation is improving an organization’s ability to run in multiple clouds. Running containers on top of Ubuntu further increases portability. Mist is an open-source multi-cloud management platform that helps teams centrally manage and control their Ubuntu instances across many different cloud environments and/or bare metal. This removes some of the operational and financial barriers to running applications in multiple clouds.

To keep up with today’s competitive landscape and with the new normal induced by the pandemic, organizations must modernize their ventures, instigate innovation and be more agile. However, the process of replacing legacy systems isn’t precisely as agile as one thinks it would be. It takes time, and that’s something your company doesn’t have. You need solutions that consolidate years of transformation into mere months.

Virtana recently published the results of a new State of Hybrid Cloud survey. One of the findings is that 81% of companies in the study who have started their migration to the public cloud have engaged multiple providers. This result tallies with a recent Gartner survey of public cloud users, in which 81% of those respondents said they are working with two or more providers.

I’ve learned a lot about serverless in my first full year at Stackery after joining from the Ops-focused automation company, Puppet. I’ve learned how to deploy rich CMS-backed web applications in a serverless way, how to cast incantations using CloudFormation’s intrinsic functions, but most of all I’ve learned that there’s a lot to learn in order to be successful in AWS.

Mutual of Enumclaw, a 100-year-old insurance company from Washington, modernized their policy processing system in order to reduce TCO and focus on their software and customers - not infrastructure. However, they realized serverless development still presents many DevOps challenges like environments, workflows, documentation and local development.

Azure Storage is like an all you can eat buffet, except the more you eat, the more you pay! This has provided organisations an almost limitless supply of storage, and as we all know, the more that’s available, the more we’ll use. Azure Storage has changed the way many organisations operate both in terms of availability and service.

Once you’ve committed to changing your culture in order to automate your database deployments, what’s next? You’ve already done the hard part, making the decision to shift the culture. Now, what’s involved is just lots of labor. There are three things you can do to begin your Database DevOps journey: Let’s discus these in detail. It’s important to understand, not just why these are your first three steps, but why they should occur in this precise order.

When it comes to your business’s global internet access, network speed, security and performance are paramount. Many enterprises use a premium internet service to meet the needs of their global operations. One option available to them, which we have covered extensively already on this blog, is to use dedicated internet access across a private MPLS network. The other is to use an IP transit service.