Business
Rogue Wave has identified a top-tier SOA capability that deeply exploits parallelism and virtualization
This could end up being a quick way to manage component heterogeneity and ushering it to services orchestration in a high-performance and transactional integrity mode that exploits the price-performance benefits of multi-core-enabled grids.
Rogue Wave Software is set to announce in April version 3.0 of its Hydra SOA framework, and in doing so has carved out a new top-end niche in SOA. I call it Transactional Integrity SOA (TIS) because of the high-performance character, transactional depth, and exploitation of parallelism and virtualization technologies.
I've followed Rouge Wave for some time and the ability to take the Service Component Architecture (SCA) into the role of coalescing Java and C++ components into the same service -- all tightly coupled -- is an important milestone for making SOA mission critical. That's especially true of the financial sector, which has been a early adopter and major investor in SOA. The implications of TIS also make sense for software as a service providers, telcos, travel, and healthcare enterprises and service providers.
Hydra at essence makes any component a service. By using a really cool GUI to allow for a manageable approach to highly complex flow design, with each service an icon in a dance of loops and splits, the needs of order and transactional integrity are met.
The Hydra 3.0 benefits of tightly coupled transactions and order integrity extend to the ability to scale massively, thanks to the use of grid benefits of managing threads in a multi-core environment within the server, obviating the need for developers to dig deeply into threading chores. Moreover, Hydra takes advantage of parallelism by coordinating work flows via its pipeline technology such that transactions can run in parallel but that the business requirements of the transactions' order is maintained. Very cool. This will be of great interest to those seeking (or being required to seek) the Straight Through Processing (STP) characteristics in the global financials arena.
So if Rogue Wave's Hydra can align Java and C++ (and others) components within a mission-critical services environment, why not bring C# and .NET components into the mix, too? I received a "no comment" but is seems quite doable. Ditto for mainframe logic and components. This could end up being a quick way to manage component heterogeneity and ushering it to services orchestration in a high-performance and transactional integrity mode that exploits the price-performance benefits of multi-core-enabled grids. Nice combo.
Full disclosure: Rogue Wave is not a client of Interarbor Solutions, though I am speaking at their Hydra 3.0 launch event in New York on April 19, based on my favorable impressions of the technical and business benefits of Hydra's approach.
I've followed Rouge Wave for some time and the ability to take the Service Component Architecture (SCA) into the role of coalescing Java and C++ components into the same service -- all tightly coupled -- is an important milestone for making SOA mission critical. That's especially true of the financial sector, which has been a early adopter and major investor in SOA. The implications of TIS also make sense for software as a service providers, telcos, travel, and healthcare enterprises and service providers.
Hydra at essence makes any component a service. By using a really cool GUI to allow for a manageable approach to highly complex flow design, with each service an icon in a dance of loops and splits, the needs of order and transactional integrity are met.
The Hydra 3.0 benefits of tightly coupled transactions and order integrity extend to the ability to scale massively, thanks to the use of grid benefits of managing threads in a multi-core environment within the server, obviating the need for developers to dig deeply into threading chores. Moreover, Hydra takes advantage of parallelism by coordinating work flows via its pipeline technology such that transactions can run in parallel but that the business requirements of the transactions' order is maintained. Very cool. This will be of great interest to those seeking (or being required to seek) the Straight Through Processing (STP) characteristics in the global financials arena.
So if Rogue Wave's Hydra can align Java and C++ (and others) components within a mission-critical services environment, why not bring C# and .NET components into the mix, too? I received a "no comment" but is seems quite doable. Ditto for mainframe logic and components. This could end up being a quick way to manage component heterogeneity and ushering it to services orchestration in a high-performance and transactional integrity mode that exploits the price-performance benefits of multi-core-enabled grids. Nice combo.
Full disclosure: Rogue Wave is not a client of Interarbor Solutions, though I am speaking at their Hydra 3.0 launch event in New York on April 19, based on my favorable impressions of the technical and business benefits of Hydra's approach.