Migrated repository
Go to file
2020-09-30 10:01:27 +08:00
.docker [REV] merge branch 3.7 to master 2018-10-08 12:25:05 +08:00
.github Update issue templates 2020-07-18 23:05:17 +08:00
api Merge branch 'master' into k8s-service 2020-09-30 10:01:27 +08:00
builder Merge branch 'V5.2' 2020-09-25 11:28:58 +08:00
cmd Merge branch 'V5.2' 2020-09-25 11:28:58 +08:00
db update k8s service name 2020-09-27 16:27:46 +08:00
discover init go mod #821 2020-09-06 11:09:48 +08:00
discover.v2 init go mod #821 2020-09-06 11:09:48 +08:00
docs change readme 2020-08-24 21:55:02 +08:00
event init go mod #821 2020-09-06 11:09:48 +08:00
eventlog init go mod #821 2020-09-06 11:09:48 +08:00
gateway Merge branch 'V5.2' 2020-09-25 11:28:58 +08:00
grctl Merge branch 'V5.2' 2020-09-25 11:28:58 +08:00
hack/contrib/docker change resource proxy 2020-09-28 16:23:05 +08:00
monitor Merge branch 'V5.2' 2020-09-25 11:28:58 +08:00
mq init go mod #821 2020-09-06 11:09:48 +08:00
node change some code 2020-09-29 18:46:22 +08:00
test/shell [ADD] support upgrade image name in service config 2019-09-03 13:38:54 +08:00
util update k8s service name 2020-09-27 16:27:46 +08:00
webcli init go mod #821 2020-09-06 11:11:11 +08:00
worker new api for getting app status 2020-09-30 09:50:58 +08:00
.gitignore ignore vendor 2020-09-17 15:47:01 +08:00
.travis.yml add sudo 2020-09-06 12:10:29 +08:00
check.sh [REV] modify some file names 2019-02-12 17:19:42 +08:00
CONTRIBUTING.md Update CONTRIBUTING.md 2020-09-07 09:40:11 +08:00
go.mod Merge branch 'master' into k8s-service 2020-09-30 10:01:27 +08:00
go.mod.edit upgrade client-go to 1.16.3 2019-11-25 16:14:32 +08:00
go.sum new api for getting app status 2020-09-30 09:50:58 +08:00
LICENSE [ADD] init commit 2017-11-07 11:40:44 +08:00
Licensing.md [ADD] init commit 2017-11-07 11:40:44 +08:00
local_release.sh change readme 2020-08-24 21:55:02 +08:00
localbuild.sh merge 2020-09-19 17:17:28 +08:00
Makefile init go mod #821 2020-09-06 11:09:48 +08:00
mockgen.sh [ADD] record OOMKilled 2019-08-26 16:21:48 +08:00
precheck.sh reset precheck.sh 2019-08-30 17:05:03 +08:00
README-zh.md change readme 2020-09-21 18:13:33 +08:00
README.md Update README.md 2020-09-21 18:15:14 +08:00
release.sh Merge branch 'master' into k8s-service 2020-09-30 10:01:27 +08:00

Rainbond GitHub stars Rainbond version Build Status GoDoc

WebsiteDocumentation

notification What is NEW!
August 24, 2020 ,Rainbond 5.2 Stable version is officially released View Release

Rainbond Introduction

Cloud native application management platform

  • Implementing the microservice architecture without changing the code.
  • Manage app in k8s without learning about container techniques.
  • Help enterprises implement application to the cloud, one-stop delivery of any enterprise application to k8s cluster, hybrid cloud, multi-cloud and other infrastructure.

Request Demo

With Rainbond you can:

  • Enterprise cloud native DevOps

Application-oriented DevOps development pipeline, provides the ability to continuously build cloud-native applications from source code or simple image, does not require developers to have containerization capability, developer-friendly, non-intrusive source code, the business continues to release to the cloud.

  • Enterprise microservice governance

Built-in ServiceMesh microservice framework, microservice governance can be used out of the box, and traditional business cloud as a service. Plug-in expansion and enhancement of microservice governance functions, and work in conjunction with microservice frameworks such as SpringCloud Dubbo, effectively lowering the threshold of microservice technology.

  • Kubernetes multi-cloud management

Kubernetes technology is complex and difficult to get started; a large number of deployment, Statefulset, or Operator resource management are complex problems that directly use Kubernetes clusters. Rainbond's application-centric resource management model shields the complexity of Kubernetes, and Kubernetes resources are handed over to Rainbond for orchestration and management.

  • Enterprise Middle Platform Construction and Application Delivery

There are many enterprise business systems, many delivery projects, and many IT products. Build a unified enterprise business center, integrate all digital systems and common component libraries of the enterprise to form digital assets, and efficiently reuse by internal teams. ToB delivery scenarios achieve the greatest level of The combination of automation, standardization and customization.

  • Support multiple CPU architectures

Rainbond has completed two-way authentication with localized computing bases represented by Loongson, Feiteng, and Kirin operating systems, which enables Rainbond to shield the differences in the underlying CPU architecture and operating system and provide users with a unified localized business application management platform.

Rainbond RoadMap

Quick start

  1. Install Rainbond Cluster
  2. Create an Application and Component
  3. Learning concepts
  4. Watch the tutorial video

Community

Rainbond Community You are welcome to read or contribute to the use cases of Rainbond in the community.

Rainbond Website Read more about Rainbond.

Join WeChart

License

Rainbond follow LGPL-3.0 licenseDetails seeLICENSE and Licensing