“dove-tailing” with subsequent “sematic” ETL steps Ingestion into relational data lake semantic layer (cubes, marts etc..) ODS, e.g. redshift, greenplum or RDS ETL users HVR Strengths • Persistent stakeholders (who SQL) a ‘cascade’ process must be implemented to compact changes into a presentation layer. – Latency is higher – Basic replication (not rich) means higher TCO Added value from HVR • Timekey definitions Ingestion into data lake storage compaction storage, e.g. CSV or Avro files on S3 semantic layer (cubes, marts etc..) ETL ODS, e.g. redshift, greenplum or RDS users HVR Strengths • Publish/subscribe

VMware Greenplum 6 Documentation VMware, Inc. 15 Provider Layer 326 Infrastructure Layer 326 Virtual Machine Cluster Layer 326 Greenplum Layer 327 Planning VMware vSphere with Greenplum 327 Calculating across all of the parallel PostgreSQL database instances. The Greenplum interconnect (the networking layer) enables communication between the distinct PostgreSQL instances and allows the system to behave Documentation VMware, Inc. 294 About the Greenplum Interconnect The interconnect is the networking layer of the Greenplum Database architecture. The interconnect refers to the inter-process communication

VMware by Broadcom 16 Layered Architecture 339 Provider Layer 340 Infrastructure Layer 340 Virtual Machine Cluster Layer 340 Greenplum Layer 341 High Availability 341 Planning VMware vSphere with across all of the parallel PostgreSQL database instances. The Greenplum interconnect (the networking layer) enables communication between the distinct PostgreSQL instances and allows the system to behave Documentation VMware by Broadcom 308 About the Greenplum Interconnect The interconnect is the networking layer of the Greenplum Database architecture. The interconnect refers to the inter-process communication

vSphere Architecture 307 Layered Architecture 307 Provider Layer 308 Infrastructure Layer 308 Virtual Machine Cluster Layer 308 Greenplum Layer 309 VMware Greenplum 6 Documentation VMware, Inc 13 Planning across all of the parallel PostgreSQL database instances. The Greenplum interconnect (the networking layer) enables communication between the distinct PostgreSQL instances and allows the system to behave Documentation VMware, Inc 276 About the Greenplum Interconnect The interconnect is the networking layer of the Greenplum Database architecture. The interconnect refers to the inter-process communication

vSphere Architecture 297 Layered Architecture 297 Provider Layer 297 Infrastructure Layer 297 Virtual Machine Cluster Layer 298 Greenplum Layer 298 Planning VMware vSphere with Greenplum 299 Calculating across all of the parallel PostgreSQL database instances. The Greenplum interconnect (the networking layer) enables communication between the distinct PostgreSQL instances and allows the system to behave Documentation VMware, Inc 268 About the Greenplum Interconnect The interconnect is the networking layer of the Greenplum Database architecture. The interconnect refers to the inter-process communication

vSphere Architecture 292 Layered Architecture 292 Provider Layer 293 Infrastructure Layer 293 Virtual Machine Cluster Layer 293 Greenplum Layer 294 Planning VMware vSphere with Greenplum 294 Calculating across all of the parallel PostgreSQL database instances. The Greenplum interconnect (the networking layer) enables communication between the distinct PostgreSQL instances and allows the system to behave Documentation VMware, Inc. 264 About the Greenplum Interconnect The interconnect is the networking layer of the Greenplum Database architecture. The interconnect refers to the inter-process communication

vSphere Architecture 266 Layered Architecture 266 Provider Layer 266 Infrastructure Layer 266 Virtual Machine Cluster Layer 266 Greenplum Layer 267 Planning VMware vSphere with Greenplum 268 Calculating across all of the parallel PostgreSQL database instances. The Greenplum interconnect (the networking layer) enables communication between the distinct PostgreSQL instances and allows the system to behave configuration on your chosen platform. About the Greenplum Interconnect The interconnect is the networking layer of the Greenplum Database architecture. The interconnect refers to the inter-process communication

storage. The segments communicate with each other and the master over the interconnect, the networking layer of Greenplum Database. VMware Greenplum v6.18 Documentation VMware, Inc. 227 Greenplum Database recommended configuration on your chosen platform. The Interconnect The interconnect is the networking layer of Greenplum Database. When a user connects to a database and issues a query, processes are created Documentation VMware, Inc. 269 funcy Functional tools focused on practicality future Compatibility layer between Python 2 and Python 3 futures Backport of the concurrent.futures package from Python 3 Gensim

storage. The segments communicate with each other and the master over the interconnect, the networking layer of Greenplum Database. VMware Greenplum v6.19 Documentation VMware, Inc. 234 Greenplum Database recommended configuration on your chosen platform. The Interconnect The interconnect is the networking layer of Greenplum Database. When a user connects to a database and issues a query, processes are created functools module from Python 3.2.3 funcy Functional tools focused on practicality future Compatibility layer between Python 2 and Python 3 futures Backport of the concurrent.futures package from Python 3 Gensim

storage. The segments communicate with each other and the master over the interconnect, the networking layer of Greenplum Database. VMware Greenplum v6.17 Documentation VMware, Inc. 161 Greenplum Database recommended configuration on your chosen platform. The Interconnect The interconnect is the networking layer of Greenplum Database. When a user connects to a database and issues a query, processes are created functools module from Python 3.2.3 funcy Functional tools focused on practicality future Compatibility layer between Python 2 and Python 3 futures Backport of the concurrent.futures package from Python 3 Gensim