Embedded Files
06-Technology Architecture :
06-Technology Architecture :
Technology Architecture in Enterprise Architecture (EA) focuses on defining and organizing the technology infrastructure, software, and hardware components required to support an organization’s business goals and applications. It acts as the blueprint for the IT environment and includes technology standards, protocols, and technical services necessary for systems and applications to operate effectively.
Key Aspects of Technology Architecture in EA
Key Aspects of Technology Architecture in EA
- Infrastructure Components
Servers
Cloud: Which cloud will you select, and upon which criteria
On-Prime: Requires hardware configuration that meets application architecture, considering the growth and scalability.
Storage
Networks
Security Model
- Technology Standards and Protocols
Outlines technology standards (e.g., operating systems, network protocols) and design principles to ensure consistency, interoperability, and scalability across systems.
- Application Hosting and Integration
Determines how applications will be hosted (on-premises, cloud, or hybrid) and how different applications will communicate (APIs, message brokers, etc.). Integration standards help maintain data consistency and streamline information flow.
- Security and Compliance
Encryption
Access control
Communication protocols:
TLS
HTTP/HTTPS
Data security: Encryption/Virtual private database
SAST: Static application security testing, Using SonarCloud for example
DAST: Dynamic application security testing, using Pen testing tools, like OWASP ZAP, Burp Suite
WAF: Web application framework
Rate limiting: How to limit connectivity and monetize it.
- Technical Services and Platforms
Includes shared services such as authentication, data management, and logging, as well as technology platforms like CRM or ERP systems. These provide reusable functions that are critical for applications across the enterprise.
- Scalability and Performance
Ensures that the technology environment can scale with demand and meet performance expectations, which is essential for maintaining a high-quality user experience.
- Stability and resiliency of the environment
Here, the focus is on building a disaster recovery model for applications that enable smooth operation
8. Disaster recovery & Resiliency
8. Disaster recovery & Resiliency
Architecture
Multi-zone deployment
Multi-availability zone architecture
Replication
CICD
Testing
DR Drill
Resiliency Drill
9. SPOF
9. SPOF
A SPOF is a specific point in a system that, if it fails, causes the entire system to fail and services to stop. It is identified by any resource whose failure results in the complete collapse of the solution.
Single Node of Execution This occurs when an application runs on only one instance, meaning the solution is unavailable if that single node goes down. To eliminate this, developers use multiple nodes distributed behind a load balancer to ensure traffic is redirected if one node fails.
Resource Scaling and Auto-scaling Systems with fixed resources may fail during peak hours if they cannot handle incoming traffic beyond their initial capacity. Modern architectures use horizontal auto-scaling to automatically increase resources, such as pods, when traffic hits a certain threshold.
Single Backing Service Relying on a single external component, like one payment or SMS gateway, creates a risk where the entire system stops if that provider fails. Systems should implement multiple integration options (e.g., several payment gateways or authentication methods) to maintain service continuity.
Resiliency Design Patterns Patterns like Retry and Circuit Breaker help manage temporary failures by attempting reconnections or stopping traffic to prevent resource exhaustion. Advanced patterns like the Scheduler Agent and Saga Transaction are used to save the state of a journey and roll back changes if a process ultimately fails
Dr. Ghoniem Lawaty
Tech Evangelist
Page updated
Google Sites
Report abuse