The trouble with business process modelling (BPM), or indeed any programmed flow, is that you need configuration to tell the program how to cope at key points of its execution.

Double Whammy

Reeling from the left-handed smash of producing the program, you’re hit with the right hook of custom configuration. Multiply that by a hundred and you’ve got configuration hell. Yet that situation is completely normal in any medium to large-sized business today.

Thus conduct risk increases rapidly with the size of the business, as new applications multiply.

Traditionally, we try to control this by completely separating infrastructure (such as networks) from the applications that run “on top” of them. Almost as if they have nothing to do with each other.

But the unstoppable wave of software-defined infrastructure means this won’t work for much longer.

Single Solution

Now, it’s true that you don’t have to change anything to use the SPARKL Sequencing Engine.

But we can’t deny that it introduces a brand new idea - a single abstraction that unifies infrastructure, services and process flows.

Handily, this can express pretty much anything.

From a router or firewall device configuration; through services on the Enterprise Service Bus or Internet of Things; to the event flow that drives distributed ledger updates - or makes your room lights dim when you start watching a movie.

Capabilities, resources and intent, all expressed in the exact same way. This is what enables the SPARKL Sequencing Engine not only to sequence events, but also to provision with reason as it goes.

This idea and its implementation is disruptive to anything that involves datacentres and applications. And, it promises an end to the double whammy of manual programming and custom configuration.

Photo courtesy of tumblr.com.