ā€‹
Introduction

Building a high-performance, low-latency UI for the Neurobro Agent service presents significant technical challenges. Our architecture is designed to efficiently distribute workloads, manage state, and optimize inter-service communication.

ā€‹
System Architecture

The Neurobro Terminal comprises four primary services:

Neurobro UI

Next.js frontend for user interactions

Neurobro Backend

FastAPI service for request handling

Neurobro Agent

Core intelligence service

Neurobro Signals

Orchestrator of signals generation and distribution

ā€‹
Communication Flow

0. Signal Generation

Neurobroā€™s signal generation pipeline:

  1. Neurobro analyzes market data and generates trading signals
  2. Signals are stored in MongoDB for persistence
  3. Backend caches signals in Redis for high-speed access
  4. UI retrieves latest signals from Backend via optimized API
  5. Users can select relevant signals to initiate targeted conversations

1. Request Initiation

User submits request via UI. Both user queries and signals are supported.

2. Authentication

Backend authenticates and forwards to RabbitMQ

3. Processing

Agent service executes workflows via Nevrons

4. Response

Real-time streaming of results back to UI

ā€‹
Core Tech

Message Broker

RabbitMQ

Relational Database

PostgreSQL

Document Database

MongoDB

Cache

Redis

Vector Store

Qdrant

SSL security

HTTPS via Traefik

ā€‹
Detailed Service Breakdown

ā€‹
Scalability & Performance

Since the Neurobro Agent is a single instance, which is not scalable, we found a way to distribute the workload across multiple orchestrators of the swarm of nevrons.

Load Distribution

RabbitMQ workload balancing

Auto-scaling

Multiple agent replicas

Low Latency

RPC streaming

ā€‹
Additional Resources

Nevron Documentation

Learn more about the Nevron framework

Development Roadmap

Future enhancements and updates

For technical support or architecture discussions, join our developer community.