How NBF’s FaaS Architecture Powers Serverless at Alibaba’s Mega Sales

1. NBF Overview

NBF (New‑Retail Business Framework) is a new‑retail service open framework developed by the supply‑chain middle‑platform team, providing standardized business definitions, rapid service development, and ecosystem openness, delivering a complete PaaS/SaaS solution for partners.

2. FaaS Definition

FaaS (Function as a Service) is a typical Serverless model that offers load balancing, high availability, automatic scaling, and service governance as transparent best‑practice capabilities, allowing developers to focus on business logic and reduce time‑to‑market.

3. Typical FaaS Architecture

Key components include Event Sources, Function Instances, FaaS Controller (e.g., API Gateway or BFF), and Platform Services such as permission management and object storage.

4. NBF‑FaaS Architecture

The architecture consists of three layers:

Serverless Platform – CSE (Cloud Service Engine) : Provides millisecond‑level auto‑scaling, cold‑start and hot‑start optimizations, and integrates with logging, monitoring, and tracing tools.

NBF Container : An OSGi‑based container that manages the full lifecycle of Bundles (load, start, unload, deregister) and ensures isolation and communication.

Platform Capabilities : Service publishing, routing (polymorphic, downgrade, mock), version management, and Serverless operations such as mixed deployment, gray release, and disaster recovery.

4.1 Bundle Lifecycle Management

The NBF container handles Bundle loading, starting, unloading, and deregistration, using OSGi mechanisms to isolate each Bundle and provide import/export capabilities.

4.2 Service Publishing

Publishing a Bundle as a service follows three steps: load the Bundle according to the routing table, start it via the NBF framework, and load the corresponding publishing Plugin.

4.3 Service Routing and Control – Broker

The Broker separates SPI from its implementation, supports dynamic loading of implementations, and provides proxy‑based, annotation‑driven service calls such as @Autowired ServiceA serviceA; or @DynamicInject ServiceA serviceA;. It also handles service discovery, URI generation, and routing calculations based on bundle version, ID, or custom rules.

4.4 Fault Tolerance and Traffic Management

Passive downgrade routes calls to a fallback Bundle when the primary service is unavailable, while active circuit‑breaker triggers based on baseline metrics. Traffic control allows fine‑grained split ratios between primary and fallback Bundles.

5. High‑Availability Operations

5.1 Serverless Capabilities

Millisecond‑level auto‑scaling, fast cold start (reducing startup to Bundle install/start only), and fast hot start (refreshing in‑memory variables) enable the platform to handle peak traffic during large‑scale promotions.

5.2 Rapid Rollback

Rollback is achieved by reloading a specific Bundle version without rebuilding the entire application, thanks to the persistent NBF Engine.

6. Summary

NBF implements a non‑typical FaaS architecture that nonetheless provides all core FaaS features, including containerized Bundle management, service publishing, routing, fault tolerance, auto‑scaling, and rapid rollback, proving its reliability in high‑traffic events such as Alibaba’s Double‑12 and “Queen’s Day” promotions.