Sharding a database
When an organization grows, the database(s) it may reach a point
where it will be reaching one or more of its resource limits. Action
will be needed, and one of the solutions is to use a sharded setup;
that is, having several databases with identical structure, and
data residing in one (or subset) of the databases.
At Booking.com, we have several sharded databases. In this talk,
we will look how we transformed a highly volatile database to a
sharded setup, without its users noticing and how Perl helped us
to achieve this.
Attended by: Michiel Beijen, Søren Lund (slu), Bas Bloemsaat (basbl), Arjen Laarhoven, Bart Orbons, Abe Timmerman (abeltje),