Convert Figma logo to code with AI

pig-mesh logopig

↥ ↥ ↥ Follow for updates An RBAC permission management system based on Spring Cloud 2025, Spring Boot 4, and OAuth2.

6,684
1,098
6,684
279

Top Related Projects

Spring Cloud Alibaba provides a one-stop solution for application development for the distributed solutions of Alibaba middleware.

84,985

mall项目是一套电商系统,包括前台商城系统及后台管理系统,基于Spring Boot+MyBatis实现,采用Docker容器化部署。 前台商城系统包含首页门户、商品推荐、商品搜索、商品展示、购物车、订单流程、会员中心、客户服务、帮助中心等模块。 后台管理系统包含商品管理、订单管理、会员管理、促销管理、运营管理、内容管理、统计报表、财务管理、权限管理、设置等模块。

🔥 官方推荐 🔥 RuoYi-Vue 全新 Pro 版本,优化重构所有功能。基于 Spring Boot + MyBatis Plus + Vue & Element 实现的后台管理系统 + 微信小程序,支持 RBAC 动态权限、数据权限、SaaS 多租户、Flowable 工作流、三方登录、支付、短信、商城、CRM、ERP、MES、IM、AI 大模型、IoT 物联网等功能。你的 ⭐️ Star ⭐️,是作者生发的动力!

21,910

eladmin jpa 版本:项目基于 Spring Boot 2.7.18、 Jpa、 Spring Security、Redis、Vue的前后端分离的后台管理系统,项目采用分模块开发方式, 权限控制采用 RBAC,支持数据字典与数据权限管理,支持一键生成前后端代码,支持动态路由

Opensabre是基于SpringCloud2023的微服务开发平台,整合了Spring Security、Springcloud Alibaba等组件。 包含了基础的RBAC权限管理、授权认证、网关管理、服务治理、审计日志等系统管理基础应用。 定义了相关开发规范、风格并落地在服务框架层,开箱即用,支持Docker、Kubenetes的部署。 让项目开发人员快速进入业务开发,而不需过多时间花费在基础架构搭建和编码风格规范上。 目标是建立一套金融级、高安全性的微服务解决方案。

47,660

【低代码v2.0,一句话即可生成整个系统】企业级AI低代码平台,一键生成前后端代码甚至整个系统。 AI Skills 一句话画流程、设计表单、生成报表、大屏。内置 AI应用平台涵盖:AI聊天、知识库、流程编排、MCP插件等,兼容主流大模型。引领AI低代码「Skills 生成 → 在线配置 → 代码生成 → 手工合并->AI修改」开发模式,解决 Java 项目 90% 重复工作,提高效率又不失灵活。

Quick Overview

The pig-mesh/pig repository is a lightweight, fast, and flexible web framework for building modern web applications in Go. It provides a simple and intuitive API for handling HTTP requests, routing, middleware, and more, making it a great choice for developers looking to build scalable and efficient web applications.

Pros

  • Simplicity: Pig is designed to be easy to use and understand, with a clean and concise API that makes it easy to get started.
  • Performance: Pig is built on top of the high-performance net/http package, and is optimized for speed and efficiency.
  • Flexibility: Pig is highly customizable and can be easily extended with middleware and other plugins.
  • Scalability: Pig is designed to be scalable and can handle high-traffic web applications with ease.

Cons

  • Limited Documentation: While the Pig project has a good amount of documentation, it may not be as comprehensive as some other web frameworks.
  • Smaller Community: Pig has a smaller community compared to some of the more popular Go web frameworks, which may make it harder to find support and resources.
  • Fewer Features: Pig is a relatively lightweight framework, which means it may not have as many built-in features as some of the more feature-rich web frameworks.
  • Lack of Widespread Adoption: Pig is not as widely used as some of the more popular Go web frameworks, which may make it harder to find developers who are familiar with the project.

Code Examples

Here are a few examples of how to use Pig in your Go web applications:

  1. Basic HTTP Handler:
package main

import (
    "fmt"
    "net/http"

    "github.com/pig-mesh/pig"
)

func main() {
    r := pig.New()

    r.Get("/", func(c *pig.Context) error {
        _, err := fmt.Fprintf(c.Writer, "Hello, World!")
        return err
    })

    http.ListenAndServe(":8080", r)
}
  1. Routing and Parameters:
package main

import (
    "fmt"
    "net/http"

    "github.com/pig-mesh/pig"
)

func main() {
    r := pig.New()

    r.Get("/users/:id", func(c *pig.Context) error {
        id := c.Param("id")
        _, err := fmt.Fprintf(c.Writer, "User ID: %s", id)
        return err
    })

    http.ListenAndServe(":8080", r)
}
  1. Middleware:
package main

import (
    "fmt"
    "net/http"

    "github.com/pig-mesh/pig"
)

func main() {
    r := pig.New()

    r.Use(func(next pig.HandlerFunc) pig.HandlerFunc {
        return func(c *pig.Context) error {
            fmt.Println("Before request")
            err := next(c)
            fmt.Println("After request")
            return err
        }
    })

    r.Get("/", func(c *pig.Context) error {
        _, err := fmt.Fprintf(c.Writer, "Hello, World!")
        return err
    })

    http.ListenAndServe(":8080", r)
}

Getting Started

To get started with Pig, you can follow these steps:

  1. Install Go on your system if you haven't already.
  2. Create a new Go module for your project:
go mod init your-project
  1. Install the Pig package:
go get github.com/pig-mesh/pig
  1. Create a new file (e.g., main.go) and add the following code:
package main

import (
    "fmt"
    "net/http"

    "github.com/pig-mesh/pig"
)

func main() {
    r := pig.New()

    r.Get("/", func(c *pig.Context) error {
        _, err := fmt.Fprintf(c.Writer, "Hello, Worl

Competitor Comparisons

Spring Cloud Alibaba provides a one-stop solution for application development for the distributed solutions of Alibaba middleware.

Pros of spring-cloud-alibaba

  • More comprehensive ecosystem with a wider range of components for microservices
  • Stronger community support and regular updates from Alibaba
  • Better integration with Alibaba Cloud services

Cons of spring-cloud-alibaba

  • Steeper learning curve due to its extensive feature set
  • Potentially heavier resource consumption for smaller projects
  • Some components may be more tailored for Alibaba Cloud, limiting flexibility

Code Comparison

spring-cloud-alibaba:

@SpringBootApplication
@EnableDiscoveryClient
public class ProviderApplication {
    public static void main(String[] args) {
        SpringApplication.run(ProviderApplication.class, args);
    }
}

pig:

@SpringBootApplication
@EnablePigFeignClients
@EnablePigResourceServer
public class PigAdminApplication {
    public static void main(String[] args) {
        SpringApplication.run(PigAdminApplication.class, args);
    }
}

Both projects use Spring Boot annotations, but spring-cloud-alibaba focuses on service discovery, while pig includes custom annotations for Feign clients and resource server configuration.

84,985

mall项目是一套电商系统,包括前台商城系统及后台管理系统,基于Spring Boot+MyBatis实现,采用Docker容器化部署。 前台商城系统包含首页门户、商品推荐、商品搜索、商品展示、购物车、订单流程、会员中心、客户服务、帮助中心等模块。 后台管理系统包含商品管理、订单管理、会员管理、促销管理、运营管理、内容管理、统计报表、财务管理、权限管理、设置等模块。

Pros of mall

  • More comprehensive e-commerce solution with front-end and back-end components
  • Extensive documentation and learning resources for developers
  • Larger community and more frequent updates

Cons of mall

  • Steeper learning curve due to its complexity
  • May be overkill for smaller projects or simpler e-commerce needs
  • Potentially higher resource requirements for deployment

Code Comparison

mall (Java):

@ApiOperation("Add product to cart")
@RequestMapping(value = "/add", method = RequestMethod.POST)
@ResponseBody
public CommonResult add(@RequestBody OmsCartItem cartItem) {
    int count = cartItemService.add(cartItem);
    if (count > 0) {
        return CommonResult.success(count);
    }
    return CommonResult.failed();
}

pig (Java):

@Inner(false)
@GetMapping("/info/{username}")
public R<UserInfo> info(@PathVariable String username) {
    SysUser user = sysUserService.getOne(Wrappers.<SysUser>query().lambda().eq(SysUser::getUsername, username));
    if (user == null) {
        return R.failed(String.format("用户信息为空 %s", username));
    }
    return R.ok(sysUserService.getUserInfo(user));
}

Both projects use Spring Boot and similar annotation-based approaches, but mall focuses on e-commerce functionality while pig emphasizes microservices and security features.

🔥 官方推荐 🔥 RuoYi-Vue 全新 Pro 版本,优化重构所有功能。基于 Spring Boot + MyBatis Plus + Vue & Element 实现的后台管理系统 + 微信小程序,支持 RBAC 动态权限、数据权限、SaaS 多租户、Flowable 工作流、三方登录、支付、短信、商城、CRM、ERP、MES、IM、AI 大模型、IoT 物联网等功能。你的 ⭐️ Star ⭐️,是作者生发的动力!

Pros of ruoyi-vue-pro

  • More comprehensive documentation and tutorials
  • Larger community and more frequent updates
  • Extensive integration with popular third-party services

Cons of ruoyi-vue-pro

  • Steeper learning curve due to its extensive features
  • Potentially heavier resource consumption
  • May be overly complex for smaller projects

Code Comparison

ruoyi-vue-pro:

@PreAuthorize("@ss.hasPermission('system:user:list')")
@GetMapping("/page")
public CommonResult<PageResult<UserPageItemRespVO>> getUserPage(@Valid UserPageReqVO reqVO) {
    PageResult<AdminUserDO> pageResult = userService.getUserPage(reqVO);
    return success(UserConvert.INSTANCE.convertPage(pageResult));
}

pig:

@GetMapping("/page")
public R getUserPage(Page page, UserDTO userDTO) {
    return R.ok(userService.getUserWithRolePage(page, userDTO));
}

The ruoyi-vue-pro example shows more detailed permission handling and request validation, while pig's code is more concise but may require additional security measures elsewhere in the application.

21,910

eladmin jpa 版本:项目基于 Spring Boot 2.7.18、 Jpa、 Spring Security、Redis、Vue的前后端分离的后台管理系统,项目采用分模块开发方式, 权限控制采用 RBAC,支持数据字典与数据权限管理,支持一键生成前后端代码,支持动态路由

Pros of eladmin

  • More comprehensive documentation and detailed user guide
  • Extensive built-in components and modules for rapid development
  • Active community with frequent updates and bug fixes

Cons of eladmin

  • Steeper learning curve due to its extensive feature set
  • Potentially heavier resource usage for smaller projects
  • Less flexibility for customization compared to Pig's modular approach

Code Comparison

eladmin (Entity class example):

@Entity
@Data
@Table(name="sys_user")
public class User implements Serializable {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;
    private String username;
    private String email;
}

Pig (Entity class example):

@Data
@TableName("sys_user")
public class SysUser implements Serializable {
    private static final long serialVersionUID = 1L;
    @TableId(type = IdType.ASSIGN_ID)
    private Long userId;
    private String username;
    private String email;
}

Both projects use similar annotations for entity classes, but Pig uses MyBatis-Plus annotations while eladmin uses JPA annotations. eladmin's approach may be more familiar to developers with a Spring Data background, while Pig's approach aligns with MyBatis-Plus conventions.

Opensabre是基于SpringCloud2023的微服务开发平台,整合了Spring Security、Springcloud Alibaba等组件。 包含了基础的RBAC权限管理、授权认证、网关管理、服务治理、审计日志等系统管理基础应用。 定义了相关开发规范、风格并落地在服务框架层,开箱即用,支持Docker、Kubenetes的部署。 让项目开发人员快速进入业务开发,而不需过多时间花费在基础架构搭建和编码风格规范上。 目标是建立一套金融级、高安全性的微服务解决方案。

Pros of SpringCloud

  • More comprehensive microservices architecture demonstration
  • Includes detailed documentation and diagrams for system design
  • Implements a wider range of Spring Cloud components

Cons of SpringCloud

  • Less frequent updates and maintenance compared to Pig
  • May be more complex for beginners to understand and implement
  • Lacks some modern features and integrations present in Pig

Code Comparison

SpringCloud (auth-server module):

@Configuration
@EnableAuthorizationServer
public class AuthorizationServerConfig extends AuthorizationServerConfigurerAdapter {
    @Autowired
    private AuthenticationManager authenticationManager;
    @Autowired
    private UserDetailsService userDetailsService;

Pig (auth module):

@Configuration
@EnableAuthorizationServer
@RequiredArgsConstructor
public class AuthorizationServerConfiguration extends AuthorizationServerConfigurerAdapter {
    private final DataSource dataSource;
    private final PigUserDetailsService pigUserDetailsService;

Both projects use Spring Cloud for microservices architecture, but Pig demonstrates a more modern approach with Lombok annotations and constructor injection. SpringCloud provides a more traditional setup, which may be easier for developers familiar with older Spring versions. Pig also includes additional security features and integrations with tools like Swagger and MyBatis-Plus, making it more feature-rich for enterprise applications.

47,660

【低代码v2.0,一句话即可生成整个系统】企业级AI低代码平台,一键生成前后端代码甚至整个系统。 AI Skills 一句话画流程、设计表单、生成报表、大屏。内置 AI应用平台涵盖:AI聊天、知识库、流程编排、MCP插件等,兼容主流大模型。引领AI低代码「Skills 生成 → 在线配置 → 代码生成 → 手工合并->AI修改」开发模式,解决 Java 项目 90% 重复工作,提高效率又不失灵活。

Pros of JeecgBoot

  • More comprehensive documentation and tutorials
  • Stronger focus on low-code development and code generation
  • Larger community and more frequent updates

Cons of JeecgBoot

  • Steeper learning curve due to more complex architecture
  • Potentially slower performance in some scenarios
  • Less emphasis on microservices architecture

Code Comparison

JeecgBoot:

@RestController
@RequestMapping("/test")
@Slf4j
public class TestController {
    @GetMapping("/hello")
    public Result<String> hello() {
        return Result.OK("Hello JeecgBoot!");
    }
}

Pig:

@RestController
@RequestMapping("/test")
@RequiredArgsConstructor
public class TestController {
    @GetMapping("/hello")
    public R<String> hello() {
        return R.ok("Hello Pig!");
    }
}

Both projects use similar Spring Boot annotations and controller structures. JeecgBoot uses a custom Result class, while Pig uses R for wrapping responses. Pig also utilizes Lombok's @RequiredArgsConstructor for dependency injection, whereas JeecgBoot uses @Slf4j for logging.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

Pig Spring Cloud Spring Boot Vue License Stars

系统说明

  • Pig 是基于 Spring Cloud、Spring Boot、OAuth2 的 RBAC 企业级快速开发平台,同时支持微服务架构和单体架构。
  • 认证中心基于 Spring Authorization Server 落地生产级 OAuth2 实践,支持授权码、密码、刷新令牌等常见登录与授权场景。
  • 当前开源版本保留认证、网关、用户权限、监控、代码生成和定时任务等核心能力,移除了商业版中的多租户、数据权限、动态路由、流程、支付、公众号、报表和移动端服务等扩展模块。
  • 提供 Docker Compose 本地编排,支持快速启动 MySQL、Redis、Nacos 和业务服务。

使用文档

PIG 提供了完整的部署与开发文档:wiki.pig4cloud.com,涵盖开发环境配置、服务端启动、前端运行、微服务部署和单体部署等关键步骤。

其他产品

快速开始

基础环境

  • JDK 17+
  • Maven 3.9+
  • Docker 和 Docker Compose
  • Node.js 20.19.0+(运行 pig-ui 前端时需要)

微服务模式

在项目根目录执行完整编译,再构建并启动本地服务栈:

mvn clean install -T 4 -Pcloud
docker compose build && docker compose up

服务启动后,默认通过网关端口 9999 访问后端接口,Nacos 控制台端口为 8848。

单体模式

单体模式通过 boot profile 启用 pig-boot 模块:

mvn clean install -T 4 -Pboot
docker compose -f docker-compose-boot.yml build && docker compose -f docker-compose-boot.yml up

单体服务默认监听 9999 端口。

核心依赖

依赖版本
Pig4.1.0
JDK17+
Spring Boot4.0.6
Spring Cloud2025.1.2
Spring Cloud Alibaba2025.1.0.0
Spring Security OAuth2 Authorization Server7.0.5
MyBatis Plus3.5.16
Nacos Client3.1.2
Druid1.2.28
Vue3.5.34
Element Plus2.13.7
Vite5.4.21

模块说明

pig-ui -- https://github.com/pig-mesh/pig-ui

pig
├── pig-register -- Nacos Server [8848/9848/18080]
├── pig-gateway -- Spring Cloud Gateway 网关 [9999]
├── pig-auth -- 授权服务 [3000]
├── pig-upms -- 通用用户权限管理模块
│   ├── pig-upms-api -- 通用用户权限管理公共 API
│   └── pig-upms-biz -- 通用用户权限业务服务 [4000]
├── pig-common -- 系统公共模块
│   ├── pig-common-bom -- 全局依赖版本管理
│   ├── pig-common-core -- 公共工具类核心包
│   ├── pig-common-data -- MyBatis Plus 与缓存扩展
│   ├── pig-common-datasource -- 动态数据源封装
│   ├── pig-common-log -- 日志服务
│   ├── pig-common-oss -- 文件上传工具类
│   ├── pig-common-security -- 安全工具类
│   ├── pig-common-sentinel -- Sentinel 与异常处理封装
│   ├── pig-common-swagger -- 接口文档封装
│   ├── pig-common-feign -- OpenFeign 扩展封装
│   ├── pig-common-excel -- Excel 导入导出封装
│   └── pig-common-xss -- XSS 安全封装
├── pig-visual -- 可视化支撑服务
│   ├── pig-monitor -- 服务监控 [5001]
│   ├── pig-codegen -- 图形化代码生成 [5002]
│   └── pig-quartz -- 定时任务管理台 [5007]
└── pig-boot -- 单体模式启动器 [9999],通过 `-Pboot` 启用

配置说明

  • 微服务模式使用 cloud profile,默认激活 dev 环境配置。
  • 单体模式使用 boot profile,pig-boot 模块只在该 profile 下参与构建。
  • 网关路由由 pig-gateway/src/main/resources/application.yml 和 Nacos 配置维护,不再依赖动态路由表。
  • 默认数据库脚本位于 db/,业务表初始化到 pig,Nacos 配置初始化到 pig_config。
  • 包名已统一为 com.pig4cloud.pig。

开源共建

开源协议

Pig 开源软件遵循 Apache 2.0 协议,允许商业使用,但务必保留类作者、Copyright 信息。

其他说明

  1. 欢迎提交 PR,请基于当前开发分支提交。
  2. 欢迎提交 Issue,请写清楚问题现象、开发环境和复现步骤。
  3. 代码格式遵循 Spring Java Format,提交前可在项目根目录运行:
mvn spring-javaformat:apply