Remove Analysis Remove DevOps Remove Microservices Remove SOA
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

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.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Heuristics for Identifying Service Boundaries

OpenCredo

I love the piece that Dan North wrote long ago in his post “Classic SOA” , explaining service concepts in the non-digital world. In IT we try to mimic such structures and came up with terms like Modules, SOA and Microservices. I recommend reading Martin Fowler’s definition of Microservices. Security Constraints (e.g.

SOA 40
article thumbnail

Egnyte Architecture: Lessons learned in building and scaling a multi petabyte content platform

High Scalability

SOA architecture based on REST APIs. Python used to power client-side code, certain microservices, migration scripts, internal scripts. Learn to keep one or two service templates to implement microservices and don’t go wild on using different tech stack for each service. Apache FTP server. Native Android and iOS apps.