reklama - zainteresowany?

Practical Process Automation - Helion

Practical Process Automation
ebook
Autor: Bernd Ruecker
ISBN: 9781492061403
stron: 294, Format: ebook
Data wydania: 2021-03-16
Księgarnia: Helion

Cena książki: 186,15 zł (poprzednio: 216,45 zł)
Oszczędzasz: 14% (-30,30 zł)

Dodaj do koszyka Practical Process Automation

In todayâ??s IT architectures, microservices and serverless functions play increasingly important roles in process automation. But how do you create meaningful, comprehensive, and connected business solutions when the individual components are decoupled and independent by design? Targeted at developers and architects, this book presents a framework through examples, practical advice, and use cases to help you design and automate complex processes.

As systems are more distributed, asynchronous, and reactive, process automation requires state handling to deal with long-running interactions. Author Bernd Ruecker demonstrates how to leverage process automation technology like workflow engines to orchestrate software, humans, decisions, or bots.

  • Learn how modern process automation compares to business process management, service-oriented architecture, batch processing, event streaming, and data pipeline solutions
  • Understand how to use workflow engines and executable process models with BPMN
  • Understand the difference between orchestration and choreography and how to balance both

Dodaj do koszyka Practical Process Automation

 

Osoby które kupowały "Practical Process Automation", wybierały także:

  • Windows Media Center. Domowe centrum rozrywki
  • Ruby on Rails. Ćwiczenia
  • DevOps w praktyce. Kurs video. Jenkins, Ansible, Terraform i Docker
  • Przywództwo w Å›wiecie VUCA. Jak być skutecznym liderem w niepewnym Å›rodowisku
  • Scrum. O zwinnym zarzÄ…dzaniu projektami. Wydanie II rozszerzone

Dodaj do koszyka Practical Process Automation

Spis treści

Practical Process Automation eBook -- spis treści

  • Preface
    • Process Automation Tools and Techniques
    • The Scope of This Book
    • Who This Book Is For
    • The Architect Always Implements
    • Accompanying Website and Code Examples
    • Feedback
    • How to Read This Book
    • Conventions Used in This Book
    • OReilly Online Learning
    • How to Contact Us
    • Acknowledgments
  • 1. Introduction
    • Process Automation
    • Wild West Integrations
    • Workflow Engines and Executable Process Models
    • A Business Scenario
    • Long-Running Processes
    • Business Processes, Integration Processes, and Workflows
    • BusinessIT Collaboration
    • Business Drivers and the Value of Process Automation
    • Not Your Parents Process Automation Tools
      • A Brief History of Process Automation
        • BPM in the ivory tower
        • Centralized SOA and the ESB
        • Misguided BPM suites
        • The limitations of low code
        • Moving past old-school BPM suites
      • The Story of Camunda
    • Conclusion
  • I. Fundamentals
  • 2. Workflow Engines and Process Solutions
    • The Workflow Engine
      • Core Capabilities
      • Additional Features of Workflow Platforms
      • Architecture
    • A Process Solution
    • An Executable Example
    • Applications, Processes, and Workflow Engines
    • Typical Workflow Tools in a Projects Life Cycle
      • Graphical Process Modeler
      • Collaboration Tools
      • Operations Tooling
      • Tasklist Applications
      • Business Monitoring and Reporting
    • Conclusion
  • 3. Developing Process Solutions
    • Business Process Model and Notation (BPMN)
      • Start and End Events
      • The Token Concept: Implementing Control Flow
      • Sequence Flows: Controlling the Flow of Execution
      • Tasks: Units of Work
      • Gateways: Steering Flow
      • Events: Waiting for Something to Happen
      • Message Events: Waiting for a Trigger from the Outside
    • Combining Process Models and Programming Code
      • Publish/Subscribe to a Process
      • Referencing Code in Process Models
      • Using Prebuilt Connectors
      • Model or Code?
        • Where do you need to (potentially) wait?
        • What do you discuss regularly with other stakeholders?
        • What crosses boundaries?
        • Example
    • Testing Processes
    • Versioning of Process Solutions
      • Running Versions in Parallel
        • Migrating process instances to the new version
        • Versioning glue code and data definitions
    • Conclusion
  • 4. Orchestrate Anything
    • Orchestrate Software
      • Service-Oriented Architecture (SOA) Services
      • Microservices
      • Serverless Functions
      • Modular Monoliths
      • Deconstructing the Monolith
    • Orchestrate Decisions
      • Decision Model and Notation (DMN)
      • Decisions in a Process Model
    • Orchestrate Humans
      • Task Assignment
      • Additional Tool Support
      • The User Interface of User Tasks
        • Using an external tasklist application
        • Building a customized tasklist application
    • Orchestrate RPA Bots
    • Orchestrate Physical Devices and Things
    • Conclusion
  • 5. Championing Workflow Engines and BPMN
    • Limitations of Other Implementation Options
      • Hardcoded Processes
      • Batch Processing
      • Data Pipelines and Streaming
      • The Actor Model
      • Stateful Functions
    • Process Modeling Languages
      • Workflow Patterns
      • Benefits of Graphical Process Visualizations
      • Textual Process Modeling Approaches
      • Typical Concerns About Graphical Modeling
      • Graphical Versus Textual Approaches
    • Process Automation with Blockchain?
    • Conclusion
  • II. Process Automation in the Enterprise
  • 6. Solution Architecture
    • When to Use a Workflow Engine
    • Architecture Trade-Offs
      • Running the Workflow Engine
      • Decentralized Engines
      • Sharing Engines
      • Ownership of Process Models
      • Using the Workflow Engine as a Communication Channel
      • In-House Workflow Platforms
      • Performance and Scalability
      • Developer Experience and Continuous Delivery
    • Evaluating Workflow Engines
    • Conclusion
  • 7. Autonomy, Boundaries, and Isolation
    • Strong Cohesion and Low Coupling
    • Domain-Driven Design, Bounded Contexts, and Services
    • Boundaries and Business Processes
      • Respect Boundaries and Avoid Process Monoliths
      • Foster Your Understanding of Responsibilities
      • Long-Running Behavior Helps You Defend Boundaries
    • How Processes Communicate Across Boundaries
      • Call Activities: Handy Shortcuts Only Within the Boundary
      • Crossing Boundaries Is an API Call
    • Decentralized Workflow Tooling
    • Conclusion
  • 8. Balancing Orchestration and Choreography
    • Event-Driven Systems
      • Emergent Behavior
      • Event Chains
        • Changing the chain affects multiple components
        • Lack of visibility
      • The Risk of Distributed Monoliths
    • Contrasting Orchestration and Choreography
      • Introducing Commands
      • Messages, Events, and Commands
      • Terminology and Definitions
      • Avoiding Event Chains by Using Commands
      • The Direction of Dependency
    • Finding the Right Balance
      • Deciding Whether to Use Commands or Events
      • Mixing Commands and Events
      • Designing Responsibilities
      • Evaluating Change Scenarios to Validate Decisions
    • Debunking Common Myths
      • Commands Do Not Require Synchronous Communication
      • Orchestration Does Not Need to Be Central
      • Choreography Does Not Automatically Lead to More Decoupling
    • The Role of Workflow Engines
    • Conclusion
  • 9. Workflow Engines and Integration Challenges
    • Communication Patterns for Service Invocation
      • Synchronous Request/Response
      • Asynchronous Request/Response
      • BPMN and Being Ready to Receive
      • Aggregating Messages
      • Poisoned and Dead Messages
      • Synchronous Facades Hiding Asynchronous Communication
    • Transactions and Consistency
      • Eventual Consistency
      • Business Strategies to Handle Inconsistency
        • Ignore the inconsistency
        • Apologize
        • Resolve the inconsistency
      • The Saga Pattern and Compensation
      • Chaining Resources by Using the Outbox Pattern
    • Eventual Consistency Applies to Every Form of Remote Communication
    • The Importance of Idempotency
    • Conclusion
  • 10. BusinessIT Collaboration
    • A Typical Project
      • The Moral of the Story
    • Including All the People: BizDevOps
      • Development
      • Business
      • Operations
    • The Power of One Joined Model
      • From a Process Pyramid to a House
    • Who Does the Modeling?
    • Creating Better Process Models
      • Extracting (Integration) Logic into Subprocesses
      • Distinguishing Between Results, Exceptions, and Errors
      • Increasing Readability
        • Labeling elements
        • Model from left to right and emphasize the happy path
    • Conclusion
  • 11. Process Visibility
    • The Value of Process Visibility
    • Getting the Data
      • Leverage Audit Data from Your Workflow Engine
      • Model Events to Measure Key Performance Indicators
    • Status Inquiries
    • Understanding Processes That Span Multiple Systems
      • Observability and Distributed Tracing Tools
      • Custom Centralized Monitoring
      • Data Warehouses, Data Lakes, and Business Intelligence Tools
      • Process Mining
      • Process Event Monitoring
      • Current Market Dynamics
    • Setting Up Process Reporting and Monitoring
      • Typical Metrics and Reports
      • Allowing for a Deeper Understanding
    • Conclusion
  • III. Get Going!
  • 12. The Journey to Introduce Process Automation
    • Understanding the Adoption Journey
      • Failures You Want to Avoid
      • A Success Story
      • The Pattern of Successful Adoption Journeys
      • Different Journeys for Different Scenarios
        • Replacing existing workflow products
        • Introducing process automation in SOA environments
        • Introducing process automation in event-driven architectures
        • Strategic initiatives driving process automation
    • Starting Your Journey
      • Bottom-up Versus Top-down Adoption
      • Proofs of Concepts
      • Presenting the Business Case
      • Dont Build Your Own Platform
      • Dos and Donts Around Reuse
    • From Project to Program: Scaling Adoption
      • Perception Management: What Is Process Automation?
      • Establishing a Center of Excellence
      • Managing Architecture Decisions
      • Decentralized Workflow Tooling
      • Roles and Skill Development
    • Conclusion
  • 13. Parting Words
    • Current Architecture Trends Influence Process Automation
    • Rethinking Business Processes and the User Experience
    • Where to Go from Here
  • Index

Dodaj do koszyka Practical Process Automation

Code, Publish & WebDesing by CATALIST.com.pl



(c) 2005-2024 CATALIST agencja interaktywna, znaki firmowe należą do wydawnictwa Helion S.A.