book

Enterprise Architecture with .NET

Name: Enterprise Architecture with .NET
Author: Jean-Philippe Gouigoux
ISBN: 9781835085660

by Jean-Philippe Gouigoux

May 2024

Intermediate to advanced

772 pages

22h 23m

English

Packt Publishing

Read now

Unlock full access

Enterprise Architecture with .NET
ForewordContributorsAbout the authorAbout the reviewer
Preface
What this book coversTo get the most out of this bookDownload the example code filesConventions usedGet in touchShare your thoughtsDownload a free PDF copy of this book
Part 1: Business-Aligned Architecture and the Problems It Solves
Chapter 1: The Sad State of Information Systems
What is an information system?A quick history of information systemsSoftware building – still craftsmanshipCraftsmanship as opposed to previous lack of qualityA word about “emerging architecture”Craftsmanship as opposed to an industrialized approachConcept of technical debtThe long-standing comparison of software to mechanical systemsThe efficiency of an ISThe measure of efficiency of a systemThe cost of maintenanceExamples of the prohibited evolution of IT systemsClassification of the causesThe classical symptoms of a blocked ISRate of renewal of large systemsSummaryFurther reading
Chapter 2: Applying Industrial Principles to Software
What is an industry?The two roots of industrialization – modularization and standardizationModularity to reduce complexityStandardization to ensure modularity is helpfulManagement of complexityDifferent types of complexityComputer science as a way to deal with complexityInformation systems and complexityThe concept of “as a service”Link to a minimum viable productThe benefits of standards and normsDocker, containers, and OCIAnother example with IAMThe urbanism metaphor of information systemsSummary
Chapter 3: Reaching Business Alignment
Technical requirementsSoftware for business and the principle of alignmentThe jungle of technical recommendationsAn example with KISS, DRY, and WETThe particular case of internal toolboxes/frameworksThe only stable guide: aligning to your users’ businessDigression on the digital transformation of companiesConway’s law applied to application and systemsIntroducing the CIGREF diagramProcess levelFunctional levelSoftware layerHardware layerUsing the four-layer diagramWhat should we map?How to start drawing a four-layer diagramA generic difficulty when aligning information systemsEvolving the information system in timeThe four-layer diagram method for service providersPatterns and antipatterns of alignmentThe sad reality of alignmentWhat we can aim forThe main antipatterns in alignmentSome other antipatterns and a proposed classificationSummary
Chapter 4: Dealing with Time and Technical Debt
The impact of time on systems due to functional changeA bit of fun with ill-placed comparisonsConsequences in the software worldHow the Agile approach aims at solving the time problemA metaphor to explain AgileBack to the concept of emerging architectureApparent opposition between architecture and Agile methodsThe position of famous architectsThinking ahead with function contractsThe concept of technical debtThe general definition of technical debtCauses of technical debt and its relation to timeTechnical debt’s relation to timeDebt or usury?Ways to balance technical debtThe Big Bang temptationAn experience-proven blueprint method for information systemsIt all starts with... mapping!Finding the atomic actionsA few last words on time, semantics, and alignmentSummary
Chapter 5: A Utopic Perfect IT System
The concept of an ideal IT systemThe use for an ideal structureThe origin of the designUsing a vision to define a targetData management in the ideal systemData is the blood of information systemsData as the 21st-century oil – really?A really “know it all” systemRelationship with CQRSThe need for data qualityDesigning a generic “referential”Choices of implementation for an MDMRules management in the ideal systemRules as the nervous network of the information systemBRMS as a dedicated tool for business rule handlingCommon implementations of business rulesProcesses management in the ideal systemProcesses as the brain of the information systemImplementations of a BPMHow close can we get to this utopic system?Favoring contextsApproaching the target, the Agile waySummaryFurther reading
Part 2: Architecture Frameworks and Methods
Chapter 6: SOLID Principles, from Code to Systems
Describing the sample information system requirementsThe company and its businessThe users and actors of the information systemData manipulationThe stakes of the information system for the companyThe situation as seen by the person put in charge of improving the systemSOLID principles and application to systems of whatever scaleSingle responsibility principleOpen/closed principleLiskov substitution principleInterface segregation principleDependency inversion approachCritical analysis of SOLIDLimits of the separation of responsibilitiesAbout the polemics on monolithsBeware of unintended couplingWrapping up before going back to the demo

Chapter 7: C4 and Other Approaches
The C4 approachThe context levelThe container levelThe component levelThe code levelClean architecture, hexagonal architecture, and other frameworksTechnical architecture patternsOnion architectureHexagonal architectureClean architectureSummary
Chapter 8: Service Orientation and APIs
Looking at the history of service orientationThe long-awaited reusabilityRoutines and avoiding punching additional paper cardsLibraries and the capacity to share instructions between programsAttempts at general interoperabilityUsing web standards to try and get universalThe steps in middlewareThe most recent evolution – REST APIsWhat we are missing to reach actual service reusabilityCharacteristics of a serviceAs a service explainedGetting rid of middleware altogetherExternal interop finally becoming a realityInterop made real with standardsKeeping complete compatibilityManaging APIsInversion of dependency for servicesApplication to our demonstration systemInterfaces needing analysisUsing norms and standardsWhere do I find norms and standards?Pivotal format for the other interfacesSummary
Chapter 9: Exploring Domain-Driven Design and Semantics
A functional approach to a functional problemThe importance of semanticsDDDApplication to clean information system architectureUsing entities in referential applicationsManaging the life cycle of entitiesRelation between subdomains and timeLink to the API and servicesIncluding time in an APIAligning an API to subdomains and the consequencesAPI testabilitySummary
Chapter 10: Master Data Management
Responsibilities around the dataPersistenceThe question of identifiersThe single entity reading responsibilityOther kinds of reading responsibilitiesThe complex art of deleting dataRelation to specialized linksSo-called secondary featuresMetadata and special kinds of dataThe different kinds of data referential applicationsCentralized architectureClone architectureConsolidated and distributed architecturesOther types of referential architecturesSome architectural choicesTabular versus NoSQLCQRS and event sourcingOne more step beyond databases – storing in memoryPatterns of data evolution in timeData governanceProgressive implementation of a unique referentialKeeping an eye on dogma and useless complexitySummary
Chapter 11: Business Processes and Low Code
Business processes and the BPMN approachWhat is a business process?Granularity in the processesLimits of the processesBusiness process modelingThe history of BPM standardsThe BPMN 2.0 standardBusiness processes software-based executionPrinciplesApplication to our example information systemLink to usersAvailable software for BPMN edition and executionWhy so little use of BPMN in the industry?Other associated practicesBusiness activity monitoringBusiness process simulation and optimizationBusiness process miningOther approaches to business process implementationProcess in the GUIProcess in higher-level APIsProcess in a MOM/ESBLow-code/no-code approaches to processesChoreography instead of orchestrationImplementing choreographyShould I use BPMN in my information system?Summary
Chapter 12: Externalization of Business Rules
Business Rules Management SystemsHow does a BRMS handle business rules?Additional characteristics of a BRMSActual use of BRMSExamples of a BRMSThe DMN standardThe origin and principle of DMNImplementationsAn example of DMN useCalling the business rule runtimeSummary
Chapter 13: Externalization of Authorization
A BRMS and authorization managementThe semantics of identity and authorization managementA digression on IAM implementationRole-based access control and attribute-based access control modelsThe XACML approachA digression on the granularity of microservicesApplying authorization to our sample information systemThe Open Policy Agent alternativeThe functional needs of DemoEditorCreating the authorization policiesAdding some data in order to make decisionsDeploying a Docker-based OPA serverTesting the authorizationsChallenges with OPASummary
Part 3: Building a Blueprint Application with .NET
Chapter 14: Decomposing the Functional Responsibilities
Some more context about the DemoEditor information systemCurrent company organizationThe current state of important dataWhat kind of information system is going to be built?Decomposing into a four-layer architectureBusiness process management layerThe BCM layerSoftware layerHardware layerLooking for standards for interfacesWriting up the specifications for the different modulesOverall system specificationsThe books referential serviceThe issue with migrationAuthors referential serviceIAMAuthorizationsTechnical specificationsExplaining how the interface will run the main use scenariosIntegration of the applications in the systemTechnical implementation of the applicationsSummary
Chapter 15: Plugging Standard External Modules
Externalizing IAM with KeycloakRealmsDelegation to Office 365 for internal user SSOMinimal implementation of external usersExternalizing persistence with MongoDBChoosing between local and online storageA little digression about old CPUsNo schema, no initialization phase!Securing through regular backupsOptionally installing a web consoleExternalizing document managementChoosing the right standard, not the right implementationStarting up AlfrescoAlternative for Alfresco setupTesting calls to the EDM moduleUsing the Apache Chemistry console as an Alfresco CMIS clientExternalizing queue management with RabbitMQStarting up the MOMDefining which streams should be handled, and operating a MOMSummary
Chapter 16: Creating a Write-Only Data Referential Service
Technical warmupGetting connected to the Git repositoryCreating the project skeletonHow to run the exampleStarting small, with a RAM-only applicationRepresenting the dataReading a single piece of dataAdding persistenceStoring operations rather than statesChoosing NoSQLA few more words on NoSQL and persistenceRemark on multitenancyCreating the data business modelA switch in thinking – modify first, create afterwardLinking the books-changes collection to the databaseFinishing the patch operation implementationCreation as a special case of modificationSummary
Chapter 17: Adding Query to the Data Referential Service
Adding features to the first version of the data referential serviceTesting the data referential serviceThe particular case of deletionQuerying as an extension of the reading responsibilityUsing ODP for a standard query APIPagination, filtering, and moreLinks to business intelligence and big data systemsA few last remarks on the books API implementationTestingTesting at the API levelManaging dependenciesSummary
Chapter 18: Deploying Data Referential Services
Installing the data referential service in the information systemDocker deploymentAdding a status operation to the APIPlugging the data referential service into the IAMPreparing the IAM to be used by the books referential serviceIntegrating the code with the IAMAdding RBAC authorization based on IAM attributesPolishing with additional ABAC authorizationsWhy are we doing all this?Summary
Chapter 19: Designing a Second Data Referential Service
Building the authors data referential serviceLinks between data referential servicesAdding a local cacheUsing Webhooks for cache quick refreshImplementing callbacks in the authors referentialRegistering to webhook in the books referentialUsing the cache in the books referentialAdditional issues on webhooks managementDealing with eventual consistencyA data referential service is not just about CRUDSummary
Chapter 20: Creating a Graphical User Interface
A standard web single page applicationDefining the GUIPreparing IAM for the clientGenerating the client skeletonTaking into account authorization concernsAdding a debugging identity page to the applicationConnecting the GUI to the backendModifying authorization in the backendListing books from the portal GUISolving authentication issuesSeparation of concerns for the pagination featureImplementing paginationSummary
Chapter 21: Extending the Interfaces
Importing some real dataThe first step of migrationImplementing data importTesting data import and next stepsTesting the GUIAutomatic end-to-end tests of the GUITests at the component levelApplying a MAUI mobile applicationThe benefits of a responsive interfaceMAUI Blazor as a mobile platformFusing MAUI and Blazor WebAssemblyAdditional considerations for graphical interfacesDecomposition of the frontendContent negotiation for a simple interfaceState managementSeparation of responsibilities for application loggingSummary
Chapter 22: Integrating Business Processes
The need for processesOrchestration and choreographyApplication to DemoEditorHow to choose the right process implementationThe GUI as the main process implementationHuman processes versus automated processesImplementation through the user interfacePassing the message to another role in the processLetting the author fill in the information in the same GUIValidating and publishing informationAdvanced uses of the GUI for process implementationImplementation through a wizardDealing with long-duration processesExternalizing processes in a dedicated toolUsing a BPMN approach, but not a BPMN engineA light alternative to BPMN orchestrationChoreographing the regular import of the book’s catalogOrchestrating the creation of a new projectAdding a dedicated service for a complex step in the processesBusiness-aligned definition of a middle officeDefining the middle office service APIImplementing the middle office servicePlugging the middle office into the process of book contractingSummary
Part 4: Validating the Architecture
Chapter 23: Applying Modifications to the System
Technical requirementsA word of warning, and an anecdoteModification at the data levelAdding a simple attributeExtending the possible values of an existing attributeMigrating a schema in a schemaless worldAscending compatibility and OpenAPIModification in the GUITaking into account the addition of a new attributeModifying ergonomics of the GUIAdding a change tracker in the form and implementing the auto-patchAdjusting the behavior of the pageConsidering further improvementsAdjusting IAM and business rulesCommon IAM changesIndustrializing KeycloakModifying the identity sourcesThe challenges of time and compatibility in IAM adjustmentModifying the business processesTypes of modificationsExamples of business process modificationsA few last words on the sample software applicationsCode adjustmentsAdjusting expositionSummary
Index
Why subscribe?
Other Books You May EnjoyPackt is searching for authors like youShare your thoughtsDownload a free PDF copy of this book

Overview

Enterprise Architecture with .NET arms you with the knowledge and techniques to craft robust, scalable, and business-aligned software infrastructure. From fundamental theories to hands-on practices in .NET and C#, this book serves as your comprehensive guide to mastering efficient information system designs.

What this Book will help me do

Understand the principles of designing business-aligned and maintainable software systems.
Learn to apply design frameworks like SOLID principles and domain-driven design.
Gain proficiency in creating modular, scalable applications using .NET technologies.
Develop skills to design and implement secure and reusable APIs for system interoperability.
Enhance your ability to address technical debt and prepare your software for evolving business requirements.

Author(s)

Jean-Philippe Gouigoux, seasoned software architect and author, brings years of experience in designing and implementing enterprise-level systems. With a specialized focus on business-IT alignment and robust architecture frameworks, his writing blends academic rigor with actionable insights. Gouigoux is passionate about helping developers build sustainable and efficient software systems.

Who is it for?

This book is tailored for software architects and developers passionate about building sustainable and maintainable systems. It's ideal for those dedicated to addressing challenges like technical debt. Readers should have prior software design experience and an eagerness to deepen their knowledge in .NET and modern architectural frameworks.

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Implementing Event-Driven Microservices Architecture in .NET 7

Publisher Resources

ISBN: 9781835085660

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills