Scalability

[Juan Padilla Julian <jt...@gmail.com>]

Hi,

I have an Etch based product and i'm really surprised with the good results
that i'm obtaining. I think that was a great decision to chose Etch instead
of other technologies such as WS, RMI, R-OSGI, etc.

Unfortunately, i'm facing with a problem of scalability.

My product is a server deployed over an Equinox OSGI engine, and i'm using
Etch as a way to connect clients to the implemented services.

OSGI allows me to dynamically assembly my components, but to expose Etch
connectivity i need to use mixins each time that i have to design a new
gateway, to join all the sub-services of my different componentes into a
general service.

I have to use prefixes for all elements (methods, types, etc) of each
sub-service to avoid collisions in the general service.

I must also manage the possibility that a sub-service is not available,
because the corresponding bundle is not installed (with a
prefixUnavailableSystem in each method).

I have to design an authentication system for each sub-service and join them
all internally in a single implementation.

I have seen now in the roadmap that there's a new proposal called "Etch
Cloud Services" (Name service, URI and Router).

Can my scalability problems be solved by this new services?

When are they planned to be available for a production environment?

I take this opportunity to congratulate the Etch team for their excellent
work

Re: Scalability

[Juan Padilla Julian <jt...@gmail.com>]

Ok, thanks.
I will try

On Sat, Mar 7, 2009 at 4:20 PM, scott comer <we...@mac.com> wrote:

> hi juan,
>
> our plan is to release initial versions of these components by mid summer,
> in etch release 1.2. the component you need is Router. you still have to
> prevent name collisions of mixed in components in your clients.
>
> if you have some spare cycles we could use some help. you could download
> and build the version of etch with the router in it and try it out sooner,
> help us shake it out. i don't think it is quite ready now, but in a week or
> two it could be.
>
> scott out
>
>
> Juan Padilla Julian wrote:
>
>> Hi,
>>
>> I have an Etch based product and i'm really surprised with the good
>> results that i'm obtaining. I think that was a great decision to chose Etch
>> instead of other technologies such as WS, RMI, R-OSGI, etc.
>>
>> Unfortunately, i'm facing with a problem of scalability.
>>
>> My product is a server deployed over an Equinox OSGI engine, and i'm using
>> Etch as a way to connect clients to the implemented services.
>>
>> OSGI allows me to dynamically assembly my components, but to expose Etch
>> connectivity i need to use mixins each time that i have to design a new
>> gateway, to join all the sub-services of my different componentes into a
>> general service.
>>
>> I have to use prefixes for all elements (methods, types, etc) of each
>> sub-service to avoid collisions in the general service.
>>
>> I must also manage the possibility that a sub-service is not available,
>> because the corresponding bundle is not installed (with a
>> prefixUnavailableSystem in each method).
>>
>> I have to design an authentication system for each sub-service and join
>> them all internally in a single implementation.
>>
>> I have seen now in the roadmap that there's a new proposal called "Etch
>> Cloud Services" (Name service, URI and Router).
>>
>> Can my scalability problems be solved by this new services?
>>
>> When are they planned to be available for a production environment?
>>
>> I take this opportunity to congratulate the Etch team for their excellent
>> work
>>
>>
>

Re: Scalability

[scott comer <we...@mac.com>]

hi juan,

our plan is to release initial versions of these components by mid 
summer, in etch release 1.2. the component you need is Router. you still 
have to prevent name collisions of mixed in components in your clients.

if you have some spare cycles we could use some help. you could download 
and build the version of etch with the router in it and try it out 
sooner, help us shake it out. i don't think it is quite ready now, but 
in a week or two it could be.

scott out

Juan Padilla Julian wrote:
> Hi,
>
> I have an Etch based product and i'm really surprised with the good 
> results that i'm obtaining. I think that was a great decision to chose 
> Etch instead of other technologies such as WS, RMI, R-OSGI, etc.
>
> Unfortunately, i'm facing with a problem of scalability.
>
> My product is a server deployed over an Equinox OSGI engine, and i'm 
> using Etch as a way to connect clients to the implemented services.
>
> OSGI allows me to dynamically assembly my components, but to expose 
> Etch connectivity i need to use mixins each time that i have to design 
> a new gateway, to join all the sub-services of my different 
> componentes into a general service.
>
> I have to use prefixes for all elements (methods, types, etc) of each 
> sub-service to avoid collisions in the general service.
>
> I must also manage the possibility that a sub-service is not 
> available, because the corresponding bundle is not installed (with a 
> prefixUnavailableSystem in each method).
>
> I have to design an authentication system for each sub-service and 
> join them all internally in a single implementation.
>
> I have seen now in the roadmap that there's a new proposal called 
> "Etch Cloud Services" (Name service, URI and Router).
>
> Can my scalability problems be solved by this new services?
>
> When are they planned to be available for a production environment?
>
> I take this opportunity to congratulate the Etch team for their 
> excellent work
>