Source: thenewstack.io
An Architect’s Guide to Edge StorageCategory: Business, Data, Kubernetes, Infrastructure, Architecture, encryption, automation
This is a remarkable statement given its size today ($6 billion) and expectations for growth ($61 billion by 2028).
This installment in MinIO’s architect series (see also the guides to hybrid cloud storage and multicloud) focuses on storage at the edge.
In this model, the application, compute and storage exist at the edge and are designed to store and process data in situ.
It’s crucial for the storage architecture to use self-healing and automation to ensure that data is safe even when drives fail and to automatically fail over to other data centers if all the drives in a particular edge location fail.
This post presents two models, one where data is gathered at the edge and another where the data is pushed to the edge.
This installment in MinIO’s architect series (see also the guides to hybrid cloud storage and multicloud) focuses on storage at the edge.
In this model, the application, compute and storage exist at the edge and are designed to store and process data in situ.
It’s crucial for the storage architecture to use self-healing and automation to ensure that data is safe even when drives fail and to automatically fail over to other data centers if all the drives in a particular edge location fail.
This post presents two models, one where data is gathered at the edge and another where the data is pushed to the edge.
Related Articles
Community Partners
DevOps Careers