Sometimes we get so caught up in the latest ICT fads that we forget about the things we leave behind. Or more importantly, the things left behind for us to clean up! This month’s topic is data migration and we’re not talking about a CSV import: we’re talking serious migration.
This month has food and drinks provided by our good friends at Leukeleu and will be hosted at their shiny new offices! We’ll also have some great swag to give away and an update on the conference later this year.
19:00 – Welcome with drinks & food
19:30 – Main Talk: Data migration: How not to leave a legacy
20:30 – Raffle & News
20:35 – Social!
Main Talk – “Data migration: How not to leave a legacy”
When a company moves to a new software architecture, they usually prefer to keep the relevant data from their old system(s). This quickly gets complicated, because data is dirty, unreliable, there’s usually a lot of it, the old architecture looks nothing like the new one, and in some cases the Dutch Central Bank kindly requires you to prove you’ve done it right down to the last cent.
In this talk, I’ll talk about migrating data from a big, complicated system to a big, complicated system. I will use insurance systems as my example, because that’s what I work with, but the problems we encounter are pretty general.
We will not get extremely technical, but cover a few examples of the following topics:
• The many steps of data migration: how not to go insane when you’re changing everything
• Performance: streamlining the biggest batch-job your client will ever run
• How to prove completeness and accuracy
Speaker: Anna Baas (@venite)
After studying physics and working as a physics teacher and tutor, Anna decided she’d rather get paid for her programming hobby. (Her hobby wasn’t -exactly- writing backend Java for insurance companies, but close enough.) She has worked in various roles at Keylane|Quinity, the last two years as a software engineer in the data migration team, who migrate legacy data into Keylane’s architecture for new customers.