Archives
-
The Shift: how Orchard painlessly shifted to document storage, and how it’ll affect you
We’ve known it all along. The storage for Orchard
content items would be much more efficient using a
document database
than a
relational one. Orchard content items are composed of parts that
serialize naturally into
infoset
kinds of documents. Storing them as relational data like
we’ve done so far was unnatural and requires the data
for a single item to span multiple tables, related
through 1-1 relationships. This means lots of joins in
queries, and a great potential for
Select N+1 problems.
-
Video: Orchard’s best kept recipes
In this talk that I gave last June for Orchard Harvest in Amsterdam, I showed, in no particular order, my favorite Orchard features, tricks, and modules. Don’t expect a narrative in there, cause there isn’t one, but I’m hoping you’ll learn a thing or two.