Microservices Architecture
Service decomposition, API gateway, service discovery, distributed transactions, resilience patterns, Kubernetes basics (deployments, services, config)
1What is the Bounded Context pattern in Domain-Driven Design applied to microservices?
What is the Bounded Context pattern in Domain-Driven Design applied to microservices?
Resposta
A Bounded Context defines an explicit boundary around a domain model with its own ubiquitous language and database. In microservices architecture, each Bounded Context typically becomes an independent distributed microservice. This ensures data autonomy and prevents model sharing between services. For example, the User entity in the Profile context can share the ID with the Buyer entity in the Ordering context, but they remain distinct models with their own attributes and business logic.
2What is the main role of an API Gateway in a microservices architecture?
What is the main role of an API Gateway in a microservices architecture?
Resposta
An API Gateway serves as a single entry point for groups of microservices, acting as a reverse proxy that routes client requests to appropriate services. It implements the Backend for Frontend (BFF) pattern and handles cross-cutting concerns like authentication, SSL termination, caching, and response aggregation. This simplifies client-to-microservice communication by avoiding multiple direct calls and centralizing routing logic.
3How does service discovery work in Docker Compose?
How does service discovery work in Docker Compose?
Resposta
Docker Compose uses internal DNS for service discovery. Each service defined in docker-compose.yml is accessible by its service name as hostname. For example, if a Redis service is named 'basketdata', other services can connect to it via ConnectionString=basketdata. Docker automatically resolves this name to the container's internal IP address on the shared Docker network, eliminating the need to hardcode IP addresses.
What is the principle of the Circuit Breaker pattern with Polly in .NET?
How to configure a retry policy with Polly for HttpClient in .NET?
+22 perguntas de entrevista
Outros temas de entrevista .NET
C# Basics
LINQ & Delegates
C# Language Essentials
ASP.NET Core Fundamentals
ASP.NET Core Request Lifecycle
Configuration & Settings
Application Lifecycle
Dependency Injection
Entity Framework Core
Minimal APIs
Web API Development
Async in ASP.NET Core
Authentication & Authorization
HttpClient & Networking
JSON Serialization
Entity Framework Core Advanced
C# Advanced Features
Clean Architecture
Logging, Monitoring & Observability
Unit Testing & xUnit
Integration Testing
Docker & Containerization
NuGet Package Management
Memory Management & GC
Reactive Programming
Async/await & Patterns
.NET Design Patterns
Performance Optimization
Security & Best Practices
SignalR & Real-time
Domine .NET para sua proxima entrevista
Acesse todas as perguntas, flashcards, testes tecnicos, exercicios de code review e simuladores de entrevista.
Comece gratis