RuBaRu Whitepaper
Main Website
  • Abstract
  • RuBaRu - Why & What?
    • Portal
    • Problem Statement
    • What future holds for Social Media and Content Platforms?
    • Why RuBaRu?
    • Key Stakeholders
    • Core Components of Protocol
      • Fully OnChain Profile, Social Graph & Interactions
      • Decentralized Identity(DiD)
      • Fully On-Chain Rich Media Cloud: Decentralized Storage & Streaming
      • Incentive Program
      • Decentralized Creator Economy
      • Creator/Influencer Reputation Factor
      • Decentralized AI (#DeAi) Layer
      • Content Moderation
      • Brand Positioning
      • DAO Governance
    • Economy
      • Creator-Consumer Incentive Program (CCIP)
        • Join-2-Earn
        • Post-2-Earn
        • Refer-2-Earn
        • Engage-2-Earn
        • Advocate-to-Earn
        • Viral-to-Earn
        • Moderate-to-Earn
      • Creator Monetisation
      • Platform Monetisation
    • Technical Architecture & Breakthroughs
      • High level Architecture Overview
      • On-Chain Social Graph
      • On-Chain Authentication & Identity Layer
      • On-Chain Media & Content Infrastructure Layer(CDN)
      • On-Chain Feed Generation, Recommendation & Delivery Pipeline
      • OnChain Reward Wallet & Transaction Layer
      • On-Chain Content Indexer & Search Layer
      • On-Chain Referral Service
      • Decentralised AI Service layer
      • On-Chain Notification Layer
      • User Experience & Interface Layer (Frontend)
      • Off-Chain Components
        • Push Notification Broker Engine (Off-Chain)
        • Leaderboard Reverse Oracle Service
    • Tokenomics
      • Distribution Model
      • Token Utility
        • Credits : In-App Currency
        • $TOKEN (Governance & Value Capture Token)
      • Airdrop Season#1
      • Airdrop Season#2
    • Marketing & Go-To-Market Strategy
    • Try RuBaRu DApp
    • Roadmap
    • Community
    • Conclusion
    • Disclaimer
    • Quickstart
    • Publish your docs
  • Basics
    • Editor
    • Markdown
    • Images & media
    • Interactive blocks
    • OpenAPI
    • Integrations
Powered by GitBook
On this page
  1. RuBaRu - Why & What?
  2. Technical Architecture & Breakthroughs
  3. Off-Chain Components

Push Notification Broker Engine (Off-Chain)

Updated: 8th March 2025

PreviousOff-Chain ComponentsNextLeaderboard Reverse Oracle Service

Last updated 2 months ago

The Push Notification Broker Engine is an off-chain microservice that fetches on-chain notifications from RuBaRu’s Notification Orchestrator Canisters & Notification Satellite Nodes, processes them, and delivers real-time push notifications via Firebase Cloud Messaging (FCM) to Android/iOS devices. This ensures instant updates, even when the app is inactive.

Key Functions

✅ Fetch On-Chain Notifications – Notification Poller in Broker service Queries Notification Orchestrator & Notification Satellite Canisters for user alerts. ✅ Process & Queue – Uses Kafkaesque for message queuing and Redis for real-time caching. ✅ Push Delivery – Sends notifications via FCM, ensuring engagement even when the app is closed. ✅ User-Controlled – Opt-in settings allow users to enable/disable push notifications.

Tech Stack

Java Spring Boot (Backend) | Kafkaesque (Queue) | Redis (Cache) | PostgreSQL (Storage) | Firebase Cloud Messaging (FCM) (Push Service)

This scalable, fault-tolerant system bridges the gap between on-chain events and off-chain engagement, ensuring seamless, real-time notifications while maintaining decentralization goals.

Note: Users would be able to opt out of the off-chain component by disabling push notifications within the DApp.