# File Storage {% hint style="warning" %} **This is the manual for older MicroStream versions (Version < 5.0).** **The new documentation (Version >= 5.0) is located at:** [https://docs.microstream.one/](https://docs.microstream.one/manual) {% endhint %} ## **Where does MicroStream store persistent data?** MicroStream stores persistent data in a physical form, typically in native file-system files. ## **Can my application use more than one MicroStream instance?** Yes, as many as you like. Each MicroStream instance represents one coherent entity graph of persistent data. ## **Is it possible to split the file-storage into many single files?** Yes. This is already done automatically. The minimum and maximum size of every partial file can be configured, although this is a very technical detail that should not be relevant in most cases. ## **May multiple JVM processes access the same MicroStream database?** At any given time, only one JVM process may directly access the files representing a unique set of data. Such a restriction is crucial for the correct execution of any application: changes to an application's persistent data have to be guarded by the rules of the application's business logic, i.e. the process that currently runs the application. Allowing another process to bypass these rules would eventually result in catastrophic consistency errors.\ The requirement to distribute an application over multiple processes must be solved by a clustering approach (e.g. by distributing logic AND persistent data over multiple processes or by having one process to serve as the data master for multiple worker processes). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://manual.docs.microstream.one/data-store/faq/file-storage.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.