This article is a continuation of a series of posts to better understand how the pitfalls around the collection, maintenance, and storage of your cloud data can mean the difference between failure and success within your cloud strategy. The concepts in this series stem from brainstorming with my good friend Roel Hodzelmans and are additionally inspired by reactions from the audience to a talk given previously in Dublin, Ireland.
The initial post provided an introduction to cloud and data, and what that means in a cloud-native architecture beyond just storage. In this second article, we discuss the forgotten data that is often overlooked when planning for cloud-native architectural solutions.