What is the difference between file oriented storage and transaction oriented storage

Transaction-oriented storage or database storage is a more modern approach to maintaining business information files.

A business employing a transaction-oriented approach to storage uses a storage-area network — SAN — to integrate files across multiple information systems. Each information unit within the system has its own set repository where new information relating to that unit appears.

This storage method eliminates the need to create new files every time a transaction occurs. Instead, a business can allocate new information to files containing matching transaction information. For example, an SAN can have individual customer files that contain purchasing information relevant to each individual customer.

Storing information in a database that all departments within a business can access allows a company to shrink its devoted space for file storage. More info. In a database, you have options you don't have with files. Now try to:. There are lots of other good points but these are the first mountains you're trying to climb when you think of a file based db alternative.

Those guys programmed all this for you, it's yours to use; think of the likely most frequent scenarios, enumerate all possible actions you want to perform on your data, and decide which one works better for you.

Again, if you're storing JPG pictures and only ever look for them by one key their id maybe? Filesystems, btw, are close to databases today, as many of them use a balanced tree approach, so on a BTRFS you can just put all your pictures in one folder - and the OS will silently implement something like an early SQL query each time you access your files.

Programming rarely says "never" or "always". Those who say "database always wins" or "files always win" probably just don't know enough. That's it. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Database vs File system storage Ask Question. Asked 5 years, 3 months ago.

Active 1 month ago. Viewed k times. Improve this question. Sriram Sriram 1, 2 2 gold badges 9 9 silver badges 14 14 bronze badges. Add a comment. Active Oldest Votes. For very complex operations, the filesystem is likely to be very slow. Advantage of the File System over Data base Management System is: When handling small data sets with arbitrary, probably unrelated data, file is more efficient than database. When you first put a box of files in there, it seems like you have plenty of space.

Object storage, on the other hand, is like the warehouse, except with no roof. In this case, you can think of object storage as valet parking while file storage is more like self-parking yes, another analogy, but bear with me! When you pull your car into a small lot, you know exactly where your car is.

Your car will be stored somewhere, and when you need it, the valet will get the car for you. All of these features and advantages also extend to object storage in the cloud. For a real-life example of why metadata makes a difference, we can look at X-rays. An X-ray file would have limited metadata associated with it, such as created date, owner, location, and size. An X-ray object , on the other hand, could have a rich variety of metadata information. The metadata could include patient name, date of birth, injury details, which area of the body was X-rayed — in addition to the same tags that the file had.

This makes it incredibly useful for doctors to pull up the relevant information for reference. If you want a more straightforward side-by-side comparison, take a look at this table that compares object-based storage vs file storage:. It basically contains wide and sparsely oriented populated tables. It has no built-in support for partitioning.

It basically supports Automatic Partitioning. Next Introduction of Database Normalization. Recommended Articles. Article Contributed By :. Easy Normal Medium Hard Expert. Writing code in comment? Please use ide. Load Comments.