osoncode/easygram-producer-bot repository overview

⁠🚀 Producer Bot — Overview

Producer Bot is a Docker-ready Telegram bot that acts as a message relay layer between Telegram and your messaging infrastructure.

Instead of handling updates locally, it forwards every incoming Telegram update directly to a message broker — either Apache Kafka or RabbitMQ — enabling scalable, decoupled bot architectures.

It is designed for zero-code configuration using standard Spring Boot properties, making it extremely easy to deploy and integrate into existing systems.

🌐 Official project site: easygram.osoncode.uz⁠

⁠🧠 Core Idea

This bot follows a producer-only architecture:

• Receives updates from Telegram
• Converts them into JSON
• Publishes them to a message broker
• Does NOT process business logic

👉 All actual bot logic is handled downstream by consumer services

⁠⚙️ Key Features

⁠🔌 Plug-and-play deployment

• Fully Dockerized
• Ready for Docker Compose
• No code changes required

⁠🔄 Flexible update ingestion

Supports:

• Long Polling (default)
• Webhook (production-ready)

⁠📡 Multi-broker support

Works with:

• Apache Kafka
• RabbitMQ

⁠🧩 Configuration-first design

• Everything controlled via .env
• Uses Spring Boot property naming
• No custom config format

⁠🚀 Forward-only mode

• Skips local handlers entirely
• Acts as a pure event producer

⁠🏗️ Architecture

Telegram → Producer Bot → Message Broker → Consumer Bot(s)

⁠🐳 Docker Compose Example (RabbitMQ)

bot:
  image: osoncode/easygram-producer-bot:0.0.5
  build: .
  environment:
    # ── Required — provide in .env file ───────────────────────────────────
    easygram.token: "${easygram.token}"

    # ── Transport: LONG_POLLING (default) or WEBHOOK ──────────────────────
    # easygram.update.transport: WEBHOOK
    # easygram.update.webhook.url: https://example.com/webhook
    # easygram.update.webhook.path: /webhook
    # easygram.update.webhook.secret-token: <secret>

    # ── Messaging ─────────────────────────────────────────────────────────
    easygram.messaging.type: PRODUCER
    easygram.messaging.forward-only: "true"
    easygram.messaging.producer.type: RABBIT
    easygram.messaging.rabbit.exchange: easygram-exchange
    easygram.messaging.rabbit.queue: easygram-updates
    easygram.messaging.rabbit.routing-key: easygram.updates
    easygram.messaging.rabbit.create-if-absent: "true"

    # ── RabbitMQ connection ───────────────────────────────────────────────
    spring.rabbitmq.host: rabbitmq
    spring.rabbitmq.port: "5672"
    spring.rabbitmq.username: rabbit
    spring.rabbitmq.password: rabbit

  ports:
    - "8080:8080"    # only needed for WEBHOOK mode

  depends_on:
    rabbitmq:
      condition: service_healthy

  restart: on-failure

⁠🔄 Supported Deployment Modes

⁠🧱 Use Cases

⁠🧩 Microservices architecture

• auth service
• command handler
• analytics pipeline

⁠📊 Event streaming

• analytics systems
• real-time dashboards
• ML pipelines

⁠⚡ High scalability

• Horizontal scaling via Kafka partitions or RabbitMQ queues
• Multiple consumers per stream

⁠🧪 Example Flow

{
  "update_id": 123456,
  "message": {
    "text": "Hello bot",
    "chat": {
      "id": 987654
    }
  }
}

⁠🔧 Why This Design Matters

Producer Bot transforms Telegram bots into:

• stateless services
• scalable systems
• event-driven pipelines

⁠💡 Summary

Producer Bot = Telegram → Broker bridge

• No business logic
• Fully configurable
• Production-ready
• Built for modern distributed systems