Strategic and Tactical Design Principles for Technical Architecture

Technical architecture translates product requirements into concrete technical solutions, addressing layering, framework and language choices (primarily Java), and non‑functional concerns such as security, performance, and big data, while defining the components, their relationships, and deployment strategies.

The biggest challenge in architecture is uncertainty: whether to adopt the latest technologies or stick with familiar ones, and how to handle future evolution and potential issues arising from new tech.

Strategic design principles consist of three core ideas: the suitability principle (choose the most appropriate technology rather than the newest), the simplicity principle (prefer simple, maintainable solutions), and the evolution principle (design for continuous iteration and adaptation).

Tactical design principles are divided into three parts: high‑concurrency (statelessness, service decomposition, service‑orientation, messaging, data heterogeneity, caching), high‑availability (degradation switches, multi‑level read services, gateway‑level throttling, IP blocking), and business‑design (idempotency, workflow definition, state machines, auditability, documentation, backup).

Logical architecture diagrams illustrate how functional requirements map to technical components, while physical architecture diagrams focus on network, cluster, middleware, and storage deployment, showing the system’s runtime organization.

The conclusion emphasizes that good architecture is planned and evolves over time, balancing comprehensive design with practical constraints to support rapid business growth.