Remove DevOps Remove Microservices Remove SOA Remove Team Building
article thumbnail

From Project to Program: Scaling Camunda Adoption in Your Company

Bernd Rucker

As part of this project they: evaluated a workflow tool, modeled the workflow, implemented the whole workflow solution, integrated it with their existing user interface, integrated it with their existing SOA infrastructure, exported relevant data into their data warehouse And set it live and operated it. Which brings us to microservices.

article thumbnail

Why Microservice Architecture Is More Than A Fad

taos

Eventually, there was SOA, and CORBA reared its head like a dyslexic snake. And now we have the so-called fad that is Microservice Architecture. The New Era The promised benefits of efficiency and interoperability from SOA/CORBA are still very much desired. Let’s explore these. S**t happens. Get over it!

article thumbnail

Architecture options to run a workflow engine

Bernd Rucker

These are valid questions which recently we get asked a lot, especially in the context of microservices , modern SOA initiatives or domain-driven design. Isolation/DevOps : The local operating tool ( Cockpit when using Camunda) is 100% focused on the workflows the DevOps team is really responsible for.