Microservices and BPM

BPM
  • January 4, 2018
  • Scott
  • 0 Comments

If you were wondering whether microservices architecture was coming for BPM engines, this post makes it pretty clear that it is happening:

This new direction will give users the flexibility to open up the architecture, replace components as needed and to scale the engine and your applications independently. In combination with containerization (Docker), Microservice architectures with event-driven endpoints provide a cloud-native approach to deploy and interact with the engine in a distributed fashion.

And this is at least the third vendor that has made a similar announcement or direction toward a microservices or cloud-native architecture.  It just stands to reason that as the architecture of much of the software world is moving this way, that the technologies that BPM suites are composed of will be exposed as microservices or similar component technologies.

In general, across the clients we work with, more infrastructure is moving to microservices and Docker images.  There are simple tutorials like this one, and one of our consultants has been publishing a series of posts about Docker as well, starting with “What is Docker?”

“Over the last few weeks I’ve been helping a lot of people get started using Docker so I thought I would write up this blog series to help people get started using Docker. I will be writing a new blog each week to help readers get started with different docker topics starting with the basics, in this blog, all the way to advanced container scaling and more. So without further ado let’s jump right in!”

I recommend it – it’s a good read and a good introduction – combined with a very practical approach to tutorial.  Of note: even if you’re deploying many of your applications without microservices, microservices architecture can still be of use to you for new elements of your architecture.  In other words, this isn’t a fork in the road – you can leverage docker images and microservices in heterogeneous environments.

The cautionary note I’d add? Designing the right interfaces to microservices is non-trivial. It requires good judgment and design, it isn’t just a rote activity.  A poorly designed interface to your microservice is worse than not having microservices.  Make your investments in design and development of microservices accordingly!

 

 

 

 

 

 

Related Posts
  • May 9, 2018
  • Andrew
  • 0 Comments

BP3 now has a customer live with the next generation of task federation in IBM BPM. While the Brazos portal h...

  • May 3, 2018
  • Ariana
  • 1 Comments

RPA Business Use Cases from BP3. How do you identify where to use Robotic Process Automation (RPA) in you...

  • April 30, 2018
  • Scott
  • 0 Comments

Hybrid Cloud and On-Premise Software Complexity The end-users who leverage our software shouldn't have to k...