- Microstacks minimize build dependencies and avoid runtime service dependencies, unlike projects relying on deep cloud integrations.
- Runtime third-party service dependencies create long-term risks, including vendor lock-in, legal issues, and geopolitical instability.
- Developers often make powerful choices without considering costs, leading to accidental commitments to providers like Microsoft.
- The microstack approach uses simple, self-hosted tools (e.g., SQLite, Alpine.js) for maintainable, low-cost projects.
- Cloud efficiency is questioned, as complex architectures can be fragile and expensive, while microstacks offer predictable costs and control.
- Legal and security risks increase with US cloud dependencies, especially for sensitive data under GDPR.
- The talk recommends 'mesostack' deployments with moderate dependencies for a balanced approach.