simple sticky notes transparency capabilities

#SIMPLE STICKY NOTES TRANSPARENCY CAPABILITIES UPDATE#
#SIMPLE STICKY NOTES TRANSPARENCY CAPABILITIES FULL#
#SIMPLE STICKY NOTES TRANSPARENCY CAPABILITIES SOFTWARE#

Here are some events generated as a customer placed an order on the platform: User action, API calls, callbacks (webhooks), recurring cron jobs can all generate Events. Let’s illustrate this with an imaginary e-commerce platform. “All changes to an application state are stored as a sequence of events.”

And finally we’ll reflect a bit on the ah-ha moments and the challenges that we’re going through with this approach - 9 months after having started to work on d.rip and 4 months after launch.

We will then talk about how we implemented a (minimal) Event Sourcing Framework at Kickstarter for d.rip.

We’ll go over a high level introduction to Event Sourcing where we will highlight the four components that make a (minimal) Event Sourcing system: Events, Calculators, Aggregates and Reactors.

So in this post we’d like to talk about Event Sourcing.

#SIMPLE STICKY NOTES TRANSPARENCY CAPABILITIES FULL#

These questions could be answered in seconds if we had a full history.

“Why is this subscription marked as inactive here but active on the payment platform? The customer is still getting charged for it!” “Was this post re-published at some point?” “Which posts had the category we just deleted?” And even then it’s quite hard to know “how we got there”. We add attributes like: updated_at, updated_by_user_id, accepted_at, destroyed_by_admin_id. The tedious hand crafted comments you see above are very similar to what we do to keep (some) data history. Unless you’re using Datomic or libraries like Papertrail.rb, the answer is very likely to be: Sigh.

#SIMPLE STICKY NOTES TRANSPARENCY CAPABILITIES UPDATE#

We would have to annotate files by hand, copy files to have some sort of backups and share code via… ftp? # Change: 14532 # Update At: 2018–04–23 # Update By: Philippe Creux # Reason: Fix a bug that was introduced sometimes between # change #12320 that’s in users.rb.backup-2018–02–11 # and change #14211 above (around line 2400) # def destroy # stroy_at = Time.now # end def destroy leted_at = Time.now endĬould you work without a tool managing code history? Nope. Think a second about how life would be (and was) without Source Version Control (git, svn, cvs, mercurial…). Rails contributions animated with gource. And thanks to all that, you can generate useful reports: number of commits per month, hotspots… and superb visualizations: When something goes wrong, you can find how a bug happened and when it was introduced.

Git is also a time machine, that allows you to go back in time and see what the code looked like back then ( git checkout You can also replay history and play what-if scenarios: go back in time, checkout a new branch, commit a change, and replay all the events commits that happened after that.

Who made the change, when it happened, what the change was (that’s the commit title), why the change was made (that’s a good commit description) and how the change was performed (well, that’s the diff). Type git log and you can see all the changes made to a codebase. Git is a fantastic example that’s used widely across the industry.

#SIMPLE STICKY NOTES TRANSPARENCY CAPABILITIES SOFTWARE#

Most software developers use a tool to keep track of code history. It’s simple and it has made our life so much better! Read on! We’ve implemented a minimal event sourcing framework at Kickstarter to power d.rip. Tl dr: Event Sourcing is to data what Git is to code.

Simple sticky notes transparency capabilities