Two-way sync
Changes in Google AlloyDB or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep Google AlloyDB and Rillet in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.
Stacksync mirrors Bill, Journal Entry, Invoice Payment, Charge from Rillet into Indexes, Sequences, Replication Slots, Databases in Google AlloyDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Google AlloyDB, and rows your code writes or updates flow back into Rillet with validation, so the finance system stays the system of record.
Updates written to the synced tables in Google AlloyDB propagate into Rillet, so automations can create or correct finance records without custom integration code.
Changes in Rillet appear in Google AlloyDB as row changes, so you can trigger downstream logic with the database tooling you already use.
Customers, invoices, and payments from Rillet live in Google AlloyDB as regular tables or collections your team can join, index, and query.
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 AlloyDB objects | Rillet objects | |
|---|---|---|
| Replication Slots Logical replication artifacts that back log-based change capture. | Custom Field Synced with incremental and full sync per the Stacksync docs. | |
| Databases Standard PostgreSQL databases within an AlloyDB cluster that syncs connect to. | Account Synced with incremental and full sync per the Stacksync docs. | |
| Schemas Namespaces used to separate synced SaaS data from application tables. | Customer Synced with incremental and full sync per the Stacksync docs. | |
| Tables Primary read/write target for bi-directional sync with CRMs and other systems. | Vendor Synced with incremental and full sync per the Stacksync docs. | |
| Views Curated projections used as read-only sync sources. | Invoice Synced with incremental and full sync per the Stacksync docs. | |
| Materialized Views Precomputed aggregates refreshed and synced outward on a schedule. | Credit Memo Synced with incremental and full sync per the Stacksync docs. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google AlloyDB–Rillet connection.
Changes in Google AlloyDB or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google AlloyDB or Rillet 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 AlloyDB or Rillet record.
Track your Google AlloyDB ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google AlloyDB and Rillet.
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 AlloyDB and Rillet 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 AlloyDB and Rillet 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 AlloyDB and Rillet: authenticate both systems, choose the objects to sync (such as Google AlloyDB's Replication Slots and Databases), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Rillet side: Bill, Journal Entry, Invoice Payment, Charge, plus custom fields where Rillet exposes them. On the Google AlloyDB side: Indexes, Sequences, Replication Slots, Databases. Stacksync auto-detects both schemas and converts types between the two systems.
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 AlloyDB and Rillet: Write back safely; React to financial events; Query finance data like any other data. Updates written to the synced tables in Google AlloyDB propagate into Rillet, so automations can create or correct finance records without custom integration code.
Google AlloyDB: SQL wire protocol (PostgreSQL-compatible), with connectivity through the AlloyDB Auth Proxy or private IP. Authentication: Database credentials or IAM database authentication. Rillet: REST API (OpenAPI-specified, with production and sandbox environments). Authentication: API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync. Stacksync manages authentication, retries, and rate limits on both sides.
Rillet: The REST API authenticates with API keys and publishes an OpenAPI specification, with separate production and sandbox environments. Google AlloyDB: It supports PostgreSQL logical replication, enabling log-based change capture from the write-ahead log. Stacksync's field mapping accounts for these differences between Google AlloyDB and Rillet without custom code.
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 AlloyDB and Rillet.