Design for Business Requirements

There is no perfect architecture for any application, Architecture must be designed based on the functional and non-functional requirements , here are few mentions before thinking to design architecture for your application

Every design decision must be justified by the business requirements.
Engineers are tend to be over-engineer, by approaching latest architecture styles and patterns .
Application tends to be eventually experimental by incorporating all the latest fancy tools and design patterns.
Drive your architecture by business needs.
Focus on constraints, assumptions and limits of your application and clearly define business requirements .
Start and Grow application with Metrics in mind

How many concurrent users application can handle?

What is the minimum latency expected?

What is the acceptable outage application can have?

Follow the below basic workflow before building or thinking any architecture for an application , Problem -> Learn -> Design -> Adapt -> Evaluate.
Explanation of the Workflow
Problem: Identify the problem that needs to be solved.
Learn: Gather requirements and understand constraints.
Design: Create an initial design and review it with stakeholders.
Adapt: Make necessary adjustments and implement changes.
Evaluate: Test the solution, collect feedback, and iterate if necessary.