Choose write behavior for your application.
Keep native database outcomes and your application’s completion requirements in view.
Native responses
MySQL and MariaDB writes wait for the database response, preserving affected-row counts, generated IDs, warnings and errors. Transactions are forwarded to the database.
Eligible queued writes
Where supported, selected single-statement autocommit writes can enter an in-memory FIFO queue. The native success response acknowledges acceptance into memory. Operations that require a database-generated result wait for that actual result.
Memory-only queue
Queued writes are not persisted or replicated. A process or host failure can lose accepted writes that have not reached the database. Select queue scope only for application operations that can use this behavior.
Drain and observe
Monitor queue depth and failed-write counters. Allow accepted work to drain before a planned stop, and review errors through accel logs errors, syslog and OpenTelemetry.
Need a hand with setup? Contact support