Platform Architecture. The Jive Cloud platform architecture is unique to the market and based on a distributed (not centrally hosted) model. It offers our customers a single, transparent experience that is at the same time limitlessly scalable, natively redundant, and extremely fault tolerant. Jive Cloud is the engine behind Jive’s industry-leading uptime, world-class customer satisfaction, and unmatched call quality and user experience. Jive Cloud is a cloud-based platform, operating from several dispersed, worldwide datacenter locations. Jive chooses datacenter facilities that are essential to the markets we serve, enabling us to provide highly available service and resilient network access to any geographic market. Jive’s global datacenter footprint includes tier one centers in: Los Angeles, CA, New York, NY, Dallas, TX, Chicago, IL, and the United Kingdom. Jive has sufficient coverage diversity to ensure our customers have enough redundant access points to deliver consistent service and high availability. Jive only partners with tier one datacenters, which have shown a commitment to a professional standard of conduct, integrity, and ethical values. All Jive selected datacenters have successfully completed AT-101 SOC II security audits. These audits stringently evaluate datacenter management, security, and controls over infrastructure and information, as well as the the people, procedures, and systems which operate and support them. All datacenter facilities perform proactive maintenance on all critical security systems, and include fully redundant UPS, backup generators, and cooling systems. Each datacenter also includes scalable bandwidth options, business continuity solutions, managed firewalls, remote hands, load balancing and a variety of security related services. Jive’s computing platform is built on x86-based hardware, ensuring easy access to additional components as necessary. Computing resources are virtualized and clustered to create a true cloud computing environment. Top-quality network equipment (e.g., Cisco, Brocade, and Juniper) provide highly available access to all computing resources. The call infrastructure component of Jive Cloud is where call processing, routing, and endpoint registration take place. Different subcomponents are responsible for managing PSTN integration, delivering specific call functionality, and managing the actual media streams and handsets involved in making internal and external calls. Call routing in Jive Cloud utilizes a microservice...
Platform Architecture. 6.1 OVERVIEW
Platform Architecture. 5 2.1. High Availability .................................................. 5 2.2. Scalability ........................................................ 6 2.3. Access Control ..................................................... 6 2.4. Interface Support .................................................. 6 2.5. Protocols .......................................................... 6 2.6. Latency Performance ................................................ 6 2.7. Server support ..................................................... 6
Platform Architecture. 2.1. HIGH AVAILABILITY The ASN-GW should have the following HA features: - System should be designed to provide carrier class with 99.999% availability - No Single Point of failure. - Hitless software upgrades. - Hitless failover for non-stop forwarding. - ASN-GW should have messaging if a connection limit has been reached to communicate to the BS to contact another ASN-GW.
Platform Architecture. This category covers the general requirements for the entire PLATOON platform reference architecture that defines its scope and characteristics: for instance, PLATOON architecture must avoid vendor lock-in providing a technologically agnostic environment leveraging open source components and public standard. The PLATOON reference architecture will be also compliant with other public initiative as the COSMAG reference architecture (3), FIWARE (2), SGAM (4) and IDS (1). In particular IDS reference architecture ensures data sovereignty, security and privacy when sharing data/tools among platform users. In order to be compatible with IDS, PLATOON reference architecture must be able to integrate the main mandatory components of IDS reference architecture, i.e. the connector and the identity provider (a.k.a DAPS). The PLATOON reference architecture must allow some of the components of the reference architecture to be hosted at the component level (e.g. edge computing), on premise and in the cloud. Finally, the PLATOON reference architecture must enable the exploitation of digital services (both data and data analytics tools) through a Marketplace.
Platform Architecture. The City has a multi-cloud strategy. The City prefers the Solution is hosted outside of the City’s data centers and maintained by the Contractor. The hosting facilities must meet the requirements provided in Exhibit F-1 Information Technology and Security Requirements.
Platform Architecture. This section provides a component-level overview as an introduction for the component-level interfaces and sub-components presented in Section 3 and 4, respectively. It also outlines the relationships in the overall platform and the scopes of orchestration of resources and services that exist in the overall system.
Platform Architecture
