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

What is event processing?

Although event processing has been around for a while, it hasn't yet been used widely.

The goal of event-driven architectures is to process information in near real time by reacting to the publication of that information when it happens. Event-driven architectures lower the latency of information propagation while promoting loose coupling between components compared with sequential programming in traditional models.

Event-processing systems have several important fundamental aspects, some of which are as follows:

  • Push-based messaging pattern: As discussed before, the traditional messaging pattern has been request-response—what can be called a pull messaging pattern because the client pulls information from the server by sending a request. In contrast, in event-processing systems, the event producers push events into the system when they occur.
  • Autonomous messages: Events are signaled by notifications that are independent of other events (this doesn&apos...
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