Introducing liveDB, a native .NET in-memory database engine that provides ACID support and allows for any data representation. It focuses on using memory over disk for faster performance and represents an alternative to relational databases by supporting non-SQL data structures and large scale databases. The document demonstrates liveDB by coding a simple model, running commands and queries against an in-memory instance, and highlighting benefits like reduced development time and no need for object-relational mapping. Potential drawbacks include data size limitations and lack of indexing, but it represents a option for memory-focused applications.

1. Introducing liveDBBuild faster systems fasterRobert Friberg, robert@devrex.seTwitter: @robertfriberg, @livedomain, #livedbhttp://livedb.devrex.se/

2. Disk.NET Process MemoryCommandserializationEngineClientsClientTransaction LogClientPass queries andcommandsSnapshot.0Synchronized executionSnapshot.1In-memoryObjectModelPrevalent System ArchitectureSnapshot.N

3. The prevalent hypothesisYour data will fit in available RAM99% of all OLTP database are 1TB or less--Stonebraker, VoltDB

4. Eric Schmidt, Google CEOAt Google we found it costs less money and it is more efficient to use DRAM as storage as opposed to hard disks.Three minutes with Google's Eric Schmidt , CNN.COM

5. What is liveDB?A native .NET in-memory database engineFull ACID supportEmbedded engine free to use for any purposeSupports any data representation

6. The NoSQL revolutionRDBMS paradigm is shakingAlternative data representation, document, graph, key/value, etcSupport large scale databasesLiveDB focuses onMemory vs. DiskFreedom of representationFacebook is not the common case

7. Relational Database PrisonRelational model formulated 1969Designed to address limitations non-existent today – disk accessA relational model is just one of many possible datarepresentationsPrimitive stored procedure languageO/R Mapping adds to the pain

8. O/R mapping vs Command/Query patternO/R mapping is based on CRUD patternCRUD is a specialization of Request/responseCommand/Query is more general (superset)You can do CRUD with Command/Query but not the other way around

9. Business argumentsReduced time to marketLower TCO for software systemsReduced development time up to 40%Operations (no rdbms)Licensing (no rdbms)Faster systems

10. Developer benefitsModel is pure .NET types and collectionsrepresentational freedomDAL and downwards is eliminatedNo object/relational mappingNo relational modelingNo T-SQL programmingDebuggingVersion controlSupports DDD, TDD

11. Simple API

12. Start your engines!var db = Engine.Load<MyModel>(path);db.Execute(command);var c = db.Execute(m => m.Customers.GetById(42));...var cmd = SetPasswordCommand(c.Id, newPassword);db.Execute(cmd);db.Close();

13. Demo!http://roxsux.devrex.se/Coding a simple modelCommands and queriesHosting the engineSee blog for more info: http://livedb.devrex.se/

14. DrawbacksModel must fit in RAMLoad time (start up and rollback)Versioning issues.NET Only (Json possible)No magical indexing (yet)

15. GotchasNo external dependencies from commandsDon’t modify the model with queryRollback is expensiveDon’t manipulate model out of contextDont rely on reference equalityResults are not direct references

16. ReferencesPrevalent System Architectureprevayler.org, java project from 2003, alive and kickingBamboo.Prevalence .NET 1.1, dead project?VoltDB

17. Thank you!Robert Friberg, DevrexTwitter: @robertfriberg, @livedomain, #livedbhttp://livedb.devrex.se/