Tracking change and innovation in the enterprise software development community
IBM WebSphere
Virtualize apps
to lower costs,
Increase agility
Learn more!
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
Create REST
-enabled Web Apps
with Project Zero
from IBM.
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
Posted by Jean-Jacques Dubray on Jul 30, 2007 11:57 PM
The WSO2 ESB is an Open Source project (under the Apache license) based upon the Apache Synapse project. A detailed description of its capabilities can be found here. In addition to providing a full web service support, WSO2 ESB offers a complete scripting environment:
The WSO2 ESB can be extended using simple Java, JavaScript, Ruby or other scripting languages. In addition there is support for using the Spring Framework to configure the mediation flow.
Last June the first performance report focused on load testing. In this new report, Asankha Perera, Architect at WSO2, focuses on the typical usage scenarios of an ESB:
I encourage you to take a look at the reports, they provide a good data point on the current capabilities of ESBs. Asankha does point out that a comparison between ESBs is:
... made harder by the lack on any industry standard benchmark for ESBs (let alone a standard definition of an ESB)
If a standard definition itself might be something people disagree on, the capabilities provided by ESBs, the usage patterns, and to a certain extend the architecture of ESBs, are becoming fairly standard across the industry. Today, the ESB concept has evolved to become a service container that exposes standard-based web service endpoints from existing web service or non web service endpoints mediated at the transport, protocol, endpoint, interface and content level. The interactions between two end points hosted in the same container are usually optimized. A modern Service Oriented Architecture can be implemented with several types of service containers, sometimes nested, with each container offering specific quality of service, scripting capabilities, legacy integration, price ...
Scaling a Massively Multi-player Server Casestudy: Terracotta on SmartFoxServer
Hibernate without Database Bottlenecks
Scale Your Application without Punishing Your Database
Why Should I Care About Terracotta?
Terracotta 2.6 - Download now for scalability without tradeoffs
Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.
In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.
In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.
It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.
In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.
In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.
Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.
Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.
1 comment
Reply