Author(s):	James Nugent
Location	Mezzanine
Date	apr Mon 13	Days Raw Files
Start	16:50	First Raw Start	error-in-template
Duration	00:30:00	Offset	None
End	17:20	Last Raw End
Chapters
Total cuts_time	None min.

http://lanyrd.com/2015/dotnetfringe/sdkttq/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Investigating_the_productionreadiness_of_Mono_via_Event_Store.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Event Store is an ACID-compliant stream database with just 24 bytes of mutable state. It is also open source on GitHub and largely written in C#, making it an excellent code base to start investigating database internals. On top of that, it was built for Mono on Linux first and foremost, with Windows and .NET support added on later. In this session we'll look at SEDA architecture of Event Store, from the client protocol down to the storage engine and replication model, we'll discuss some of the hard decisions and why we made them, and some of the tradeoffs which must be considered when building big systems on a managed platform. We'll also cover some of the "gotchas" in working with Mono on a large scale system, and show why 99% of your .NET server apps should actually be deployed on top of Mono on Linux. markdown
Comment:	production notes