Browse Prior Art Database

Utilising policy to dynamically configure conditions under which to cloud burst message processing in and ESB based on message properties

IP.com Disclosure Number: IPCOM000244382D
Publication Date: 2015-Dec-08
Document File: 1 page(s) / 40K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article describes applying a policy to a server / message flow / application node specifying the conditions under which off-load to a cloud environment (cloudbursting) should occur based on system metrics (ie. cpu, memory) and message properties (ie. priority, payload size, XPath evaluation).

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 1

Utilising policy to dynamically configure conditions under which to cloud burst message processing in and ESB based on message properties

While processing messages in an ESB system it is possible to cloudburst processing to enable faster throughput / handle higher workloads at certain checkpoints through the flow. But sending a message to a remote cloud server for processing can be slow and so this may not be desirable for high priority messages

which may be able to be processed faster by remaining within the current flow being

run on the bare metal on site.

    For example, by setting a policy of any message with priority in the range 3-10 being sent to the cloud this will enable your higher priority 1-2 messages to be processed very quickly on site.

Current technologies enable applying policies at a flow and node level. Here

we would have a policy which can be changed at run-time to determine whether to cloudburst depending on the message properties. The message property indicating message priority will be used below by means of an example.

    During message processing on-premise the system will be monitored to determine if it is becoming constrained (ie. approaching CPU saturation) to determine whether workload needs to be off-loaded to a cloud environment. Certain application logic (ie. a particular sub-flow, database access) will need to be

processed on-premise within a message flow as it may be working on secure data, however, other application logic may be suitable to be processed in a public cloud environment. When a message is being processed and enters a section of application logic that is suitable for cloud-bursting then if the on-premise...