persist and list with database
create episodeAction list reponse (with mocked timestamp, started and total)
create episodeActions with received values
update existing episodeActions by unique episode link
receive and store subscription changes
deal with multiple subscription changes in single request
split database into subdirectories
only return subscription changes younger then passed parameter since
parse passed timestamp
parse passed timestamp for episode_actions listing
only return list of urls for subscription changes
align list endpoint naming schema
store userId with episode actions and subscriptions
return json object on application root route
thrillfall
Matthias Gutjahr