Analytics & Data Warehouse

If it holds customer or payment data, in our reading it does. The warehouse processes that data, keeps backups and time-travel copies, and controls access through the cloud provider's identity service, all outside Nigeria. The directive names each of those elements. This is general guidance, not legal advice; confirm the interpretation with your compliance team.

They share the same architecture and SQL. Greenplum remains the choice if you already run it and need continuity. Apache Cloudberry is the open source successor under Apache governance with a newer PostgreSQL core, and it is our default for new deployments. WarehousePG is the community fork for teams that want a drop-in open source continuation of Greenplum, and SynxDB is the commercially supported route. We support all four and help you choose on the basis of your workload and upgrade timeline.

For the steady, predictable workloads of a bank (daily loads, month-end closes, regulatory returns), a correctly sized MPP cluster on local NVMe storage matches or beats a cloud warehouse, and the cost does not rise with usage. Where public cloud wins is elastic burst for rare, very large jobs; we design headroom for month-end rather than for hypothetical peaks.

Iceberg gives the bank an open, engine-independent copy of every dataset with ACID guarantees, schema evolution and time travel. Spark, the warehouse and data-science tools all read the same tables, so a change of engine later is not a second migration. It also provides the immutable snapshots that make regulatory reports reproducible.

Corrective support with contractual response times on the warehouse engine, Spark, Iceberg and Hadoop, CVE patching by severity, version lifecycle management and, at the higher tiers, a named engineer, quarterly health checks, query tuning and upgrade support, including the move from Greenplum to Cloudberry.

For a warehouse of ten to thirty terabytes with a few hundred pipelines, assessment and build take seven to ten weeks and the domain-by-domain migration another six to ten. Dual running for two reporting cycles per domain is included, because the comparison of results is what gives the finance team confidence to switch.

Yes. None of the components requires internet access at runtime. Images, packages and patches are delivered through an internal signed registry, and we run the same tooling for our own air-gapped deployments.

Only if you already have it or need very cheap deep storage for history that is rarely queried. New deployments usually use S3-compatible object storage with Iceberg instead. We support HDFS estates and help move them to object storage when it makes sense.