InfoQ Homepage Workflow / BPM Content on InfoQ
-
/articles/workflows-aws-step-functions/en/smallimage/building-workflows-with-AWS-step-functions-small-1661853537630.jpg)
Building Workflows with AWS Step Functions
AWS Step Functions use a state machine to represent the workflow. A workflow consists of a set of tasks, each of which represents a discrete activity to be performed. Each task is defined by a state of the state machine. In this article, we will learn about the main concepts of AWS Step Functions and apply those to build a workflow for a sample business process: Order Fulfillment.
-
/articles/feedback-loops-value-streams/en/smallimage/the-implication-of-feedback-loops-for-value-streams-small-1661774785949.jpg)
The Implication of Feedback Loops for Value Streams
Lead time and throughput are dynamic variables which impact flow in a value stream. Capacity, processing time and feedback loops (such as error conditions) have a significant impact on WIP and flow and need to be mapped and measured when building value stream maps.
-
/articles/workflow-pipelines-as-code/en/smallimage/logo-1657111983732.jpg)
How Development Teams Can Orchestrate Their Workflow with Pipelines as Code
Infrastructure as Code was just the beginning. Configuration as Code followed shortly after – again becoming extremely commonplace and enabling organisations to scale their engineering capacity by a number of times. And in order to continuously increase the value development teams generate, Pipelines as Code is the natural consequence.
-
/articles/waste-not-want-not/en/smallimage/waste-not-want-not-s-1562257732956.jpeg)
Waste Not, Want Not: A Simplified Value Stream Map for Uncovering Waste
This article describes a simplified form of Value Stream Maps that makes it easy to visualize bottlenecks and inefficient processes in the software delivery lifecycle. It focuses on the two forms of Lean waste defined as Inventory and Waiting.
-
/articles/many-flavors-low-code/en/smallimage/many-flavors-low-code-s-1555920596237.jpeg)
The Many Flavors of “Low-Code”
While the low-code hype often tells how "citizen developers" can create enterprise applications without the need to code, these platforms can serve an important role for professional developers.
-
/articles/monitor-workflow-collaborating-microservices/en/smallimage/secure-scalable-web-ecosystem-linkedin-s-1551190398162.jpeg)
Monitoring and Managing Workflows across Collaborating Microservices
This article argues that you need to balance orchestration and choreography in a microservices architecture in order to be able to understand, manage and change the system.
-
/articles/ballerina-integration-tutorial-part-2/en/smallimage/ballerina-part2-logo-small-1527788057440.jpg)
Ballerina Tutorial: A Programming Language for Integration
Ballerina is a new programming language and platform whose objective is to make it easy to create resilient services that integrate and orchestrate across distributed endpoints. Ballerina’s design principles focus on baking integration concepts into a language, including a network-aware type system, sequence diagrammatic syntax, concurrency workers, being “DevOps ready”, and environment awareness.
-
/articles/ballerina-microservices-language-part-1/en/smallimage/ballerina-1527427668312.jpeg)
Ballerina Microservices Programming Language: Introducing the Latest Release and "Ballerina Central"
The tutorial demonstrates Ballerina, a new programming language and platform whose objective is to make it easy to create resilient services that integrate and orchestrate across distributed endpoints. Ballerina uses compile time abstractions for distributed system primitives that enable the compiler to generate artifacts like API gateways for deployment to Docker and Kubernetes.
-
/articles/events-workflow-automation/en/smallimage/logo-events-1513675812085.jpeg)
Events, Flows and Long-Running Services: A Modern Approach to Workflow Automation
Recent discussions around the microservice architectural style has promoted the idea that “to effectively decouple your services you have to create an event-driven-architecture”. Although events can decrease coupling, we must avoid the mistakes of traditional SOA: centralised control should to be avoided, and workflow engines must be less painful to use and operate.
-
/articles/microservice-event-choreographies/en/smallimage/GettyImages-544982936 copy.jpg)
Know the Flow! Microservices and Event Choreographies
This article explores ways to implement services which are long running and stretch across the boundary of individual microservices using event based architectures.
-
/articles/agile2016-middle-management-kanban/en/smallimage/logo-agile.jpeg)
The Misaligned Middle and Getting off the Hamster Wheel Using Kanban
At the Agile 2016 conference, Dominica DeGrandis and Julia Wester of Leankit gave talks on helping middle managers adapt to change and how Kanban can be used to identify problems in workflows, which people need to address.
-
/articles/purpose-case-management/en/smallimage/Stonehenge N0.JPG)
Purpose Case Management
Article “Purpose Case Management” describes a Case Management method that overarches BPM and Adaptive Case Management. Author reviews several modern movements such as Unstructured BPM, Social BPM, Dynamic BPM, and ACM. The article concludes with a generic method that allows switching between BPM and ACM depending on which one of them is more efficient in an execution context at certain moment.