Book Image

JBoss: Developer's Guide

By : Elvadas Nono Woguia
Book Image

JBoss: Developer's Guide

By: Elvadas Nono Woguia

Overview of this book

Have you often wondered what is the best JBoss product to solve a specific problem? Do you want to get started with a specific JBoss product and know how to integrate different JBoss products in your IT Systems? Then this is the book for you. Through hands-on examples from the business world, this guide presents details on the major products and how you can build your own Enterprise services around the JBoss ecosystem. Starting with an introduction to the JBoss ecosystem, you will gradually move on to developing and deploying clustered application on JBoss Application Server, and setting up high availability using undertow or HA proxy loadbalancers. As you are moving to a micro service archicture, you will be taught how to package existing Java EE applications as micro service using Swarm or create your new micro services from scratch by coupling most popular Java EE frameworks like JPA, CDI with Undertow handlers. Next, you will install and configure JBoss Data grid in development and production environments, develop cache based applications and aggregate various data source in JBoss data virtualization. You will learn to build, deploy, and monitor integration scenarios using JBoss Fuse and run both producers/consumers applications relying on JBoss AMQ. Finally, you will learn to develop and run business workflows and make better decisions in your applications using Drools and Jboss BPM Suite Platform.
Table of Contents (10 chapters)

Developing virtual databases

The data virtualization journey comes down to developing a set of virtual databases and interconnecting them to client applications. In this section, we will cover both creation of and connection to a virtual database thrown from a practical business use case.

Business case

Client: Hello JBoss Doctor, regarding the Beosbank money transfer database, following connectivity issues from some countries, high loads, and various regulatory and business needs, we decided to have two separate databases for the EMEA regions. The beosbank-africa database is used for all our customers in Africa; this database runs on a cluster. MySQL is in South Africa and holds all the transactions sent from Africa....