In many companies a single SQL Server or PostgreSQL database answers every read: microservices, web and
mobile apps, branches and point-of-sale terminals. As usage grows, reads compete with writes, and the central
database becomes the bottleneck for everyone.
This video shows a practical pattern: keep writes on the central database and move read-only slices of
the data to where they are used , in SQLite, PostgreSQL or MariaDB, refreshed by dbSlice on a schedule.
Who it is for
Architects looking for a way to cut read traffic on the central database without rewriting the apps.
Teams running branches or terminals that need local data, even when the link to headquarters is slow.
DBAs who want the copy to be a scheduled job with a log, not a script someone has to remember.
What the video shows
One synchronization per slice.…