Solution architecture patterns for enterprise : a guide to building enterprise software systems /

Gain a deeper understanding of how distributed systems work, as well as which applications and systems are used for specific business domains or industries. This book provides a set of solution architecture patterns that were developed based on the author's experience building enterprise softwa...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor principal: Fernando, Chanaka (Autor)
Formato: Electrónico eBook
Idioma:Inglés
Publicado: New York, NY : Apress, [2023]
Temas:
Computer architecture.
Computer software > Development.
Acceso en línea:Texto completo (Requiere registro previo con correo institucional)
Tabla de Contenidos:
  • Intro
  • Table of Contents
  • About the Author
  • About the Technical Reviewer
  • Acknowledgments
  • Introduction
  • Chapter 1: Introduction to Enterprise Software Systems
  • What Are Enterprises?
  • How Software Is Used in Enterprises?
  • How Software Is Used in the Healthcare Industry
  • How Software Is Used in the Retail Industry
  • Characteristics of Enterprise Software Systems
  • Scalability
  • Availability
  • Latency
  • Robustness
  • Security
  • Modularity
  • Reusability
  • Replaceability
  • Observability
  • Adaptability
  • Practical Examples of Enterprise Software Systems
  • Enterprise Software System Architecture for Healthcare
  • Enterprise Software System Architecture for Transportation
  • Summary
  • Chapter 2: Introduction to Solution Architecture
  • What Is Enterprise Architecture?
  • Layered Enterprise Architecture Pattern
  • Microservices-Based Enterprise Architecture Pattern
  • What Is Solution Architecture?
  • Business Architecture (Level 0 Architecture)
  • Technical Architecture (Level 1 Architecture)
  • Deployment Architecture (Level 2 Architecture)
  • Solution Architecture Defining Process
  • Complex Solution Architecture Example
  • Business Architecture for a Banking Solution
  • Technical Architecture for a Banking Solution
  • Build vs. Buy
  • Deployment Architecture for a Banking Solution
  • Moving from Solution Architecture to Implementation
  • Sample Project Timeline
  • Weeks 1-2
  • Weeks 3-4
  • Weeks 5-6
  • Weeks 7-10
  • Weeks 11-14
  • Weeks 15-16
  • Advantages of Solution Architecture Patterns
  • Summary
  • Chapter 3: Building Enterprise Software Systems with Microservice Architecture
  • Introduction to Microservice Architecture (MSA)
  • Size and the Scope of the Service
  • Functionality (Domain)
  • Lines of Code (Size)
  • Number of Functions (Scope)
  • Nature of the Service
  • Development
  • Deployment
  • Deployment Automation
  • Container-Based Deployments
  • Governance
  • A Reference Architecture for Enterprise Software System with MSA
  • Components of Enterprise Software Systems
  • Databases
  • Core Business Applications
  • Integration Software
  • API Software
  • Accessibility Software
  • Proxy Servers
  • Load Balancers
  • Ingress Controllers
  • Content Delivery Network (CDN)
  • Firewalls
  • Security Software
  • User Management
  • Access Management
  • Authentication
  • Authorization
  • Monitoring Software
  • Monitoring for Insights
  • Observability
  • Infrastructure Management Software
  • A Reference Architecture with MSA
  • In-House Applications
  • Migrating Existing Applications to Microservice Architecture
  • Strangler Pattern for Migration
  • Integration Software
  • API software
  • API Gateway or Microgateway (Data Plane)
  • API Manager (Control Plane)
  • API Developer Portal
  • Security Software
  • Defining the Reference Architecture
  • What Is a Service Mesh and How to Use It with MSA?
  • Introduction to Service Mesh
  • Using Service Mesh for MSA

Ejemplares similares