Migrated repository
Go to file
2020-12-01 13:26:07 +08:00
.docker [REV] merge branch 3.7 to master 2018-10-08 12:25:05 +08:00
.github change github action config 2020-11-27 09:32:39 +08:00
api exclude non-container and non-gateway metrics 2020-11-27 17:48:53 +08:00
builder Merge branch 'master' into V5.2 2020-11-25 07:33:56 -06:00
cmd format code 2020-11-25 16:39:38 +08:00
db format code 2020-11-25 16:39:38 +08:00
discover format code 2020-11-25 16:39:38 +08:00
discover.v2 format code 2020-11-25 16:39:38 +08:00
docs change readme 2020-08-24 21:55:02 +08:00
event format code 2020-11-25 16:39:38 +08:00
eventlog format code 2020-11-25 16:39:38 +08:00
gateway make ssl_protocols configrable 2020-12-01 13:26:07 +08:00
grctl format code 2020-11-25 16:39:38 +08:00
hack/contrib/docker make ssl_protocols configrable 2020-12-01 13:26:07 +08:00
monitor format code 2020-11-25 16:39:38 +08:00
mq format code 2020-11-25 16:39:38 +08:00
node format code 2020-11-25 16:39:38 +08:00
test/shell [ADD] support upgrade image name in service config 2019-09-03 13:38:54 +08:00
util format code 2020-11-25 16:39:38 +08:00
webcli format code 2020-11-25 16:39:38 +08:00
worker status for legacy app 2020-11-26 13:26:02 +08:00
.gitignore Merge branch 'master' into V5.2 2020-11-25 07:33:56 -06:00
check.sh add pr check code job 2020-11-25 21:25:34 +08:00
CONTRIBUTING.md Update CONTRIBUTING.md 2020-09-07 09:40:11 +08:00
go.mod parse environment variables 2020-11-17 09:25:56 +08:00
go.sum delete addOrUpdateEnvs 2020-10-23 14:11:19 +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-11-25 14:38:41 +08:00
README.md change readme 2020-11-25 14:38:41 +08:00
release.sh support no tty build 2020-11-25 17:03:05 +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 and easy-to-use application management platform

Rainbond is a cloud native and easy-to-use application management platform, a best practice for cloud native application delivery, and easy to use. Focus on the application-centric concept. Enabling enterprises to build cloud native development cloud, cloud native delivery cloud.

For Enterprise Rainbond is a cloud native platform that can be used directly out of the boxWith Rainbond, you can quickly complete the cloud-native transformation of the enterprise R&D and delivery system.

For Developers Develop, test and operate enterprise business applications based on RainbondYou can get a full range of cloud native technology capabilities out of the box. Including but not limited to continuous integration, service governance, architecture support, multi-dimensional application observation, and traffic management.

For Delivery engineer Build a product version management system based on Rainbond and build a standardized customer delivery environment, so that the traditional delivery process can be automated, simplified and manageable.

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.

Add Maintainer WeChart

License

Rainbond follow LGPL-3.0 licenseDetails seeLICENSE and Licensing