[chef] Re: Re: Re: How to split up chef stack?

[KC Braunschweig < >]

On Fri, Oct 5, 2012 at 1:51 PM, Brian Hatfield 
<
 >
 wrote:
> Assuming my architecture looks like:
>
> chef-api-01 + chef-api-02
>
> both pointing to
>
> chef-couchdb-01
>
> Does rabbit/solr/expander need to be on the couch server, so things are
> consistent, or should they be on each api server? Or should there be some
> other division?

You haven't specified what your goals for this are (redundancy, scale,
a specific bottleneck, etc) but I'd say keep it simple and put
everything on a single backend except the api layer. If you have
bottlenecks after that, you can do more.