ERP & database sync
Turn database rows into governed exchanges, and exchanges back into rows.
Bitween holds pooled connections to PostgreSQL, MySQL, SQL Server and Oracle. Poll named statements into exchanges, write deliveries into tables and stored procedures, and keep every row’s journey on record.
How it works
Four things to know.
Named statements only
SQL lives in statements on the data source and is checked by the database when saved. Subscriptions refer to statements by name, and every value is bound as a parameter.
Five receive modes
Poll with an incrementing or timestamp cursor, or drain rows in bulk and marker modes that mark each row after its exchange is stored.
Write with query, execute or call
Deliveries run selects, inserts, updates and stored procedures, and store the returned rows, affected counts and timing as the response.
Separation of duties
Grant statement permissions to the people who write SQL without giving them the right to change connection credentials.
-- ReceiveMode: incrementing Key column: id Cursor column: id
select id, order_no, customer, updated_at
from orders
where id > @cursor
order by idOutcomes
What your team gets.
- Each row becomes one exchange with its own history
- No SQL templated from partner input
- Several jobs can poll one database independently
- Schema browser and connection tests built in
Good to know: Database receiving has no deduplication: if marking a row fails after its exchange is stored, the row is read again. Order statements by the cursor column and keep mark statements idempotent.
Documentation
Read the details.
Industries
Where this pattern shows up.
Put every integration on one governed pipeline.
Talk to the architects who build Bitween about your partners, systems and message volumes, or start from the docs and run it yourself today.