Turmeric is a comprehensive, policy-driven SOA platform that you can use to develop, deploy, secure, run and monitor SOA services and consumers. It is a Java based platform, follows the standards (SOAP, XML, JSON, XACML, etc.), and supports WSDL (SOAP style - Doc Lit wrapped mode and REST style). It supports a variety of protocols and data formats. Eclipse plugins help with the development of services and consumers. Other important features include:
Various Quality of Service (QoS) features such as authentication, authorization, and rate limiting, which you control by defining respective policies.
A Repository Service that enables service registration and governance.
The Type Library, which provides the ability to define and manage reusable schema type definitions across services, and hierarchically organizes them.
The Error Library, another useful capability that lets you define and re-use error definitions across services.
Local binding, which lets you locally bind services to consumers as a deployment time option, for optimization, without loss of any generality or changing code.
The Turmeric platform is highly extensible and customizable. For example, you can easily plug in additional protocol processors, data formats, handlers and various other capabilities. The platform is also highly optimized for large scale environments. eBay uses this platform internally, and most parts of it are now open source, including replacing functionality dependent on commercial products with an equivalent, first-version, open-source implementation, and changing package names to match the open-source spirit. This is the first version of the open-source release of Turmeric, and might have some rough edges, so please provide feedback and contribute as you see fit. ·
UltraESB is the first [and still the only] Open Source Enterprise Service Bus (ESB) to utilize Zero-copy proxying with Memory Mapped files and Java Non-Blocking IO for extreme performance! ·
What CouchDB is
* A document database server, accessible via a RESTful JSON API.
* Ad-hoc and schema-free with a flat address space.
* Distributed, featuring robust, incremental replication with bi-directional conflict detection and management.
What it is Not
* A relational database.
* A replacement for relational databases.
* An object-oriented database. Or more specifically, meant to function as a seamless persistence layer for an OO programming language. ·