From everything I've read, Orchard makes it very easy to store information in its own database. But we need to integrate Orchard with a fairly complex pre-existing backend (consisting of a home-grown repository + EF + SQL Server).
This is a rather different scenario than the existing documentation and code samples presume, and I'm still wrapping my head around Orchard, so I could use a little guidance on best practices in this regard.
Should we just create a standard MVC app and ignore the Orchard plumbing entirely, other than decorating our controllers with a [Themed] attribute? I'm pretty sure I can make this work, but I suspect I'd be giving up some useful functionality - though I'm
not sure exactly what.
Should we use the Orchard plumbing as much as humanly possible, and only override the piece(s) that actually persist things to the database? (Not sure what pieces these are - for all its talk about simplicity, Orchard is astonishingly complex.)
Should we do something somewhere in-between?
I surely can't be the only person who's trying to do this. Are there any blog posts/code samples on best practices in this regard?