Solution Architect

Що робити

• 1. System Design & Architecture
• Service Boundaries: design systems, define service interactions and domain boundaries.
• Monolith vs Services: decide what stays in the monolith and what becomes a separate service, avoiding a distributed monolith and overengineering.
• Communication & Events: define event flows and rules for sync vs async communication (HTTP, Kafka, gRPC, SQS).
• Multi-tenancy: design config-driven, scalable client configuration without tenant-specific hacks in the core system.