Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Section
bordertruefalse
Column
width12%15%
Include Page
SimpleMenu
SimpleMenuTUSCANY: Main MenuTUSCANY: Main Menu
Overview
Column
width88%
85%

Welcome to

the

Apache Tuscany

project! The Tuscany community is working to create a robust and easy to use infrastructure that simplifies the development of service-based application networks and addresses real business problems posed in SOA.

Tuscany is based on specifications defined by the Open SOA Collaboration:

Apache Tuscany simplifies the task of developing SOA solutions by providing a comprehensive infrastructure for SOA development and management that is based on Service Component Architecture (SCA)

defines technologies for creating services and assembling them into higher-order service networks. SCA provides a language-independent way to compose and deploy service networks. SCA also defines language-specific programming models for service authoring including Java, Spring, C++ , and PHP. There are currently Tuscany SCA runtimes written in Java and C++.
  • Service Data Object (SDO) provides a uniform interface for handling different forms of data, including XML documents, that can exist in a network of services and provides the mechanism for tracking changes. Apache Tuscany provides Java and C++ implementations for SDO.
  • Data Access Service (DAS) provides a simple SDO interface to relational databases. Apache Tuscany provides a Java implementation for DAS.
  • The above mentioned technologies provide a full infrastructure for developing and running SOA based applications. They are not dependent on one another and can be used independently.

    Please join us to create a simple, practical, extensible SOA infrastructure to address the problems that large-scale applications and service networks are faced with. We look forward to your participation.

    ...

    standard. With SCA as it's foundation, Tuscany offers solution developers the following advantages:

    • Provides a model for creating composite applications by defining the services in the fabric and their relationships with one another. The services can be implemented in any technology.
    • Enables service developers to create reusable services that only contain business logic. Protocols are pushed out of business logic and are handled through pluggable bindings. This lowers development cost.
    • Applications can easily adapt to infrastructure changes without recoding since protocols are handled via pluggable bindings and quality of services (transaction, security) are handled declaratively.
    • Existing applications can work with new SCA compositions. This allows for incremental growth towards a more flexible architecture, outsourcing or providing services to others.
    Include Page
    Home subpage
    Home subpage