> For the complete documentation index, see [llms.txt](https://blog.gomchik.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.gomchik.com/books/seven-databases-in-seven-weeks/factors-to-consider.md). # Factors to consider * What data types does it support and what are your own requirements for data types ? * Do you need flexible schema or rigid schema ? * Is query flexibility important to you ? * Do you want to store large amounts of data across several machines * How much important is sata safety (via ACID compliance or something else) * Do you need Triggers * Do you need Transactions (for atomicity) * Do you need Stored Procedures * How much important is having ability to create **Views** for you ? * Can you live without **Joins** ? * Do you need **Partitioning** ? * Do you need to store only large blobs of data ? * Do you have enough information about the database requirements (like schema, probable tables, data types etc) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://blog.gomchik.com/books/seven-databases-in-seven-weeks/factors-to-consider.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.