SCA allows you to define an application without knowing where things are
There is a difference between this kind of abstraction and cloud
elasticity when could allows for multiple copies of a component to be
deployed
Stateless components and elasticity
Just moving component is not so hard as our 2.x registry is already
able to raise events on this basis
Would have to update our infrastructure to take account of multiple
deployments of the same component/service
Binding.sca
Could we add some level of scheduling for load balancing purposes
Scheduling to different instances of component running on
different nodes and coming/going
Yahoo have messaging which is offered as a service
There was a feeling in the room that cloud integration should be
hidden by Tuscany infrastructure as far as possible.
Interesting questions about things like data which are in the app space
Have cloud envs to date done a good job at this?
Ran out of time.
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
