Strategic and Tactical Design Principles for Technical Architecture

Technical architecture is the process of turning product requirements into concrete technical solutions, covering layer separation, framework and language choices (primarily Java), and non‑functional concerns such as security, performance, and big data.

The biggest challenge for architects is uncertainty: whether to adopt the latest industry technologies or the ones the team is most familiar with, and how to handle future evolution and problem solving when new technologies fail.

Because business and technology constantly change, there is no universal architecture pattern; therefore, design must balance stability and excellence through strategic and tactical principles.

Strategic Layer Design Principles

The strategic layer follows three principles: suitability, simplicity, and evolution.

1.1 Suitability Principle

Engineers often want to use the newest frameworks or reinvent wheels, but blindly chasing new technology leads to high failure risk, especially when teams are small, lack experience, or lack accumulated knowledge.

In practice, the most appropriate technology—one that fits the team’s skill set and project constraints—is preferable to the most cutting‑edge solution.

1.2 Simplicity Principle

Simplicity means delivering a solution that meets requirements with the least complexity, avoiding unnecessary structural or logical intricacy that can increase failure probability and maintenance cost.

Structural complexity arises from many components and intricate relationships; logical complexity arises when a single component contains too much logic, making the system hard to understand and evolve.

1.3 Evolution Principle

Software architecture must evolve with business changes; attempting to design a final, unchanging architecture leads to over‑investment and eventual mismatch with real needs.

Evolution involves iteratively improving the design, preserving good decisions, fixing defects, and discarding unnecessary parts.

Tactical Layer Design Principles

The tactical layer provides detailed guidance in three areas: high concurrency, high availability, and business design.

2.1 High Concurrency Principle

Key aspects include statelessness, splitting, service‑orientation, message queues, data heterogeneity, and caching.

Stateless applications facilitate horizontal scaling; state can be externalized via a configuration center.

Splitting can be done by system, function, read/write characteristics, AOP, or module dimensions.

Service‑orientation evolves from in‑process calls to clustered services with registration, routing, and governance.

Message queues decouple services, enable asynchronous processing, and provide flow control.

Data heterogeneity aggregates changes via queues and creates closed‑loop storage.

Caching spans user‑side (DNS, browser, app), proxy‑side (CDN, Nginx), access‑side (Nginx+Lua+Redis), application‑side (static pages, Redis/Memcache), and data‑side (NoSQL).

2.2 High Availability Principle

Includes degradation, rate limiting, and rollback mechanisms.

Centralized degradation switches allow graceful fallback to read‑only caches or simplified services.

Rate limiting protects against malicious traffic and overload, using Nginx limits, IP deny lists, or firewall rules.

Rollback ensures quick recovery to a stable version when a release fails.

2.3 Business Design Principle

Idempotent and de‑duplication designs.

Clear workflow definitions and state‑machine modeling.

Feedback mechanisms for backend operations and approval processes.

Comprehensive documentation and backup strategies.

Technical Architecture Diagrams

Two types of diagrams are used: logical (functional) architecture and physical (non‑functional) architecture.

Logical diagrams illustrate how technology components realize product features, typically presented in an overall‑local‑overall hierarchy.

Physical diagrams focus on network, cluster, middleware, and storage design, showing how the system is deployed across hardware.

Conclusion

Good software architecture is a planned, evolving artifact; its quality influences system performance, reliability, and future adaptability. While a perfect universal architecture does not exist, a well‑designed, domain‑specific architecture can be iteratively refined to support rapid business growth.