[Sandbox] joylive-agent

[hexiaofeng]

Application contact emails

hexiaofeng@jd.com, chenzhiguo@jd.com

Project Summary

Bytecode-enhanced microservice traffic governance framework designed for application multi-active

Project Description

Microservice governance framework,
leveraging bytecode enhancement technology, employs a micro-kernel extensible
architecture's proxyless implementation, offering superior performance and
resource efficiency compared to the sidecar pattern. In addition to supporting
conventional microservice governance features such as circuit breaking, rate
limiting, and degradation, it also facilitates swimlane governance and
application multi-active traffic governance. Offers traffic governance plugins
for Spring cloud hoxton/2020/2021/2022/2023/2024, Dubbo 2.6/2.7/3, SofaRpc, Rocketmq, and
Kafka. This enables existing java applications within enterprises to seamlessly
integrate traffic governance capabilities without altering business code,
supporting traffic scheduling in same-region, cross-region and multi-cloud
multi-active scenarios, thereby enhancing business stability and disaster
recovery capabilities.

Project repo URL in scope of application

https://github.com/jd-opensource/joylive-agent

Additional repos in scope of the application

https://github.com/jd-opensource/joylive-injector

Website URL

https://github.com/jd-opensource/joylive-agent

Roadmap

https://github.com/jd-opensource/joylive-agent/blob/main/docs/roadmap.md

Roadmap context

By 2024, complete the basic governance capabilities, allowing a large number of Java applications to be used out-of-the-box.
By 2025, integrate more frameworks and support xDS.

Contributing Guide

https://github.com/jd-opensource/joylive-agent/blob/main/CONTRIBUTING.md

Code of Conduct (CoC)

https://github.com/jd-opensource/joylive-agent/blob/main/CODE_OF_CONDUCT.md

Adopters

No response

Contributing or Sponsoring Org

https://www.jdcloud.com/

Maintainers file

https://github.com/jd-opensource/joylive-agent/blob/main/community/members.md

IP Policy

• If the project is accepted, I agree the project will follow the CNCF IP Policy

Trademark and accounts

• If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF

Why CNCF?

This project can contribute to the CNCF in several ways:

• Providing high-performance, scalable service governance capabilities, expanding the microservices ecosystem, and making it easier for developers to use.
• Offering traffic governance for application multi-live, facilitating application disaster recovery, and promoting multi-cloud, multi-active.

By joining the CNCF, this project will gain the following benefits:

• Access to a large and active developer community. The CNCF has a vast and active developer community interested in cloud-native technologies. This can help attract new contributors to the project and ensure it is well-maintained.
• Access to resources and support from the CNCF. The CNCF provides various resources and support to its member projects, such as funding, training, and marketing. This can help the project grow and succeed.
• Increased visibility and adoption. As a member of the CNCF, the project can increase its visibility and adoption. This may lead to more users and contributors, which can help further develop and improve the project.
• Overall, this project can contribute to the CNCF and benefit from being a member of the CNCF in multiple ways. This can help make it a more successful project and make it easier for developers to use.

Benefit to the Landscape

This project provides an alternative choice for service governance and offers traffic governance for application multi-live, making it convenient for disaster recovery

Cloud Native 'Fit'

This project is suitable for placement in service mesh, similar to istio and sermant project.

Cloud Native 'Integration'

The following CNCF projects are dependencies of this project:
K8s: Based on webhook intercepting Deployment creation, automatically injects joylive-agent
opentelemetry: Uses opentelemetry to report traffic metrics

Cloud Native Overlap

This project overlaps with Istio and Sermant in terms of service governance capabilities, but this project also provides governance for multi-live traffic.

Similar projects

istio
sermant

Landscape

N/A

Business Product or Service to Project separation

JD Cloud Vessel - Application Multi-Live module depends on this project, and provides support for private frameworks through plugins on top of this open-source project. Its repository is in JD's internal repository, and we will continue to contribute core capabilities and integrations with open-source frameworks to this open-source project.

Project Domain Technical Review

No response

CNCF Contacts

No response

Additional information

No response

[dims]

From the name, this is just the agent. What about a control plane for the agents? how do they get configured? monitored? Looks like those things are in "JD Cloud Vessel". In other words, what can the agents do by themselves without needing the control plane?

Also what happens if folks working in the open source project want to do something that is not blessed by JD or not in the "plan" for JD Cloud Vessel. Will that get accepted? prioritized? How can you decouple the two?

[dims]

And what is nacos? how is it related to this submission?

[hexiaofeng]

From the name, this is just the agent. What about a control plane for the agents? how do they get configured? monitored? Looks like those things are in "JD Cloud Vessel". In other words, what can the agents do by themselves without needing the control plane?

Also what happens if folks working in the open source project want to do something that is not blessed by JD or not in the "plan" for JD Cloud Vessel. Will that get accepted? prioritized? How can you decouple the two?

LiveAgent provides a plugin for obtaining control policies, which currently allows reading from files, thus not depending on the control plane.
LiveAgent is open-sourced under the Apache2 license and follows its usage guidelines.

The control plane of JD Cloud Vessel has its own unique dependencies and UI, making it inconvenient to separate and open-source. We expect the community to develop its control plane.

[hexiaofeng]

And what is nacos? how is it related to this submission?

Nacos is a well-known open-source project for a registration center in the Apache community.
LiveAgent is a microservice governance project that supports the registration center relied on by Spring Cloud projects.
Currently, we have prioritized and optimized the adaptation for Nacos, including support for reading configuration policies from it.