Design and Architecture
Software is designed to run in production from the start, not cleaned up later.
Requirements
- Integrate through contracts. Systems connect with each other through documented, versioned APIs or a shared middleware layer, never directly to each other's databases.
- Plan for load and failure. Expected load and response-time targets are stated before building. Timeouts, retries and partial outages are handled without losing data.
- Protect personal data by design. Collect only the personal data a feature needs, record where it is stored, and follow the data-residency rules for the region it comes from.
- Publish privacy and terms of service links. Before it goes public, any project that collects user data must link to a privacy policy and to terms and conditions. This is not a mere formality, the product must actually adhere to the policies published there.
- Make it observable. Production services write logs, expose health checks, alert on errors and keep tested backups of the data they own.
- Use supported foundations. Runtimes, frameworks and base images are on versions that still receive security fixes.
Recommendations
- Put external services (AI models, speech, storage, payments) behind an interface, so a provider can be swapped if its price, quality or availability changes.
- Choose the simplest design that meets the requirement.
- Ship small working increments to staging early instead of perfecting one part on its own.