Home
Embark is about starting a new adventure, a clean slate. It's intended to help you to defer the plumbing or commitment of choosing a specific database technology. DB agnostic architecture keeps data storage a tool, instead of a constraint.
The idea is that you use something quick and practical to persist data, preferably behind some abstraction layer like a repository or data provider. When the time comes that you confirm and measure which DB is the best fit for the problem, or need to use a more extensive DB in a live environment for security, scaling or other reasons, then the switch to that DB should only take 2-3 days. I've done this, so has Uncle Bob.
You should be able to do any queries, with a little creativity and not worrying too much about GetAll() operations.
If there is anything lacking about Embark to make it usable and fast enough while prototyping - please tweet @ubrgw or email [email protected] with any thoughts, or better yet, pull requests ;)
-
Collections
- Storage details about the POCO, DTO or primitive values you store
-
DocumentWrappers
- How items are returned, and embark doesn't force convertions on your entities
-
SQL Equivalents
- Example of how queries in sql could translate to embark
-
Server
- Info about WCF permissions and why OWIN/Katana isn't used
