Application database: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
The client’s database is called the application database and is not required | {{DISPLAYTITLE: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 | 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 | application database since the performance/reliability requirements vary depending on the application. Frequently it | ||
| Line 11: | Line 13: | ||
'''Caveats''' | |||
Database access is usually synchronous. This is not a problem but it should not be overlooked when designing the | |||
Database access | |||
application database. A lot of synchronous access to a slow database (or on a slow link) can cause significant call | 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 | delays (not in the data path but in the control path). Using the multi-threaded feature of the CMC library, we can | ||
| Line 22: | Line 23: | ||
---- | ---- | ||
Return to the Toolpack [[User Guide]] | Return to the Toolpack [[User Guide]] | ||
Latest revision as of 10:22, 12 July 2022
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