{"id":25775966,"url":"https://github.com/TencentFemas/femas","last_synced_at":"2025-02-27T06:05:18.253Z","repository":{"id":36971090,"uuid":"462164819","full_name":"TencentFemas/femas","owner":"TencentFemas","description":"JavaAgent-based Microservice Governance Platform","archived":false,"fork":false,"pushed_at":"2023-11-02T10:55:47.000Z","size":624519,"stargazers_count":460,"open_issues_count":55,"forks_count":143,"subscribers_count":11,"default_branch":"develop","last_synced_at":"2023-12-29T16:32:53.948Z","etag":null,"topics":["api-management","apm","authentication","circuit-breaker","javaagent","metrics","microservices","router","service-discovery"],"latest_commit_sha":null,"homepage":"https://zilongtong.notion.site/Femas-Home-4e1ad62bc48d4f23b6063c460a337c40","language":"Java","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/TencentFemas.png","metadata":{"files":{"readme":"README-zh.md","changelog":null,"contributing":"CONTRIBUTING-zh.md","funding":null,"license":"LICENSE","code_of_conduct":"Code-of-Conduct-zh.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null}},"created_at":"2022-02-22T06:17:57.000Z","updated_at":"2023-12-29T16:32:56.944Z","dependencies_parsed_at":"2023-01-17T10:02:18.003Z","dependency_job_id":"be01dcfb-ea7e-4e86-ad6f-bacdddbb940e","html_url":"https://github.com/TencentFemas/femas","commit_stats":null,"previous_names":["tencentfemas/femas","polarismesh/femas"],"tags_count":2,"template":null,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TencentFemas%2Ffemas","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TencentFemas%2Ffemas/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TencentFemas%2Ffemas/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TencentFemas%2Ffemas/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/TencentFemas","download_url":"https://codeload.github.com/TencentFemas/femas/tar.gz/refs/heads/develop","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":240987435,"owners_count":19889333,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["api-management","apm","authentication","circuit-breaker","javaagent","metrics","microservices","router","service-discovery"],"created_at":"2025-02-27T06:01:15.533Z","updated_at":"2025-02-27T06:05:18.246Z","avatar_url":"https://github.com/TencentFemas.png","language":"Java","funding_links":[],"categories":["微服务治理"],"sub_categories":[],"readme":"\u003cimg src=\"https://user-images.githubusercontent.com/22976760/153148783-0ce5ae2f-cc36-4217-8f80-b29a2930b593.png\" width=\"400px\"\u003e\n\n# Femas：腾讯云开源微服务治理平台\n\n**[`English`](./README.md) | `简体中文`**\n\n\n- [简介](#简介)\n     - [能力](#能力)\n     - [特色](#特色)\n- [快速入门](#快速入门)\n     - [安装服务端](#安装服务端)\n     - [单机部署](#单机部署)\n     - [集群部署](#集群部署)\n     - [Springcloud接入](#springcloud接入)\n         - [样例](#样例)\n         - [添加依赖](#添加依赖)\n         - [配置文件](#配置文件)\n         - [启动服务命令](#启动服务命令)\n- [Dubbo接入](#dubbo接入)\n     - [样例](#样例)\n- [文档](#文档)\n     - [官方文档](#官方文档)\n     - [常见问题](#faq)\n     - [贡献手册](#贡献手册)\n     - [行为准则](#行为准则)\n- [参与贡献](#参与贡献)\n- [联系我们](#联系我们)\n- [许可证](#许可证)\n\n## 简介\n**Femas 是腾讯云微服务平台[TSF](https://cloud.tencent.com/product/tsf) 的开源产品形态，聚焦微服务运行时，提供给多框架统一服务发现、南北及东西流量治理、服务可观测、配置管理等一站式微服务管控能力，解决企业微服务架构转型中异构框架复用难、 激增流量管控难、排障恢复耗时长等核心问题。**\n\n\u003e - 治理数据面：`Femas`运用`Multi-runtime`的架构设计，将微服务底层的核心能力标准化、模块化，将微服务领域割裂的基础组件通过合理的架构组装在一起，来满足多元化的微服务场景，轻量化、可移植、低成本、无云厂商绑定，目前社区提供`SDK`和业务无感知的`JVM TI Agent`两种`proxyLess`模式的治理数据面。\n\u003e - 微服务控制面：Femas提供统一的控制面标准协议，一套治理协议，多语言、多数据面下发。\n\n### 能力\n![image](https://user-images.githubusercontent.com/22976760/153163444-aa444552-8fe9-486d-9e6e-4d1cd2f00836.png)\n\n- 注册中心管理：\nFemas实现了对主流开源注册中心(目前支持`Consul、nacos、eureka`)的管理，包括集群管理，服务管理，用户在Paas平台配置注册中心集群，即可查看集群状态和服务列表。\n- 服务治理：**`鉴权`、`API管理`、`熔断降级`、`访问限流`、`服务注册发现`、`服务路由`、`服务事件`**。\n- 服务配置：应用配置管理、配置热更新，Femas实现了一套标准的配置API接口，配置分为`治理规则`、`应用配置`，**开源侧支持通过Paas平台直接下发`治理规则`，不依赖其他三方组件**。\n- 服务注册发现：Femas实现了一套标准的注册发现API接口，用户可以直接使用Femas提供的SDK注册发现到主流的开源注册中心。\n- 服务监控：\n    - \u003e Metrics:Femas实现了一套标准的业务Metrics指标的API接口，Femas默认使用`micrometer`实现业务Metrics统计；\n    - \u003e Tracing:实现了一套标准的tracing API接口，SDK侧负责制定OpenTracing日志规范和链路采集。由于业界可观测的统一标准Opentelemtry在发展阶段，第一阶段默认使用SkyWalking agent采集Tracing信息。\n\n### 特色\n\n- 提供 `Java` 与 `Go` 的 SDK，帮助用户在同一套Paas平台上实现**多语言**统一管理。\n- Femas将微服务能力标准化封装，提供无关协议的统一接入`Layer`层，方便将全套能力接入任意协议，实现**多协议的统一管理**。\n- Femas将一个微服务应用在运行过程中可能需要用到的能力抽象成了一个个标准`API`组件，方便扩展，兼容其他开源组件生态。\n- Femas的底层能力`插件化`，`标准化`，用户可按需要灵活组合搭配微服务能力矩阵。\n- Femas不绑定任何特定组件，只要是符合Femas标准化协议的组件都能纳管到Femas平台，方便各个层级的用户学习、使用以及二次开发。\n![image](https://user-images.githubusercontent.com/22976760/157235354-27819b3c-69f1-4ad1-95e0-c82d2be99272.png)\n\n- **下沉式无侵入接入，用户改造零成本**。\n\t\u003e - `Java Agent`字节码注入\n\t\u003e - `ServiceMesh`服务网格（TODO）\n- Femas希望能够将腾讯微服务产品中心对微服务的理解总结成平台，帮助用户快速搭建企业级微服务生态。\n- Femas支撑了腾讯内部亿级用户生态。\n## 快速入门\n\n### 代码结构\n\n```\n.\n├── femas-adaptor # paas平台插件化适配层\n│   └── femas-adaptor-opensource-admin # paas平台适配层，这里默认是跟开源平台的适配，如果要对接其他控制面，可以插件化实现一个adaptor，其次在这里可以组装平台所需要的能力矩阵\n├── femas-admin # 控制台\n├── femas-admin-starter # 控制台打包部署文件\n├── femas-agent # java agent模块\n│   ├── femas-agent-core # javaagent bytebuddy封装模块\n│   ├── femas-agent-example\n│   ├── femas-agent-plugin #字节码插装插件模块\n│   ├── femas-agent-starter #premain入口\n│   └── femas-agent-tools\n├── femas-api #微服务生命周期抽象层，方便用户对接异构rpc框架\n├── femas-benchmark\n├── femas-common #工具包\n├── femas-config #配置模块插件化的抽象层\n├── femas-config-impl #配置模块的实现层\n│   ├── femas-config-consul #consul配置实现\n│   ├── femas-config-nacos #nacos配置实现层\n│   └── femas-config-paas #开源控制台的配置实现层，开源数据面和控制面的治理规则交互\n├── femas-dependencies-bom # 统一管理femas依赖版本\n├── femas-example #示例\n│   ├── feams-example-springcloud-hoxton\n│   ├── femas-example-alibaba-dubbo-consumer\n│   ├── femas-example-alibaba-dubbo-provider\n│   ├── femas-example-springcloud-2020-consumer\n│   ├── femas-example-springcloud-2020-provider\n│   ├── femas-example-springcloud-greenwich-consumer\n│   ├── femas-example-springcloud-greenwich-gateway\n│   ├── femas-example-springcloud-greenwich-provider\n│   └── femas-example-springcloud-greenwich-zuul\n├── femas-extensions #sdk对接RPC框架层\n│   ├── femas-extension-dubbo #对接dubbo\n│   └── femas-extension-springcloud #对接springcloud\n├── femas-governance #治理模块的插件化抽象层\n├── femas-governance-impl #治理模块的实现层\n├── femas-helm\n├── femas-registry #注册中心插件化抽象层\n├── femas-registry-impl #注册中心插件化的实现层\n│   ├── femas-registry-consul\n│   ├── femas-registry-etcd\n│   ├── femas-registry-eureka\n│   ├── femas-registry-k8s\n│   ├── femas-registry-nacos\n│   └── femas-registry-polaris\n├── femas-starters #用户的sdk的starter依赖\n│   ├── femas-dubbo-starters\n│   └── femas-springcloud-starters\n└── jacoco-aggregate\n```\n\n### 安装服务端\n\n运行环境依赖：\n\n\u003e 64 bit OS，支持 Linux/Unix/Mac/Windows，脚本启动支持Linux/Unix/Mac；\n\n\u003e 64 bit JDK 1.8+；\n\n\u003e Maven 3.2.x+；\n\n\u003e 外接数据库Mysql（可选）\n\n### 单机部署\n\n源码编译方式启动：\n```\nmvn -Dmaven.test.skip=true clean install -U\n\ncd femas-admin-starter/target/femas-admin-starter-$version/femas-admin/bin\n\nsh startup.sh\n```\n\n控制台配置：\n项目配置文件在`femas-admin/conf`目录下\n\u003e cd femas-admin-starter-$version/femas-admin/conf\n\n控制台配置主要包含：\n- 服务端口\n- 数据库配置(如果使用内嵌数据库则不需要配置)\n- nacos地址配置(如果使用配置管理则需要配置)\n- skywalking web地址配置(获取链路信息需要配置)\n- grafana地址配置(获取metrics信息需要配置)\n\n默认使用内嵌数据库启动，一键开箱即用，无需依赖第三方存储组件:\n\u003e 内嵌数据库仅支持单机部署，暂不支持集群部署，内嵌数据库数据存储的磁盘路径为`${user.home}/rocksdb/femas/data/`\n\n\u003e 启动脚本:sh startup.sh\n\n需要用到监控能力则需要以下配置：\n```\n#配置skywalking后端地址（在此之前你必须有部署好的Skywalking集群）\nfemas:\n  trace:\n    backend:\n      addr: http://skywalking WEB IP:PORT\n#配置Metrics grafana地址 （在此之前你必须有部署好的grafana、promethus）\n  metrics:\n    grafana:\n      addr: http://IP:PORT\n```\n\n### 集群部署\n\n集群部署同单机部署，唯一区别是数据源必须是外接数据源，使femas的server端支持无状态水平扩展\n\n配置文件配置数据源\n```\nspring:\n  datasource:\n    url: jdbc:mysql://IP:3306/adminDb?useUnicode=true\u0026characterEncoding=utf8\u0026rewriteBatchedStatements=true\u0026useSSL=false\u0026serverTimezone=Asia/Shanghai\n    username: username\n    password: password\n    hikari:\n      driver-class-name: com.mysql.cj.jdbc.Driver\n```\n\n启动命令为\n\u003e sh startup.sh external \n\n\n**访问`http://localhost:8080/index`即可看到控制台页面**\n\u003e 登陆用户名:admin，密码:123456，用户名密码写死，开源侧不做任何权限限制。\n\n### 服务接入paas平台前准备\n\n#### step 1.配置注册中心 (在此之前你必须有已经部署好的注册中心集群，Femas不绑定任何注册中心，你可以将任意注册中心托管到Femas平台)\n\u003cimg width=\"804\" alt=\"image\" src=\"https://user-images.githubusercontent.com/22976760/156726829-ff8380d1-0a28-426a-8cbb-1398a69f9cb4.png\"\u003e\n\n\u003e 集群地址支持IP:prot逗号隔开，或者域名方式\n\n#### step 2.创建命名空间\n\u003cimg width=\"1643\" alt=\"image\" src=\"https://user-images.githubusercontent.com/22976760/156727253-834f560f-e147-4217-9203-4b0cbd4e5575.png\"\u003e\n\n\u003e 命名空间绑定配置的注册中心\n\n\u003e femas治理中心的服务列表是以命名空间维度逻辑隔离，服务列表从第三方注册中心拉取，拉取条件是接入FemasSDK且服务标记（下文中通过—D写入的命名空间ID）的命名空间和列表选取的命名空间一致。\n\n完成以上两步之后，接下来就可以通过SDK接入femas将服务纳管到paas平台了。\n\n\n### Springcloud接入\n\n##### [样例](./femas-example/)\n\n在femas父pom下执行脚本：\n\u003e mvn -Dmaven.test.skip=true clean install -U \n\n\n##### 添加依赖\n```\n\u003c!-- 注册中心原生依赖 --\u003e\n\u003cdependency\u003e\n    \u003cgroupId\u003eorg.springframework.cloud\u003c/groupId\u003e\n    \u003cartifactId\u003espring-cloud-starter-consul-discovery\u003c/artifactId\u003e\n    \u003cversion\u003e2.1.2.RELEASE\u003c/version\u003e\n\u003c/dependency\u003e\n \n\u003c!-- femas中间件依赖 --\u003e\n\u003cdependency\u003e\n    \u003cgroupId\u003ecom.tencent.tsf\u003c/groupId\u003e\n    \u003cartifactId\u003efemas-springcloud-greenwich-starter\u003c/artifactId\u003e\n    \u003cversion\u003e${femas.latest.version}\u003c/version\u003e\n\u003c/dependency\u003e\n```\n目前femas支持starter列表目录：cd femas-starters/\n\n默认支持的版本组件有：\n- springcloud greenwich\n- springcloud 2020\n- springcloud gateway\n- springcloud zuul\n\n#### 配置文件\n##### 业务应用原生配置文件，路径为:resources/bootstrap.yaml\n```\nserver:\n  port: 18001\nspring:\n  application:\n    name:\n      femas-springcloud-consumer\n  cloud:\n    consul:\n      host: 127.0.0.1\n      port: 8500\n      discovery:\n        serviceName: femas-springcloud-consumer\n        instanceId: ${spring.application.name}-${server.port}-${spring.cloud.client.hostname}\n        heartbeat:\n          enabled: true\n#    nacos:\n#      discovery:\n#        server-addr: 127.0.0.1:8848\n ```\n ##### Femas组件配置文件路径：resources/femas.yaml（Ymal格式，用于配置femas相关本地配置，如paas地址、自定义注册中心集群、自定义治理规则等）\n ```\n# 配置paas后台地址，如果没有配置，则从本地配置文件获取规则\npaas_server_address: http://127.0.0.1:8080\nfemas_namespace_id=命名空间ID  //服务需要指定所属命名空间\nfemas_prog_version=服务版本   //指定服务所属的版本（部署组），配合sdk侧的实现服务治理，如流量分拨路由\n \n# 使用Femas提供的方式接入注册中心，dubbo或者自研协议的使用方式\nfemas_registry_ip: 127.0.0.1  //注册中心集群地址\nfemas_registry_port: 8500\t//注册中心端口号\t\nfemas_registry_type: consul\t//注册中心类型\n\n#以下配置可选，用于配置加载基础组件类型及本地治理规则，不加则加载femas默认配置。\nrateLimit:\n  type: femasRateLimit\nauthenticate:\n  type: femasAuthenticate\nserviceRouter:\n  chain:\n    - FemasDefaultRoute\nloadbalancer:\n  type: random\ncircuitBreaker:\n  enable: true\n  chain:\n    - femasCircuitBreaker\n```\n\n##### 启动服务命令\n```\n# 有监控需求的用户按需添加，非必须\n-javaagent:\"{skywalking agent绝对路径}/agent/skywalking-agent.jar\"  // 引用skywalking的agent探针\n-Dskywalking.agent.service_name=注册到skywalking上的服务名，需要跟注册中心名称一致,否则tracing链路观测会找不到相应服务。\n-Dskywalking.collector.backend_service=skywalking 后端地址，可以覆盖agent的conf配置\n```\n\n### Dubbo接入\n\n##### [样例暂时未放开](./)\n\u003e 详情参见下文官方文档\n\n## 文档\n#### [官方文档](https://zilongtong.notion.site/Femas-Home-4e1ad62bc48d4f23b6063c460a337c40)\n#### [FAQ](https://zilongtong.notion.site/FAQ-c5ac338be9d948bfb36bc7c3025837ca)\n#### [贡献手册](./CONTRIBUTING.md)\n#### [行为准则](./Code-of-Conduct.md) \n\n\n## 参与贡献\n\u003e - 积极参与 Issue 的讨论，如答疑解惑、提供想法或报告无法解决的错误（Issue）\n\u003e - 撰写和改进项目的文档（Wiki）\n\u003e - 提交补丁优化代码（Coding）\n\n**你将获得**\n\u003e - 加入腾讯开源项目贡献者名单，并展现在腾讯开源官网\n\u003e - 写入具体项目的 [CONTRIBUTING.md](./CONTRIBUTING.md)\n\u003e - 腾讯开源贡献者证书（[电子版\u0026纸质](https://opensource.tencent.com/img/example.jpg)）\n\u003e - 成为线下技术大会/沙龙特邀嘉宾\n\u003e - Q币及纪念品\n\n## 联系我们\n\n![群微信号](https://user-images.githubusercontent.com/22976760/177910313-2521275e-e1ed-4358-87ff-1f559b0143ec.jpg)\n\n\n添加微信，备注【Femas】\n\n![微信号](https://user-images.githubusercontent.com/22976760/177910329-1e396bad-d5a2-4d32-8d4b-70fbc361f073.jpg)\n\n\n## 许可证\n[LICENSE.](./LICENSE)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FTencentFemas%2Ffemas","html_url":"https://awesome.ecosyste.ms/projects/github.com%2FTencentFemas%2Ffemas","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FTencentFemas%2Ffemas/lists"}