Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Design Principles for Process-driven Architectures Using Oracle BPM and SOA Suite 12c

You're reading from   Design Principles for Process-driven Architectures Using Oracle BPM and SOA Suite 12c A design handbook to orchestrate and manage flexible process-driven systems with Oracle BPM and SOA Suite 12c

Arrow left icon
Product type Paperback
Published in Jun 2015
Publisher
ISBN-13 9781849689441
Length 444 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (14) Chapters Close

Preface 1. Business Process Management, Service-oriented Architecture, and Enterprise Architecture FREE CHAPTER 2. Modeling Business Processes for SOA – Methodology 3. BPMN for Business Process Modeling 4. Process-driven Service Design 5. Composite Applications 6. Process Execution with BPMN and BPEL 7. Human Interaction with Business Processes 8. Business Rules 9. Adaptive Case Management 10. Mobile and Multichannel 11. Event Processing and BPM 12. Business Activity Monitoring Index

Best practice considerations – performance, extensibility, upgrade protection


Building task-driven applications is not easy as it can be seen from the sections within this chapter. As usual, the first steps are the most painful. Within this last section, some experiences from elementary implementation of best practices collected in real-world projects will be discussed, which can be used as hints for considerations about process and human task design when doing own implementations the first time.

General process design

How a process is designed is essential when building BPM applications. Ideally, a process's memory footprint is minimal to ensure platform stability and performance. This means that it carries as little business data as possible. In most cases, a technical identifier is suitable, which can be used to communicate with stateless service-evaluating process-flow-relevant data on demand. What applies to the processes applies to human tasks as well. The task payload should also be...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image