The key point to keep in mind is that, at the end of the day, your building an application to satisfy a customer. Or to be exact, a list of requirements that may or may not be constantly changing.
In this case from what i'm reading, I am assuming its your hobby project, so the 'customer' is you.
In this case, over-engineering is when you add more functionalities/services than what you needed to hit the bare minimum requirement. Ideally you want to hit basic requirements first, then start designing/engineering on top of what you have when your customer wants more features, etc.
Your design providing more features than the bare minimum should be an 'accident' more than intentional ideally, unless you think the extra feature takes 0% effort to implement. (Though TBH safe rule of thumb is, never design for additional unrequested features)
With the above context in mind, you should be asking the questions:
How much downtime is acceptable? (Usually measured in per year)
How much $ cost in SaaS/API services is acceptable? (per month, or year, etc...)
How much time/money spent in maintenance is acceptable? (Helps in determining the API/Service you are going to use)
Other questions related to acceptable risk/costs, etc...
Yea, welcome to client engineering. Usually its handled by senior developers or project managers, unless your in startup.
TLDR; It's not about finding a design that is perfect, its about finding a design that is acceptable by the involved. What is acceptable? that is for the involved parties to decide.
Aside from the commonly stated - experience:
The key point to keep in mind is that, at the end of the day, your building an application to satisfy a customer. Or to be exact, a list of requirements that may or may not be constantly changing. In this case from what i'm reading, I am assuming its your hobby project, so the 'customer' is you.
In this case, over-engineering is when you add more functionalities/services than what you needed to hit the bare minimum requirement. Ideally you want to hit basic requirements first, then start designing/engineering on top of what you have when your customer wants more features, etc.
Your design providing more features than the bare minimum should be an 'accident' more than intentional ideally, unless you think the extra feature takes 0% effort to implement. (Though TBH safe rule of thumb is, never design for additional unrequested features)
With the above context in mind, you should be asking the questions:
Yea, welcome to client engineering. Usually its handled by senior developers or project managers, unless your in startup.
TLDR; It's not about finding a design that is perfect, its about finding a design that is acceptable by the involved. What is acceptable? that is for the involved parties to decide.