Cloud Application: Don’t write to disk!

Share this post:

While most of your applications should work just fine in the cloud, there are a few things that make your application not ready for the cloud. Here’s a big one. 

Don’t write to disk….most of the time. Let me explain. The file system is a resource that isn’t persisted.  As you application instance gets restarted, updated, scaled or recreated, the file system it sits on changes – you get a new isolated chunk of disk each time. The physical location of your application or application server on disk should not be part of your application design. If you’re using the disk for temporary or cache purposes, you might be OK, but don’t try to avoid storing data in a database. Creating a database and accessing it in BlueMix is super easy!

IBM Cloud Technical Offering Manager

More stories
May 7, 2019

We’ve Moved! The IBM Cloud Blog Has a New URL

In an effort better integrate the IBM Cloud Blog with the IBM Cloud web experience, we have migrated the blog to a new URL:

Continue reading

May 1, 2019

Two Tutorials: Plan, Create, and Update Deployment Environments with Terraform

Multiple environments are pretty common in a project when building a solution. They support the different phases of the development cycle and the slight differences between the environments, like capacity, networking, credentials, and log verbosity. These two tutorials will show you how to manage the environments with Terraform.

Continue reading

April 29, 2019

Transforming Customer Experiences with AI Services (Part 1)

This is an experience from a recent customer engagement on transcribing customer conversations using IBM Watson AI services.

Continue reading