|
|
|
|
| LEADER |
06192nmm a2200421 u 4500 |
| 001 |
EB002138175 |
| 003 |
EBX01000000000000001276302 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
230102 ||| eng |
| 020 |
|
|
|a 148428948X
|
| 050 |
|
4 |
|a QA76.76.A65
|
| 050 |
|
4 |
|a QA76.9.A73
|
| 100 |
1 |
|
|a Fernando, Chanaka
|
| 245 |
0 |
0 |
|a Solution architecture patterns for enterprise
|b a guide to building enterprise software systems
|c Chanaka Fernando
|
| 260 |
|
|
|a New York, NY
|b Apress
|c 2023
|
| 300 |
|
|
|a 388 p.
|
| 505 |
0 |
|
|a 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
|
| 505 |
0 |
|
|a 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
|
| 505 |
0 |
|
|a 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
|
| 505 |
0 |
|
|a 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
|
| 505 |
0 |
|
|a 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)
|
| 653 |
|
|
|a Ordinateurs / Architecture
|
| 653 |
|
|
|a Computer architecture / http://id.loc.gov/authorities/subjects/sh85029479
|
| 653 |
|
|
|a Computer software / Development / http://id.loc.gov/authorities/subjects/sh85029535
|
| 653 |
|
|
|a Computer software / Development / fast
|
| 653 |
|
|
|a Computer architecture / fast
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 500 |
|
|
|a Includes index. - Designing MSA with a Message Broker
|
| 024 |
8 |
|
|a 10.1007/978-1-4842-8948-8
|
| 776 |
|
|
|z 9781484289471
|
| 776 |
|
|
|z 9781484289488
|
| 776 |
|
|
|z 148428948X
|
| 776 |
|
|
|z 1484289471
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781484289488/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 004.2/2
|
| 520 |
|
|
|a 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 software systems for hundreds of different organizations across the globe. The architecture diagrams (patterns) and examples allow you to not only grasp the concepts, but to build working projects. Solution Architecture Patterns for Enterprise starts with an introduction to the concepts of enterprise software systems and solution architecture and later moves to individual solution architecture patterns used in real-world enterprises. Subsequent sections cover various industry-specific solution architecture patterns that can be used to build domain-specific software systems. The book concludes with a view of what the future holds for solution architecture, including likely new developments in the field. This book will help enterprise software architects and engineers to design and implement real-world enterprise software systems using best practices and techniques adopted by organizations across the globe. It provides software architecture blueprints to build domain-specific enterprise software systems. If you are working on any digital transformation project or initiative, you will find this book useful, as it provides quick reference on architecture and implementation to get started with your work. What You Will Learn Understand the key elements of enterprise software systems and how to design and implement them Master different approaches to build real-world software applications Build domain specific enterprise software systems Use open-source tools to build enterprise software systems Who This Book Is For Software Developers, software architect, solution architects, and enterprise architects
|