You're reading from Hands-On Software Architecture with Java Learn key architectural techniques and strategies to design efficient and elegant Java applications

Product type Paperback

Published in Mar 2022

Publisher Packt

ISBN-13 9781800207301

Length 510 pages

Edition 1st Edition

Languages

Java

Tools

Java EE

Concepts

Software Architecture

Author (1):

Giuseppe Bonocore

View More author details

Table of Contents (20) Chapters

Preface

1. Section 1: Fundamentals of Software Architectures

2. Chapter 1: Designing Software Architectures in Java – Methods and Styles FREE CHAPTER

3. Chapter 2: Software Requirements – Collecting, Documenting, Managing

4. Chapter 3: Common Architecture Design Techniques

5. Chapter 4: Best Practices for Design and Development

6. Chapter 5: Exploring the Most Common Development Models

7. Section 2: Software Architecture Patterns

8. Chapter 6: Exploring Essential Java Architectural Patterns

9. Chapter 7: Exploring Middleware and Frameworks

10. Chapter 8: Designing Application Integration and Business Automation

11. Chapter 9: Designing Cloud-Native Architectures

12. Chapter 10: Implementing User Interaction

13. Chapter 11: Dealing with Data

14. Section 3: Architectural Context

15. Chapter 12: Cross-Cutting Concerns

16. Chapter 13: Exploring the Software Life Cycle

17. Chapter 14: Monitoring and Tracing Techniques

18. Chapter 15: What's New in Java?

19. Other Books You May Enjoy

Case studies and examples

In this section, we are going to go on with our payment use case, to see some examples of integration and business automation.

For example purposes, we will use Camel, jBPM, and Drools. Our target runtime will be Quarkus, which we already saw in the previous chapter.

But many of the concepts and implementations are applicable to other runtimes, such as embedded ones (as in using the runtime as a dependency of your Java application), deployed on JBoss WildFly, and deployed on Spring Boot.

Integrating payment capabilities

Our first use case to implement integration is the connection of payment capabilities with a legacy backend. Let's suppose that we have developed our microservices payment application and it is working correctly. A new business requirement is to integrate a legacy platform for settlement purposes (which is a kind of accounting operation done after payments).

It's fairly easy for our core application to call a REST service...