Cisco Cisco Unified Contact Center Management Portal 11.5(1) Technical References
Web service latencies are measured in the hundreds to thousands of milliseconds which is
significantly slower than the binary streaming operations between App Servers to Databases
found in traditional client server systems. Hence, make each call count by requesting or
doing as much as possible in each call
significantly slower than the binary streaming operations between App Servers to Databases
found in traditional client server systems. Hence, make each call count by requesting or
doing as much as possible in each call
HTTP/S is a best-effort delivery service. This means any request could simply be dropped.
Hence, the clients of the Unified CCMP Web Services have to handle this and retry.
Hence, the clients of the Unified CCMP Web Services have to handle this and retry.
Take the frequency of the messaging into account. Remedy: For provisioning, the majority of
data interactions are read-many/write-seldom making them suitable for caching techniques in
the higher levels; ideally caching at the edge nearest the users. In the context of many users
making many similar small calls then this can be simply implemented as taking the results
out of a higher level cache such as memcache.
data interactions are read-many/write-seldom making them suitable for caching techniques in
the higher levels; ideally caching at the edge nearest the users. In the context of many users
making many similar small calls then this can be simply implemented as taking the results
out of a higher level cache such as memcache.
High volume aggregation services which involve many elements of state based data queries
can be particularly difficult to scale. Hence, replicate key data items into a high level
persistent model (the Master Data Source) and use regular re-synchronization, ideally
retrieving data during off-hours in large, course-grained transactions.
can be particularly difficult to scale. Hence, replicate key data items into a high level
persistent model (the Master Data Source) and use regular re-synchronization, ideally
retrieving data during off-hours in large, course-grained transactions.
Repeated client calls to access server state can choke a network and degrade the server
performance. So cache data on the client whenever possible to avoid requests to the server.
performance. So cache data on the client whenever possible to avoid requests to the server.
The SOAP protocol is more resource-intensive than the REST equivalent. SOAP has a high
intrinsic overhead because it has to extract the SOAP envelope, parse the contained XML
information and handle the typing information required in every SOAP message. The XML
data cannot be optimized very much, and the binary representation of an object may be
expanded by around 500% when encoded in XML.
intrinsic overhead because it has to extract the SOAP envelope, parse the contained XML
information and handle the typing information required in every SOAP message. The XML
data cannot be optimized very much, and the binary representation of an object may be
expanded by around 500% when encoded in XML.
Unified CCMP Technical Overview
365