Skip to content

Choreo Connect 0.9.0-Alpha Released!

Pre-release
Pre-release
Compare
Choose a tag to compare
@dinusha92 dinusha92 released this 08 Apr 09:14
· 2933 commits to main since this release
v0.9.0-alpha
5f798f7

What's new in Choreo Connect 0.9.0-Alpha

  • This is the alpha release of the Choreo Connect 0.9.0

  • Microservices have become the norm for modern application architecture. Workloads of modern applications are
    spread across many groups of microservices, cloud services and legacy services. The characteristics and
    behaviors of such heterogeneous services have a massive diversity. Such as authentication mechanisms, message
    formats, high availability factors and so on. The Choreo-Connect is designed to expose heterogeneous
    microservices as APIs to end consumers using a common API interface based on the Open API Specification. This
    helps expose microservices using a unified interface to external consumers, internal consumers and partners. It
    applies the common quality of service attributes on API requests such as security, rate limiting and analytics
    and also offers a wide range of features which helps organizations to deploy APIs microservice architectures
    efficiently.

Features

Improvements and Bug fixes

List of completed tasks

Known Issues

Open Issues

Try it

Quick start guide

Contributing

How To Contribute

Your feedback is most welcome!

Contributing Code

Read through the project Contribution Guidelines to learn how to contribute with code.

User Forum

If you have any questions regarding the product you can use our StackOverflow forum to raise them.

Slack Channels

Join us via this to our wso2-apim.slack.com for even better communication. You can talk to our developers directly regarding any issues, concerns about the product. We encourage you to start discussions or join any ongoing discussions with the team, via our slack channels.

Reporting Issues

We encourage you to report issues, documentation faults, and feature requests regarding Choreo-Connect through the Github Issues.

And please be advised that security issues must be reported to [email protected], not as a GitHub issue, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines when reporting the security issues.

--WSO2 API Manager Team--

Assets 3
Loading