With the Cloud Service Broker, Vordel pledges to bring trust and reliability to Cloud Computing
So what does this mean?
The solution aggregates multi-domain services across their enterprise, partners and 3rd party cloud services such as Amazon EC2 and Google Apps
Through bringing the services together, the Broker enables organisations to consistently define and manage policy across these services and report on them
Through the Broker, composite applications can be built seamless while offering full visibility, trust and control".
So why do we need this?
Organizations using Cloud services in conjunction with their own on-premises SOA face major issues related to reliability and trustworthiness.
Very difficult to bring together services from across domains (i.e. on-premises, Public and Private Clouds, and B2B) into coherent composite services and applying policies to them.
Vordel CEO, Vic Morris, said "Many organizations see the value of incorporating Cloud Services into their IT infrastructure, but they also have concerns about the reliability and performance of these services outside their domain of control. The Vordel Cloud Service Broker addresses these issues by providing a trustworthy “
So how does it work?
The Broker solves this problem by registering services from all three domains into a single repository, enabling monitoring, management and policy enforcement.
Plus the Vordel Cloud Service Broker offers value added services like caching, acceleration, and transformation, delivering enterprises savings in time and money.
What is under the covers?
Multi-Domain Registry Repository (MDRR) – This is where the Broker registers aggregated services across domains. This one-stop-shopping for compliance to Service Level Agreements, privacy and security mandates.
Analytics – Providing the visibility through an independent audit trail including raw usage information, service quality, patterns of usage over time, and identity of users.
Content Analysis – Content is analyzed to enable Data Loss Prevention (DLP), content-level threats, and application-level attacks at the API and payload level.
Caching – Protecting against latency from the Cloud service, saving money by allowing some requests to be serviced by the broker itself.
Composition – Allowing developers to link together local apps with Cloud-hosted apps via Web Services interfaces, database, or message schemes like MQ or JMS.
Content transformation – Accelerated transformation for mediation between different applications or between REST API interfaces and SOAP, JMS, COBOL, etc.
SLA Monitoring - Comprehensive monitoring of response time of Cloud services, and the entire transaction throughput time.
Traffic Throttling – Vordel refers to this as the “surge protector”, protecting against apps making a high number of calls to a Cloud service by deflecting a portion to a back-up service, newly provisioned for this purpose.
Event Alerting – Notification of events like Cloud outages so that remedial measures can be put into place.
Extensibility to 3rd Party Valued Added Services – Traditionally very difficult/costly with non standard API's from competing solutions, but is made easy & pluggable here.
For more information:
View the PDF