> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/apis-and-integration/application-database.md). # Application Database The client’s database is called the application database, and although it is not required, it is doubtful that large systems will do without one. There is no restriction on the the DBMS of the application. It is up to the client to design the application database since the performance/reliability requirements vary depending on the application. Frequently it will be used to store: * Customer data records * Routing information (dial plans) * Client accounts (subscribed features) * Prompts * Call states for HA switchover **Caveats** Database access is usually synchronous. This is not a problem but it should not be overlooked when designing the application database. A lot of synchronous access to a slow database (or on a slow link) can cause significant call delays (not in the data path but in the control path). Using the multi-threaded feature of the CMC library, we can protect a call from another call’s asynchronous operations but we cannot protect it from himself. This can be prevented with good database design. *** Return to the Toolpack [User Guide](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/user-guide/README.md) --- # 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://prosbcdocs.telcobridges.com/telecom-references/apis-and-integration/application-database.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.