3 interesting data techniques I've used to solve business problems

The year was 2014

• I was busy working on my first public API
• REST was having it's day in the sun
• I discovered a talk...

"Turning the database inside out with Apache Samza" by Martin Kleppmann

The only bit I remember

This is a basic version of CQRS

(Command and Query Responsibility Segregation)

We use this pattern in heaps of places with a payroll product.

Let's extend on this idea and look at some options

We could expire the data

Was the edit to payslip 9 correct or incorrect?

We could state the changes

Now we can see the logic behind the changes

There's heaps of variations to this concept

We can even use it to deal with race conditions

Set to true when the shift has been processed

Race conditions are the best

We start processing the job

Fetch the shift details from the db

Edit is made

Processed flag is marked as true and the edit is not processed

I love race conditions

We could process each change sequentially but that might be unnecessary

Race conditions = pure bliss

Grab the latest version which is unprocessed and process the latest version

Repeat when more changes come in

Questions?