cloudrun-development

CloudBase Run Function mode suits standard HTTP backends, while Container mode is necessary for long-running services needing WebSocket/SSE, private networking, custom runtimes, or AI agent development. Mode selection depends on your specific networking and runtime requirements.

To build a scalable CloudBase Run backend with WebSocket support, use Container mode to deploy a custom runtime. This mode supports long-running services and real-time communication protocols like WebSocket and SSE for maintainable backend architectures.

Yes, you can develop AI agents using CloudBase Run by selecting Container mode. This mode provides the necessary long-running service capabilities, custom runtimes, and private networking required to host and scale AI agent applications effectively.

The best way to deploy a custom runtime backend on CloudBase Run is using Container mode. It provides deterministic guidance, step-by-step workflows from initialization to deployment, and security guidelines to ensure production readiness for your services.

Yes, CloudBase Run provides comprehensive security, networking, and resource-management guidelines. These rules ensure your Function or Container mode backend meets production readiness requirements, covering private networking configurations and best practices for deployment.

CloudBase Run Function mode may fail to maintain WebSocket connections because it is not designed for long-running services. For WebSocket or SSE support, you must switch to Container mode, which handles persistent connections and custom runtimes properly.