Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
 Designing Hexagonal Architecture with Java

You're reading from   Designing Hexagonal Architecture with Java Build maintainable and long-lasting applications with Java and Quarkus

Arrow left icon
Product type Paperback
Published in Sep 2023
Publisher Packt
ISBN-13 9781837635115
Length 438 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Davi Vieira Davi Vieira
Author Profile Icon Davi Vieira
Davi Vieira
Arrow right icon
View More author details
Toc

Table of Contents (24) Chapters Close

Preface 1. Part 1: Architecture Fundamentals
2. Chapter 1: Why Hexagonal Architecture? FREE CHAPTER 3. Chapter 2: Wrapping Business Rules inside Domain Hexagon 4. Chapter 3: Handling Behavior with Ports and Use Cases 5. Chapter 4: Creating Adapters to Interact with the Outside World 6. Chapter 5: Exploring the Nature of Driving and Driven Operations 7. Part 2: Using Hexagons to Create a Solid Foundation
8. Chapter 6: Building the Domain Hexagon 9. Chapter 7: Building the Application Hexagon 10. Chapter 8: Building the Framework Hexagon 11. Chapter 9: Applying Dependency Inversion with Java Modules 12. Part 3: Becoming Cloud-Native
13. Chapter 10: Adding Quarkus to a Modularized Hexagonal Application 14. Chapter 11: Leveraging CDI Beans to Manage Ports and Use Cases 15. Chapter 12: Using RESTEasy Reactive to Implement Input Adapters 16. Chapter 13: Persisting Data with Output Adapters and Hibernate Reactive 17. Chapter 14: Setting Up Dockerfile and Kubernetes Objects for Cloud Deployment 18. Part 4: Hexagonal Architecture and Beyond
19. Chapter 15: Comparing Hexagonal Architecture with Layered Architecture 20. Chapter 16: Using SOLID Principles with Hexagonal Architecture 21. Chapter 17: Good Design Practices for Your Hexagonal Application 22. Index 23. Other Books You May Enjoy

Answers

  1. Contrary to value objects, entities have an identity.
  2. No. The most important property of a value object is its immutability.
  3. The entry-point object for any aggregate is called an aggregate root.
  4. No, but objects from other domains and other hexagons can call domain services.
  5. A policy is a pattern that encapsulates part of the problem domain knowledge in a block of code or an algorithm. A specification is a pattern that works with predicates to assert the validity of the properties of objects.
  6. Because a POJO doesn’t depend on external technology details, such as a feature provided by an external library or a framework. Instead, a POJO relies only on a standard Java API, which makes POJOs simple and easy-to-reuse objects. POJOs are helpful for creating business rules objects that aren’t blurred by technology details.
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 £16.99/month. Cancel anytime