The PrivOps Matrix™ Architecture
Primary elements
Parts repository
Pipeline component templates
Data in process
Operating environment
Pipeline microservices
The PrivOps Matrix was designed with two core elements – the Matrix Hybrid Integration Fabric™ and the Matrix metaDNA™ catalog. The first is an application architecture Gartner calls an “event driven, mesh app and service architecture” (MASA - referring to a mesh of separate services) to create hybrid applications.
The Matrix metaDNA™ catalog contains the state, policy, code, and data objects within the PrivOps Matrix™. Each object is stored as time series data for audit and troubleshooting; organizations can demonstrate every change, every event, every access at every point in time. The catalog is built on top of distributed open source Apache Cassandra. Apple, for example, runs more than 78,000 Cassandra nodes as the backbone for their technology platform. At IBM, The Weather Company processes over 30 billion API requests daily on its Cassandra based IoT platform.
The Matrix Hybrid Integration Fabric™ operating environment consists of a set of standard functions and libraries that handle workflow automation, time series versioning of everything in the metadata catalog , data ETL and integration. Integration and automation are greatly simplified since developers need not have any knowledge of how the Matrix stores its data or the underlying database. The Matrix uses node.js, the most popular and quickest growing open source server-side programming language. As a result, integrations have access to nearly 500,000 plug-ins making it easy to connect to virtually any API, software, database, or tool in existence.
Physical Architecture
Because PrivOps Matrix™ nodes can be located anywhere – cloud providers and/or on-premise and because Cassandra provides for replication across datacenters, disaster recovery is built in by design.
