Skip to main content

Use Cases

Web APIs and Services​

Molnett excels at running HTTP-based services like REST APIs, GraphQL endpoints, and microservices. The platform automatically provides HTTPS endpoints and handles service discovery, making it simple to build distributed systems.

Example: E-commerce API

name: product-api
containers:
  - name: api
    image: mycompany/products:v1.2.0
    ports:
      - target: 8080
        publish: true
    secrets:
      - key: DATABASE_URL
        value: production-db-url

Modern Web Applications​

Server-side rendered applications built with frameworks like Next.js, Nuxt, or Django work well on Molnett. The platform handles static asset serving and provides the compute resources needed for dynamic rendering.

Single-page applications that need backend APIs benefit from Molnett's simple deployment model. Deploy your frontend and backend services together with consistent configuration.

Development and Testing Workflows​

Molnett's environment isolation makes it ideal for development workflows. Create separate environments for feature development, testing, and production without complex setup.

You can clone existing environments to test changes against real data and configuration. This is particularly useful for testing database migrations or configuration changes.

Example: Environment cloning and deployment

# Clone staging environment for testing
molnctl envs create test-pr-1 --copy-from staging

# Deploy your changes to the cloned environment
molnctl deploy --env test-pr-1

# Deploy stable version to production  
molnctl deploy --env production

Each environment gets its own isolated network and can use different container images or configuration. This makes it safe to test breaking changes without affecting other work.

Microservices Architecture​

Molnett's service discovery and networking make it straightforward to build microservices. Services within the same project can communicate using simple DNS names without complex service mesh configuration.

The platform's environment isolation allows you to test service interactions safely in development before deploying to production.

Example: Microservices setup

# User service
name: user-service
containers:
  - name: api
    image: mycompany/users:latest
    ports:
      - target: 3000
        publish: true

---
# Order service that calls user service
name: order-service  
containers:
  - name: api
    image: mycompany/orders:latest
    ports:
      - target: 3001
        publish: true
    environment:
      - key: USER_SERVICE_URL
        value: "http://user-service:3000"

When to Consider Alternatives​

Molnett works best for stateless applications or those that use external databases and storage. Applications requiring large amounts of persistent storage should wait for object storage availability or use external storage services.

CPU-intensive applications that need specialized hardware (like GPUs) or applications requiring Windows containers should consider alternatives that support those specific requirements.