Embracing the cloud means preparing for problems you can’t control

Cloud computing. Cloud-native computing. Software-as-a-service. They're all secure and reliable. Except when they're not.

Recently, we've seen Microsoft Azure suffer an extended outage and we've seen Docker Hub get hacked. (Docker also has a new CEO.) Gartner published a report (subscription required) on how enterprises should think about adopting SaaS applications, in the context of data backup (or lack thereof). You can get details and context on all of these things by reading the links.

If we hop in our wayback machines and travel just a few years, we'll also re-encounter AWS outages that seem to have brought down the internet; Slack outages that might or might not have halted productivity within thousands of companies; and any number of SaaS startups shutting down, getting hacked or just plain losing data. It's enough to make someone think twice about getting rid of their server closets and packaged software.

But, of course, clinging to the past would be crazy for any company that actually wants to remain competitive by using and building cutting-edge applications. For all but a small handful of companies (some of which actually run public clouds), there is no realistic vision of a successful future that doesn't involve some combination of clouds, containers and SaaS-probably all three. The trick is adopting these things intelligently and accounting for the very real possibility that something will, at some point, go wrong.

What the best solutions look like might vary widely based on the company, although it seems logical to settle for nothing less than cloud-native best practices around high availability and automated security patching. That probably means building resilience into the compute, storage and networking tiers, designing apps that tolerate component failure, and, yes, sometimes using multi-cloud platforms

And while container security is a newer concern than, say, VM security, there actually are a lot of tools-from startups, large IT vendors and even open source communities-that can provide peace of mind. A SaaS application that doesn't let you export your data is probably not a SaaS application worth using (good news: there's no shortage of SaaS applications).

What we can't do is let fear and uncertainty get in the way of progress, which is what cloud computing, however defined and in all its forms, ultimately delivers. Getting things like security and reliability right might require spending a little more time and money on software, engineers, and maybe even lawyers, but the payoff over the long term should make up for any early investments many times over. Assuming that settling for the status quo isn't a viable option, thinking ahead is a much better option than rushing into the cloud and ending up on the receiving end of an outage, breach or other large-scale incident that could have been avoided with just a little forethought.





WHAT YOU NEED TO KNOW THIS WEEK
How the tech-savvy are adapting

Stripe's fifth engineering hub is remote (Stripe): Supporting remote employees might soon become a serious recruitment strategy, if it's not already. Few good people want to uproot if they don't have to.

How Slack hires a red team (and you can too!) (Several People Are Coding): Your company probably needs penetration testers to find security weaknesses. Here's some good advice from Slack.

Square acquires conversational AI startup Eloquent Labs (TechCrunch): Sometimes, you need to acquire talent and/or capabilities. 

So. Much. Cloud. News.

Everything Microsoft announced at Build (VentureBeat): Here's a useful roundup if you're a Microsoft shop or thinking about becoming one. There's almost certainly more news if you dig a little.

You can now rent an entire AI supercomputer from Google Cloud (Data Center Knowledge): The headline is a bit hyperbolic, but you can rent Google's custom AI hardware, called TPUs, which perform very well on certain tasks. 

AI meets digital transformation

Canadian trucking firm adopts AI, then jumps into consulting (Wall Street Journal): One of the cool things about today is that you can solve an internal problem with software, and if it's broadly applicable, make a new business out of it. 

Amazon says fully automated shipping warehouses are at least a decade away (The Verge): That's not actually too long, if you think about it.  

Microsoft teams up with Starbucks on predictive drive-thru ordering and bean-to-cup blockchain (GeekWire): Predictive ordering could be useful, but the predictive maintenance work here (on in-store equipment) certainly will be. 

Toyota AI Ventures launched $100M fund to invest in robotics and autonomous tech (TechCrunch): For orgs with the resources, venture funds and/or university partnerships are a good way to get access to cutting-edge work in spaces like AI. 


OTHER RESOURCES WORTH CHECKING OUT

Take the State of DevOps Survey (DORA/Google Cloud)

Serverless computing vs platform-as-a-service: Which is right for your business? (ZDNet)

Webinar: Deploying Kubernetes to Drive Business, Not Complexity (Pivotal)

Market Guide to Container Management Software (Gartner; free download)

Hack Your Culture to Drive Quality and DevOps Success (Gartner; free download)

Increase IT Value: Shift Your Seat at the Table (Gartner; subscription required)

CIOs Must Leverage Both Business Models and Strategy (Gartner; subscription required)

Adopt I&O Key Performance Indicators to Deliver Digital Business Value (Gartner; subscription required)

Beyond Agility - Adaptive Enterprises Hold The Winning Hand (Forrester; subscription required)



Subscribe Now

Thank you!

Follow us on Twitter Join the conversation on LinkedIn Like us on Facebook Visit our YouTube channel

 

pivotal.io

Pivotal, and the Pivotal logo are registered trademarks or trademarks of Pivotal Software, Inc. in the United States and other countries. All other trademarks used herein are the property of their respective owners.
© 2019 Pivotal Software, Inc. All rights reserved. 875 Howard Street, Fifth Floor, San Francisco, CA 94103. Published in the USA.
문의