MusivaDocs

Introduction & Ecosystem Overview

High-level overview of the services, integrations, and infrastructure powering the Musiva ecosystem.

Welcome to the Musiva Developer & Infrastructure Documentation. This documentation platform covers the technical architecture, microservices, third-party music integrations, and managed audio infrastructure that power the Musiva platform.

Musiva is structured around a separation of responsibilities. Instead of tightly coupling audio decoding, metadata retrieval, chart analytics, and player session management inside a monolithic application, Musiva utilizes specialized internal services and an abstraction gateway.


Architectural Pillars


Why Separate Services?

Operating a high-scale music streaming platform requires resilience against rate limits, token expirations, and node downtime. Musiva solves these challenges through modular architecture:

  1. Independent Lifecycle Management: Token managers like the Deezer ARL service and Spotify Tokener maintain their own background renewal loops without restarting the core bot or web application.
  2. Infrastructure Resilience: If a Lavalink node fails or requires operating system maintenance, the Gateway automatically migrates active sessions to healthy nodes without disconnecting Discord voice listeners.
  3. Security by Abstraction: Third-party bot developers and public clients connect exclusively to gateway.musiva.app, preventing exposure of origin node IP addresses and mitigating DDoS risks.
  4. Optimized Audio Quality: Native lossless flac and high-bitrate MP3 decoding from Deezer is integrated directly with fallback logic to Apple Music, Tidal, Spotify, and YouTube.

Quick Navigation

Explore the major sections of this documentation: