The boom of digital commerce is making all businesses take a closer look at how they deliver great customer experiences. To stay competitive, businesses today are using cloud-native architectures, because the cloud-native applications they produce deploy quickly and better support the continuous improvement cycles of agile methodology. Behind the practicality of keeping online customers happy are distributed cloud environments that business applications use for each customer interaction.
Any new technological breakthrough tends to be greeted by two opposing factions. On one hand, you have promoters, for whom this technology is a panacea, the cure for every ailment plaguing the current environment.
If you’ve never searched for ways to improve help desk efficiency, do you really work in IT? For experienced IT leaders and L1 agents, it’s a familiar problem. It usually sounds something like this.
Every Lambda function comes with 512MB of ephemeral storage in the shape of a /tmp directory. This storage space can be reused across multiple invocations for the same instance of a Lambda function. Each instance of a function has its own /tmp directory and data is not shared amongst different instances of a function.
Remember when Slack went down in early January? The three-hour outage, set off by AWS capacity issues, cost the company an untold amount of money. And the effects rippled across the enterprise. The outage devalued the company’s stock and seemed to send all 142,000 of its customers to Twitter to gripe. This high-profile outage is just the most recent of many outages highlighting the critical nature of continuous availability. And there’s only one answer to the problem.
