Most applications are stateful. Stateful is when streaming services remember where you left off in a movie even if you switch devices, or mobile applications store users’ preferences or recently opened files. For application-level cases, it’s the ability to recover from a session interruption, putting the users back to the place they left off, without loss of data.
We come from a stateful world. Stateful applications remember things about states, which is durable across sessions. The state data is stored within some nonvolatile mechanism, such as physical storage, including databases.
Enter containers, with new challenges and opportunities regarding state retention.
It’s hard to believe Kubernetes didn’t hit 1.0 until mid-2015 (a year after its first commit), given that the container orchestration platform is now in production at 78 percent of enterprises surveyed by the Cloud Native Computing Foundation (CNCF). That’s crazy fast adoption.
And if we’re going to talk about “crazy fast adoption,” it’s worth pointing out that just a year ago, 58 percent of enterprises were running Kubernetes in production, according to the CNCF’s 2018 report.
This speaks to the power of containers as enterprises look to improve how they develop applications. It also underscores just how
Popular online marketplace Etsy recently completed a two-year migration from 2,000 on-premises servers to Google Cloud. The Etsy website and mobile app provide an online shop window to makers of hand-crafted and niche goods, but with more than two million sellers on the platform by 2018, the in-house bare metal infrastructure was starting to creak.
Etsy was founded in 2005, well into the internet era but long before the explosion of public cloud services. The firm went public in 2015 and soon afterward made cloud migration a priority, so that it could scale its services without having to make big
In news that I would file under “duh,” almost 60 percent of U.K. businesses think that cloud has overpromised and underdelivered, according to a report sponsored by the consulting company Capita.
The report surveyed 200 IT decision-makers in the United Kingdom, and found that an overwhelming nine in ten respondents confessed that cloud migration has been delayed or pushed off due to “unforeseen factors.”
I’m just speculating, but it’s been my experience that those “unforeseen factors” usually include one or more of these three problems:
Unexpected cloud complexity has put so much stress on the newly formed cloudops groups that
Building and running modern cloud-native applications has its risks. One of the biggest is that you’re sharing computing resources with an unknown number of other users. Your memory and CPU are shared, and there’s always a possibility that data may accidentally leak across boundaries, where it can be accessed from outside your organization.
A breach, even an accidental one, is still a breach, and if you’re using Azure or another cloud platform to work with personally identifiable information or even your own financial data, you’re in breach of any compliance regulations. It’s not only user or financial data that could