Backend Development 8 min read

Explore SpringBlade 2.0: A Powerful Backend Framework for Rapid Enterprise Development

SpringBlade 2.0 is an open‑source, Spring‑Boot‑based backend framework that combines Spring Cloud, Mybatis, and a suite of tools such as BladeTool, Sentinel, Nacos, Traefik, Docker/K8s, and JWT, while offering front‑end projects Sword (React) and Saber (Vue) and detailed project structure, all under the Apache 2.0 license.

Java Architecture Diary
Java Architecture Diary
Java Architecture Diary
Explore SpringBlade 2.0: A Powerful Backend Framework for Rapid Enterprise Development

Introduction

SpringBlade 2.0 is a product of the RuoMeng technology team, a foundational framework built on Spring Boot 2, Spring Cloud Finchley, Mybatis and other core technologies for quickly constructing medium‑to‑large systems.

SpringBlade aims to create a novel development model by consolidating pain points and production pitfalls and embedding the solutions directly into the framework.

Official Website

Official site: https://bladex.vip

Online Demo

Sword demo: https://sword.bladex.vip

Saber demo: https://saber.avue.top

Backend Project URLs

https://gitee.com/smallc/SpringBlade

https://github.com/chillzhuang/SpringBlade

Frontend Project URLs

https://gitee.com/smallc/Sword

https://gitee.com/smallc/Saber

Main Features & Changes

Adopts a front‑back separation model; the front‑end open‑sources a React‑based framework Sword (React, Ant Design, Umi, Dva).

Also open‑sources a Vue‑based framework Saber (Vue, VueX, Avue, Element‑UI).

The back‑end uses the Spring Cloud stack and provides a highly encapsulated component BladeTool.

BladeTool is published to Maven Central for easy inclusion, reducing project bloat and allowing developers to focus on business logic.

Integrates Sentinel for traffic control, circuit breaking, and load protection.

Uses Nacos as the service registry and configuration center, slimming the project while strengthening module interaction.

Employs Traefik for reverse proxy, automatically applying new configuration files on backend changes.

Deployment can be done with Docker or K8s + Jenkins.

Provides a basic Kong usage solution without deep integration due to OpenResty involvement.

Includes a simple Secure module using JWT for token authentication, extensible with Redis and fine‑grained control.

Before version 2.0, it had nearly a year of stable production, evolving from Camden to Finchley and from fat‑jar to Docker, then to K8s + Jenkins deployment architectures.

Clear module partitioning enforces a standardized micro‑service development model.

Project Structure

SpringBlade

├── blade-auth -- Authorization service

├── blade-common -- Common utility package

├── blade-gateway -- Spring Cloud gateway

├── blade-ops -- Operations center

├── blade-admin -- Spring Cloud admin backend

├── blade-develop -- Code generation

├── blade-service -- Business modules

│ ├── blade-desk -- Workbench module

│ ├── blade-log -- Logging module

│ ├── blade-system -- System module

│ └── blade-user -- User module

├── blade-service-api -- Business module API package

│ ├── blade-desk-api -- Workbench API

│ ├── blade-dict-api -- Dictionary API

│ ├── blade-system-api -- System API

│ └── blade-user-api -- User API

Open Source License

Apache Licence 2.0 (original English text)

Apache Licence is the license used by the well‑known non‑profit Apache organization. It is similar to BSD, encouraging code sharing while respecting authors' copyrights, allowing modifications and redistribution as open‑source or commercial software.

Requirements:

Provide a copy of the Apache Licence to code users.

If you modify the code, note the changes in the modified files.

Derived works must retain the original license, trademark, patent statements, and any other required notices.

If a NOTICE file is included in the distributed product, it must contain the Apache Licence; you may add your own notices but not alter the Apache Licence.

The Apache Licence is also business‑friendly; users may modify the code to meet their needs and release it as open‑source or commercial products.

User Rights

Free for learning, graduation projects, company projects, freelance work, etc.

Code files must retain the relevant license information.

Prohibited Items

Directly selling this project on commercial platforms such as Taobao.

Re‑open‑sourcing code with more than 50% similarity without contacting the author.

Note: If prohibited clauses are discovered, the right to claim an authorization fee of 19,999 is reserved.

Note

Frontend UI project (React): Sword

Frontend UI project (Vue): Saber

Core framework project: BladeTool

Community group: 477853168

Interface

Monitoring Interface Overview

Open Source Recommendations

microservicesSpringBootOpenSourceSpringCloudApacheLicenseBackendFramework
Java Architecture Diary
Written by

Java Architecture Diary

Committed to sharing original, high‑quality technical articles; no fluff or promotional content.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.