Why should you care?

Applies microservices, service discovery, API gateway, and GitOps for a customer-facing SaaS CRM module.

See it live — copy this example

Use AWS/Azure/GCP free tier or local Docker/Kind. Sketches and YAML are meant to be typed and adapted.

# CloudVerse CRM services
# contacts-api, deals-api, activity-worker
# Gateway: /crm/v1/* ; OAuth2 client credentials for partners
# Event: deal.won → billing-api subscriber
apiVersion: v1
kind: Service
metadata:
  name: contacts-api
spec:
  selector: { app: contacts-api }
  ports: [{ port: 80, targetPort: 8080 }]
---
# GitOps path: apps/crm/overlays/prod

What happened?

• CRM data is tenant-scoped; async workers handle email ingestion without blocking UI APIs.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Deploy contacts + deals services.
2. Expose via gateway with OAuth.
3. Publish deal.won test event.
4. Add full-text search service.
5. build webhook subscriptions for tenants.

Remember

Microservices by domain. Events for side effects. Gateway for partners.

CloudVerse sales CRM

Sales team closes deal in mobile app.

Outcome: deal.won triggers invoice draft in billing automatically.