Why don’t we write a database file system? Isn’t a file system practically a database already? Isn’t layering an OS between the data and the database application slowing things down?
In: Engineering
There are file type storage systems that are based on files or “objects”. These are very popular in cloud computing because they scale really well across a network. AWS S3 is an example of this as well as Azure Blob Storage. There are other technologies called “key value” stores that have a similar approach (AWS DynamoDB), where a key is an identifier and the values are the things you want to store. The key can be a unique identifier or can even be something that resembles a file path. Anyways, things get messy when files are not on a single computer and someone wants to update a file. Different data stores have different strategies for accomplishing this with different degrees of success. Other considerations is finding the data you are looking for, how to efficiently store the data, and cost/performance – if the data is stored on a running computer or sitting there waiting for a computer to read it (share vs share nothing).
Latest Answers