Today I would like to present to you a prototype I have been working over past couple of weeks. This solution is built around a story about language fallback requirements of a fictitious multinational company. This is just an example of how you can approach similar requirement.
There is a number of alternative solutions that the gurus from all over the world came up with, so you could naturally ask me: what is so special about this approach?
Well, here is a couple of things coming to my mind:
It is granular, field based solution.
It is consistent with the product architecture, relying on proven technologies such as Standard Values provider.
It is friendly to business users as they can clearly see what attributes falls back using familiar Content Editor UI.
This solution covers all major data access methods: direct API, Sitecore Query, Search via in-built Lucene engine.
I should mention, that Fast Query, is not respecting these settings, because this data access technology is simply not language aware. No language fallback solution that I’ve seen works with Fast Query.
It has minor impact on performance – I ran a few performance tests and confirmed it.
It is quite generic.
It is flexible.
It is plug and play.