Two-way sync
Changes in Google Cloud Spanner or IBM AS/400 instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud Spanner and IBM AS/400 in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between Google Cloud Spanner and IBM AS/400 continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Keep the same dataset live in both Google Cloud Spanner and IBM AS/400, so each workload runs on the engine that suits it.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Google Cloud Spanner objects | IBM AS/400 objects | |
|---|---|---|
| Tables Relational tables mapped one-to-one to sync targets. | Rows / records The unit of read and write, accessed via SQL or record-level access. | |
| Rows The unit of read and write in each sync cycle, keyed by primary key. | Journals and journal receivers The change log that enables log-based CDC on journaled files. | |
| Interleaved tables Child rows physically co-located with parents; synced as related records. | Data queues Program-to-program messaging objects sometimes used to hand events off to integrations. | |
| Secondary indexes Used to make incremental read queries efficient on non-key columns. | Libraries The schema-equivalent containers that scope which files a sync reads. | |
| Change streams Capture inserts, updates, and deletes for log-style change data capture. | Physical files (tables) The Db2 for i tables mapped directly to sync targets. | |
| Views Read-only projections useful for shaping data before it leaves Spanner. | Logical files (views) Indexed or filtered views over physical files, usable as read sources. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–IBM AS/400 connection.
Changes in Google Cloud Spanner or IBM AS/400 instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud Spanner or IBM AS/400 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Google Cloud Spanner or IBM AS/400 record.
Track your Google Cloud Spanner ⇄ IBM AS/400 sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and IBM AS/400.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Google Cloud Spanner and IBM AS/400 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Google Cloud Spanner and IBM AS/400 objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Google Cloud Spanner and IBM AS/400: authenticate both systems, choose the objects to sync (such as Google Cloud Spanner's Tables and Rows), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Google Cloud Spanner and IBM AS/400: Cross-engine sync; Migration with zero-downtime cutover; Shared reference data between services. Keep the same dataset live in both Google Cloud Spanner and IBM AS/400, so each workload runs on the engine that suits it.
Google Cloud Spanner: GRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects). Authentication: Google Cloud IAM (service accounts). IBM AS/400: SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access. Authentication: IBM i user profile credentials (database credentials). Stacksync manages authentication, retries, and rate limits on both sides.
Google Cloud Spanner: Interleaved tables physically store child rows with their parent rows, which affects how related records are read. IBM AS/400: Journaling writes row-level before/after images to journal receivers, which is the basis for log-based CDC on IBM i. Stacksync's field mapping accounts for these differences between Google Cloud Spanner and IBM AS/400 without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Google Cloud Spanner and IBM AS/400 records are not retained after a sync operation.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Google Cloud Spanner and IBM AS/400.