v2.0.0 (2022-07-07)
Easegress v2.0.0 is now released. This is the second major release of Easegress.
Full Changelog
Docker image
docker pull megaease/easegress:v2.0.0
What's new?
Significant changes in Easegress 2.0:
- Protocol Independent Pipeline
- One pipeline implementation for all protocols, such as HTTP, MQTT, TCP, etc.
- All protocols in one pipeline instance.
- Decoupling of control logic and business logic.
- Resilence filters are removed and resilience policies are now defined in the pipeline.
- Resilience policies are injected into filters that support resilience, e.g. the
Proxy
filter.
- Multiple APIs Orchestration.
- Multiple requests and responses can be used during processing.
- Add filters
RequestBuilder
andResponseBuilder
, new requests and responses can be easily created based on the existing requests and responses.
Detailed Changes
-
pipeline
- protocol-independent pipeline,
Pipeline
replacesHTTPPipeline
,MQTTPipeline
and etc. - add
RequestBuilder
filter,ResponseBuilder
filter and built-in filterEND
. - add the support of
namespace
. - add the support of filter alias.
- remove
Retryer
,CircuitBreaker
andTimeLimiter
filters, and add support of resilience policies on the pipeline.
- protocol-independent pipeline,
-
resilience
- resilience policies can be easily reused, they are defined on pipeline and injected into filters that support resilience.
-
tracing
- tracing is now using Zipkin B3 format.
-
cluster
- drop the support of dynamic cluster management.
- depreciated configuration method is removed.
Compatibility
Please note this release is not fully compatible with previous releases:
- please rename
HTTPPipeline
toPipeline
. - if you are using
Retryer
,CircuitBreaker
,TimeLimiter
,APIAggregator
, please refer this document and this document to make necessary changes. - please follow this document to migrate your filters to v2.0.
- PLEASE BACKUP YOUR v1.x INSTALLATION BEFORE UPGRADING TO v2.0.