Wednesday, August 30, 2006 has organized an International Event in collaboration with the OMG®.

The web site has just been published:

It is the first event in Italy on Model Driven Architecture (MDA) realized in collaboration with Object Management Group (OMGTM). The event, organized by, OMG Member and MDA Qualified Service Provider (QSP), aims at promoting the MDA approach through a tutorial, some speeches taken by international experts and an expo area.

MDA provides a non proprietary and open approach to challenge the business and technology changes that has been extensively used in the DBE project and it is one of its technical founding principles.

Registry & Scale free networks

Registry as implemented in current SOA architectures does not scale up in EOA.
Services or Event registries are strategic elements for SOA. Even tough information and services are theoretically always active and available, if it is not known their network location, they get often fully lost.

Taking into consideration such as criticality of registry in SOA, OASIS in UDDI version 3 has introduced replication policies on cluster that allow an higher degree of tolerance toward damages. Currently UDDI version 3 supports both clustering and mirroring of a main node. Replications are complete and for such a reason they have to be implemented into the intranet so as to avoid any network constraint. The strategy is a complete replication for failover where each node is a mirror of the master.

In EOA we have an international-wide federation of services where it is strongly suggested not to set up the registry in a single node, even if implemented as a cluster. Who will assume the responsibility of maintaining 24hrs. x7 days a system that if crashes will cause impossibility to access to the whole ecosystem? By persisting with the intention of reinforcing and consolidating the single central registry the result would be a sort of Fort Knox where also the network of services like the supply of electric energy should be redundant, replicated and should come from different power stations1. How would it be possible to guarantee service continuity in case of natural calamity?

Typical disaster recovery solutions lack of scalability if applied throughout the whole national territory: N^2resource should be employed where N stands for the number of place of failover and procedures of human intervention for network reconfiguration should be planned. An hierarchical structured network cannot easily get managed and balanced by an administrator due to its numerous parameters which change very frequently.

The alternative solution proposed in the context of digital ecosystem registries is to exploit resources spread in the territory, getting an higher degree of tolerance against failure through a self-healing architecture (self-maintaining), replicated, redundant, with a scale free distribution rather than hierarchic, gaussian (random) distribution.

Ecosystem Oriented Architecture (EOA)

SOA has been designed and envisioned for being applied inside an Enterprise as a means to bridge systems and to create a governance layer on top of existing platforms as either legacy or assets. Inside Enterprises there is administration ability of the SOA infrastructure, ability to handle the network and having control over IT resources and IP: everything is reasonably under control.

Between enterprise, in a B2B environment that implements a value chain, SOA still scale up even if with some differences related to a more extend functional model and some negotiation ability.

In a Digital Ecosystems (DES) however, this is not true any more – IPs may change, protocols are subject to be replaced without notice, UDDI needs to be shared among parties, UDDI becomes vital for indexing and discovering services, functional models need to change at a pace which is faster than any ability to maintains coherence and harmonization via a managed coordination process. DES need to support very loosely coupled communities which brings news challenges in SOA architecture, and dealing with this reality requires re-thinking the founding principles and technology of SOA.
EAO is the name for this novel approach to DES architectures. It is a conceptual framework, it represents a collection of best practices principles and patterns related to Ecosystem-aware decentralized computing and architectures.

Tuesday, August 08, 2006

DBE Bulletin Num.6 Jul 2006

Our newsletter, The DBE Bulletin (Num. 6, July 2006) is available for download as a pdf:
DBE Bulleting Num. 6

Saturday, August 05, 2006

Calendar Demo with Semantics

Link to the Video

(Please use full screen playback or 1024x800 minimum)

The next (video) demo extends the previous SugarCRM&OpenLaszlo calendar integration and enhances it with simple semantics to create a search&discovery scenario.

During the demo, a calendar service made "searchable/findable" via the added semantics using BML and BML data.

The BML model has for example very simple attributes such as object (i.e. “Calendar”), action (i.e. “Get”) and name (i.e. my name), which uniquely identifies the service and owner of the calendar. The data associated to the model is entered on a separate editor (see video, BMLData Editor)

Once the calendar service and the semantics are deployed on the DBE, then the service can be discovered via the DBE Service Discovery Portal:

Then the different Calendar services available are ranked according to the search terms. The service integrates a Calendar service from SugarCRM, pulls the data via WebServices (WS) and refactors the data and displays it on a OpenLaszlo calendar. Potentially this scenario could be extended to integrate truly P2P calendars (currently is not!) and aggregation of different users calendars.

Link to the Video

OpenSource Tools/Services used for this demo:

Wednesday, August 02, 2006

The Zen of OpenSource

source: Sun Microsystems

On this article, Simon Phipps from Sun microsystems presents "The Zen of OpenSource" or what is good about OpenSource, why it makes economical sense, some insights into the OpenSource Commons (is it the source code? is it the community?, is the the free as in speech? and many more ideas. Read more at:

We had the pleasure to attend one one of the Simon's presentation at LugRadioLive'06:

You can also catch Simon on this podcast from

"The Zen of Free":