Technical Architecture Design Principles: Strategy and Tactics for Backend Systems

Technical architecture is the process of turning product requirements into concrete technical solutions, defining the components, their relationships, and deployment strategies, with a focus on Java‑based stacks, security, performance, and big‑data concerns.

The biggest challenge is uncertainty: choosing between the latest technologies and familiar ones, handling future evolution, and balancing risk versus benefit.

Strategic layer design principles :

Suitability principle – select the most appropriate technology for the team and project rather than the newest hype.

Simplicity principle – keep the design as simple as possible while meeting requirements.

Evolution principle – treat architecture as an evolving artifact that adapts to business changes.

Tactical layer design principles are divided into three parts:

High‑concurrency principle – adopt stateless services, split systems, service‑oriented architecture, message queues, data heterogeneity, and caching.

High‑availability principle – implement degradation switches, multi‑level read services, Nginx/Lua based traffic shaping, and graceful fallback strategies.

Business‑design principle – ensure idempotency, avoid duplicate design, define clear workflows, use state machines, provide feedback and approval mechanisms, and maintain documentation and backups.

Key technical details for high concurrency include:

Stateless applications for easy horizontal scaling.

System splitting by business, function, read/write, and AOP dimensions.

Service‑oriented evolution from in‑process services to registered, discoverable micro‑services.

Message queues for decoupling, asynchronous processing, and traffic buffering.

Data heterogeneity to handle diverse data sources and create closed‑loop storage.

Caching at user, proxy, access, application, and data layers (DNS, CDN, Nginx, Redis, NoSQL, etc.).

High‑availability tactics cover degradation (centralized switches, read‑only fallback, Nginx/Lua routing), rate limiting (protect against attacks, Nginx limits, IP deny lists), and rollback (quick revert to a stable version).

Business design principles emphasize preventing duplicate effort, ensuring idempotent operations, defining processes, managing state machines, providing system feedback, enabling approval workflows, documenting code, and backing up data.

The article also presents technical architecture diagrams :

Logical architecture (functional and product architecture) showing component interactions.

Physical architecture focusing on network, cluster, middleware, and storage deployment.

In conclusion, a well‑planned architecture improves system performance and quality, while continuous evolution adapts the design to changing business needs, balancing long‑term stability with the software lifecycle.