add-microservice

To set up a microservice architecture with a shared DaaS backend, run the command 'add-microservice [service name] [domain]' to automate the creation of domain-based collections and API proxy routes for your new micro-app.

Yes, you need Supabase to manage authentication for DaaS microservices. The architecture requires Supabase specifically for backend authentication alongside the DaaS backend to properly secure and route your micro-apps.

Yes, you can compose multiple micro-apps into a single user interface using Next.js through iframe composition. Micro-apps are integrated via iframe in the Main App to maintain a consistent user experience across the shared backend.

The best way to isolate data collections for separate micro-apps in a DaaS environment is using domain-based collections. This approach assigns each micro-app its own domain of collections within the single shared DaaS backend.

API proxy routes work for micro-apps sharing a single backend by providing each micro-app with its own dedicated proxy route. This ensures seamless integration and secure data routing between the micro-apps and the shared DaaS infrastructure.

No, you cannot use add-microservice without a DaaS backend setup. The Skill explicitly requires an active DaaS backend and Supabase for authentication to automate the microservice architecture setup and API proxy configuration.