oracle

System architecture design involves defining high-level structure, selecting technology components, and planning for growth. Start by mapping business requirements to technical constraints, choose patterns suited to your scale, and document trade-offs between consistency, availability, and performance across your stack.

Evaluate architectural decisions by assessing scalability, maintainability, and alignment with business goals. Document the rationale for each choice, consider load patterns and bottlenecks, and compare alternative patterns before committing to implementation.

Performance and scalability planning requires identifying potential bottlenecks, projecting load growth, and selecting patterns that handle distributed workloads. Design with future capacity in mind and implement phased steps that allow incremental scaling without major refactors.

Yes, core architectural principles like separation of concerns, modularity, and asynchronous communication apply across stacks. However, implementation details vary by framework and platform, so adapt patterns to your specific technology choices and constraints.

Architectural assessment covers code organization, maintainability, extensibility, and alignment with business needs. Evaluate whether the design handles current load, identify scaling bottlenecks, and recommend refactoring patterns or technology updates to address drift from original intent.