Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
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
Mastering jBPM 5

You're reading from   Mastering jBPM 5 Design, build, and deploy business process-centric applications using the cutting-edge jBPM technology stack

Arrow left icon
Product type Paperback
Published in Jun 2015
Publisher
ISBN-13 9781783289578
Length 326 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Simone Fiorini Simone Fiorini
Author Profile Icon Simone Fiorini
Simone Fiorini
Arun V Gopalakrishnan Arun V Gopalakrishnan
Author Profile Icon Arun V Gopalakrishnan
Arun V Gopalakrishnan
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Business Process Modeling – Bridging Business and Technology FREE CHAPTER 2. Building Your First BPM Application 3. Working with the Process Designer 4. Operation Management 5. BPMN Constructs 6. Core Architecture 7. Customizing and Extending jBPM 8. Integrating jBPM with Enterprise Architecture 9. jBPM in Production A. The Future B. jBPM BPMN Constructs Reference Index

Availability


The availability of an application or system can be viewed as the total amount of time that it provides its services against the total time it is expected to do so. System availability is affected by multiple factors ranging from failure of the system due to hardware/software failures and the known downtime for maintenance and upgrades.

High availability is achieved in applications by having failover mechanisms using which the system can get back to its service provisioning state after a failure. A more optimized system would consider backup mechanisms, which it can immediately switch on to in a failure scenario, thus improving the availability. Scheduled maintenance can be done using a rolling upgrade to ensure high availability. The solutions are usually depicted in the form of deployment architecture, vary according to the software solution, and consider the trade-offs in non-functional requirements.

The following figure depicts the sample deployment architecture that can 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