Advanced Software Architectures

4,2 (78 voting)
 Last update date 08/2026
 Türkçe
egitim.kurumsalbasvuru

Robotic Coding Training (For Middle School Students) check out our education.

📞Contact:  0850 840 85 43 📧 E-Mail: usem@uludag.edu.tr

The training is intended for professional development purposes, and the certificate obtained does not replace an MYK authorization certificate in trainings where an MYK authorization certificate is mandatory.

1. Training Overview and Format

The training duration and format have been updated with two alternative options, taking into consideration the operational workload of your organization: Face-to-Face (4 Days) or Online (8 Days - Half-Day Sessions).

 Training Name

Advanced Software Architectures

 Target Audience

Senior Developers, Technical Leads, and Aspiring Software Architects (Closed Group of 10 Participants)

 Alternative 1 (Face-to-Face)

4 Full Days (At the Organization's Office) - 20 Hours Total

 Alternative 2 (Online)

8 Half-Days (Virtual Classroom) - 20 Hours Total

 

 Alternative Schedule Plans

* Important Note: The training hours specified below are for reference only and are flexible according to the daily workflow of your organization. They can be adjusted prior to the training through mutual consultation, in line with the requirements of your organization.

 

Training Content

Module 1: Modern Architecture Fundamentals and Principles

  • Architectural Mindset: The role and responsibilities of a software architect, requirements analysis (NFRs - Non-Functional Requirements), and creating Architecture Decision Records (ADR).

  • Core Principles and Technical Debt: The application of SOLID, DRY, KISS, and YAGNI principles in enterprise projects, code complexity (cyclomatic complexity), and technical debt management.

  • Modern Architectural Patterns: Beyond layered architecture; in-depth analysis of Clean Architecture, Onion Architecture, and Hexagonal Architecture (Ports and Adapters).

  • Domain-Centered Design: Identifying use cases, the dependency rule, and designing a core layer isolated from the outside world.

  • Practical Case Study: Theoretical redesign of a financial application with monolithic and spaghetti code using Clean Architecture principles and separation of layers.

Module 2: Distributed Systems and Microservices

  • Domain-Driven Design (DDD): Defining Bounded Context boundaries, creating a Ubiquitous Language, and Entity, Value Object, Aggregate, and Repository patterns.

  • Microservices Transformation: Safe migration strategies from monolithic structures to microservices, implementation of the Strangler Fig Pattern, and use of the Anti-Corruption Layer (ACL).

  • Inter-Service Communication: Synchronous (REST, gRPC) communication methods, API design standards (Richardson Maturity Model), and idempotent endpoint design.

  • API and Traffic Management: API Gateway architecture (Routing, Rate Limiting, Authentication), Service Mesh (Istio/Envoy) architecture, and Backend for Frontend (BFF) Pattern.

  • Service Discovery and Configuration: Service Discovery (Consul, Eureka) in dynamic environments and distributed configuration management.

Module 3: Data Management and Event-Driven Architectures

  • Data Consistency: CAP Theorem, PACELC Theorem, and the data integrity challenges created by the "Database per Service" approach.

  • Distributed Transaction Management: Limitations of Two-Phase Commit (2PC) and management of long-running transactions using the Saga Pattern (Choreography vs Orchestration models).

  • CQRS Architecture: Performance optimization by physically/logically separating read and write databases using Command Query Responsibility Segregation (CQRS).

  • Event Sourcing: Recording all state changes in the system as a sequence of events instead of storing the current state, and the concept of an "Event Store".

  • Asynchronous Communication and Messaging: Message Broker (Kafka, RabbitMQ) architectures, Publish/Subscribe pattern, Eventual Consistency, and Dead-Letter Queue (DLQ) strategies.

Module 4: Performance, Scalability, and Observability

  • Scaling Strategies: Dynamics of Vertical and Horizontal scaling, Stateless application design, and Auto-scaling scenarios.

  • Performance Improvements: Distributed Caching (Distributed Cache - Redis, Memcached), Cache Invalidation strategies (Cache-Aside, Write-Through, etc.), and CDN usage.

  • Resilience: Error handling in distributed systems; resilient architecture design using Circuit Breaker, Retry, Timeout, Fallback, and Bulkhead patterns.

  • Cloud-Native and Modern Deployment: 12-Factor App principles, Containerization (Docker) fundamentals, and deployment, pod, and service concepts on Kubernetes.

  • Observability: Identifying system bottlenecks through Centralized Logging (ELK Stack), Metrics Monitoring (Prometheus/Grafana), and Distributed Tracing (Jaeger/Zipkin).

The training is open to corporate collaboration (packaged for the legal entity of an organization/company), and individual applications are not accepted. The training content can be restructured according to the profile and needs of corporate participants. Following mutual consultations, the scope and method of the training (Face-to-Face, Online) are determined and the relevant processes are completed. Upon reaching an agreement, suitable dates and times for the organization's participants and our academic staff, as well as the location where the training will be conducted, are determined.

Comments

Add a comment
More
Share:
Advanced Software Architectures
Corporate Application

You are allow cookie by using us website. ENTER