Skip to content

Architecture ​

Guide ​

This section helps product, delivery, operations, and secondary-development teams quickly understand FastBee's system boundary, technology choices, module responsibilities, and deployment model. The content is consolidated from the architecture notes and reorganized around a practical reading path.

  1. Start with System Architecture Overview to build an overall understanding of platform capabilities and module relationships.
  2. Read Technology Stack and Modules to confirm backend, frontend, database, and middleware choices.
  3. Development teams should continue with Backend Architecture, Frontend Architecture, and Data and Database Architecture.
  4. Delivery and operations teams should focus on Deployment and Operations Architecture and Performance Optimization.
  5. For cluster scenarios, read this section together with Cluster Edition Docs. Cluster deployment, load balancing, and benchmarking are maintained under the cluster edition section.

Common Tasks ​

Scope ​

PageAudienceQuestion Answered
System Architecture OverviewProduct, pre-sales, project ownersWhat FastBee is, what it provides, and how the overall chain works
Technology Stack and ModulesArchitects, development leadsWhich frameworks, middleware, and runtime dependencies are used
Backend ArchitectureBackend developers, extension teamsHow services are divided and how protocols, messages, and rules collaborate
Frontend ArchitectureFrontend developers, delivery teamsHow the admin UI, visualization, configuration, and mobile side are organized
Data and Database ArchitectureDBA, backend developers, operationsHow data is stored, cached, migrated, and backed up
Deployment and Operations ArchitectureDelivery, operations, implementation teamsHow containers are orchestrated and how services are started, exposed, and diagnosed
Performance OptimizationOperations, architects, performance testersHow to establish baselines and keep optimizing

FastBee | fastbee.cn