So the focus of this talk is about how do you re-architect your software to take advantage of the advances of software today. Many developers treats the serialization of objects as sort of a separate process something that hangs off the side where the object is out of flat file or disk. But now if your object lives in persistent memory how do you manage that? How do you update that in a consistent way so it's you know it's just constant even through power failures and so on. So most of the focus is on talking about how we write our software in the future when our DRAM is persistent.

So I'm going to sort of start by talking about general principles. C had sort of an object layout in memory and if the the memory was persistent, how would you manipulate that in a failure atomically? What does it means if I'm inserting a node of a red/black tree and now pull power in between, how do I ensure I haven’t destroyed the black tree. So this has been tackled in the file system and database world. But I'm talking about a general principle that we're tackling this with non-volatile memory and I'm sort of going to move on to saying in a practical sense if you’re writing code today, what are the libraries available to let you do this in a more high level maybe having to take up all those details yourself.