Hi,

@Mari,

Great work with new diagram!

@Chamila,

I think you raised the concern since the Stratos manager is mentioned
separately. Thinking further, I feel like we should remove "Stratos
Manager" box here. It is better to have different conceptual functions in
separate boxes such as logging, artifact distribution, Rest API etc.
Having "Stratos Manager", alone, doesn't add any value to the diagram.

Or we should wrap Rest API and ADC in a box called Stratos Manager, and
have Stratos clients in a separate box. It would be fine to have ADC inside
Stratos Manager, since the coordination part happens at Stratos Manager,
and ADC carry "Coordinator" in it's name.

Thanks.

On Thu, May 7, 2015 at 8:06 PM, Chamila De Alwis <chami...@wso2.com> wrote:

> Hi Mary,
>
> This diagram looks great, however I'm not sure if Artifact Distribution
> Coordinator should be illustrated as a separate component. Functionality
> wise it's important however component wise it's divided among the Cartridge
> Agent and Stratos Manager.
>
> Devs, WDYT?
> On May 7, 2015 6:24 PM, "Mariangela Hills" <mariang...@wso2.com> wrote:
>
>> Hi All,
>>
>> The Stratos layered architecture diagram in [1] needs to be changed for
>> the Stratos 4.1.0 release. I have attached the draft of the new
>> architecture diagram that Lakmal came up with in an offline discussion.
>> Please let me know whether any further changes are needed.
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Architecture
>>
>>
>> Regards,
>> Mariangela
>>
>>
>>
>>
>> *--*
>> *Mariangela Hills*
>> PMC Member & Committer of Apache Stratos
>> Senior Technical Writer
>> WSO2, Inc.
>> lean.enterprise.middleware.
>> m: +94 773 500185
>> w: http://wso2.com
>> <http://wso2.com/events/>
>>
>


-- 
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

phone: +94773325954
email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146

Reply via email to