I've always gone with the rule of 1 Broker per website, the main reasons being for most efficient CCS, cleaner deploying set up, separation of concerns if one 'goes down' etc
We have a new implementation and 3 main websites, where all content is being published to the DB using the DD4T framework.
A new requirement is that the websites will need to use content and component links from each others publications. The team here is going with the rule 'we'll put all sites in the same broker db'
I don't like this idea, but the content was originally not intended to be shared across the multiple sites and the mvc views are not stored in a correct structure to allow easy consumption from the other site so to do this 'my way' would require some extensive last minute development.
The 'my way' solution would be to have the content stored in separate broker database and:
- Use odata to pull the content we need from each others site
- Write our own logic where we need to pull specific content
I wanted to open this scenario up to the community to see what people's thoughts are, if anyone has encountered a similar situation, or worse gone down the route of a 'single' broker and what issues they have ran into further down the line, what has been done to ensure performance, uptime and is not an issue.