You're reading from Enterprise Architecture with .NET Expert-backed advice for information system design, down to .NET and C# implementation

Product type Paperback

Published in May 2024

Publisher Packt

ISBN-13 9781835085660

Length 772 pages

Edition 1st Edition

Languages

Tools

.NET

Concepts

Application Development

Author (1):

Jean-Philippe Gouigoux

View More author details

Table of Contents (30) Chapters

Preface

1. Part 1: Business-Aligned Architecture and the Problems It Solves

2. Chapter 1: The Sad State of Information Systems FREE CHAPTER

3. Chapter 2: Applying Industrial Principles to Software

4. Chapter 3: Reaching Business Alignment

5. Chapter 4: Dealing with Time and Technical Debt

6. Chapter 5: A Utopic Perfect IT System

7. Part 2: Architecture Frameworks and Methods

8. Chapter 6: SOLID Principles, from Code to Systems

9. Chapter 7: C4 and Other Approaches

10. Chapter 8: Service Orientation and APIs

11. Chapter 9: Exploring Domain-Driven Design and Semantics

12. Chapter 10: Master Data Management

13. Chapter 11: Business Processes and Low Code

14. Chapter 12: Externalization of Business Rules

15. Chapter 13: Externalization of Authorization

16. Part 3: Building a Blueprint Application with .NET

17. Chapter 14: Decomposing the Functional Responsibilities

18. Chapter 15: Plugging Standard External Modules

19. Chapter 16: Creating a Write-Only Data Referential Service

20. Chapter 17: Adding Query to the Data Referential Service

21. Chapter 18: Deploying Data Referential Services

22. Chapter 19: Designing a Second Data Referential Service

23. Chapter 20: Creating a Graphical User Interface

24. Chapter 21: Extending the Interfaces

25. Chapter 22: Integrating Business Processes

26. Part 4: Validating the Architecture

27. Chapter 23: Applying Modifications to the System

28. Index

Why subscribe?

29. Other Books You May Enjoy

Additional considerations for graphical interfaces

Before we close this chapter, a few considerations are in order about graphical interfaces when talking about business alignment and the correct separation of responsibilities. Since these considerations bear no relation to each other, they will be discussed in the following separate sections.

They will not be accompanied by code samples because it would bring us too far on the technical side. If you want to see them in action, please keep an eye on the accompanying source code and its evolution, which may encompass these subjects in the future. But for now, we will only cover how they should be implemented to respect the design principles we have developed in this book.

Decomposition of the frontend

One of the first reflections architects have when they start working with services (I prefer to simply talk about services, rather than SOA or microservices, which have become too oriented toward particular technologies and techniques...