openstack team mailing list archive
Mailing list archive
Re: Architecture for Shared Components
On Fri, Jul 30, 2010 at 4:23 PM, Michael Gundlach <
> service D # e.g. API endpoint
> => cache service
> service E # e.g. more specific endpoint, maybe cloud servers endpoint
> In my experience, drawing #2 is the best, and a huge reason is that I can
> actually explain to you what each service does. I can tell you what inputs
> he expects, what outputs he expects, and the one thing that he calculates --
> and you can just throw more instances of him in place to
s/what outputs he expects/what he outputs downstream and what he returns
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@xxxxxxxxxxxxx, and delete the original message.
Your cooperation is appreciated.