This is an automated email from the ASF dual-hosted git repository.
albumenj pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dubbo-website.git
The following commit(s) were added to refs/heads/master by this push:
new 387b072b106 Update 3.3 release docs (#3053)
387b072b106 is described below
commit 387b072b1062e8f7c6a9337cf8d355d1f821ffa3
Author: Albumen Kevin <[email protected]>
AuthorDate: Tue Oct 22 14:06:47 2024 +0800
Update 3.3 release docs (#3053)
* Update 3.3 release docs
* Announce
---
content/en/blog/news/apache-33-release.md | 155 ++++++++++-----------
content/zh-cn/blog/news/apache-33-release.md | 2 +-
data/announcements/en/scheduled.yaml | 9 ++
data/announcements/zh/scheduled.yaml | 2 +-
.../364921d0-324a-4325-a453-71c111e0312c.png | Bin 0 -> 1115061 bytes
.../533a9f55-a98b-4f07-b7b2-63d939338160.png | Bin 0 -> 75104 bytes
.../53857659-bd89-4e1c-b713-83689378b12f.png | Bin 0 -> 70768 bytes
.../6b3202d2-b703-4708-8d05-7f8445e1ad14.png | Bin 0 -> 974506 bytes
.../70125f11-14be-4786-bef7-b12462331263.png | Bin 0 -> 69929 bytes
.../cc93cf33-8f19-45dc-970f-1288994bf8a5.png | Bin 0 -> 231806 bytes
.../f38f6e7e-997f-4f5b-a888-ddea1ce7c6ca.png | Bin 0 -> 78203 bytes
11 files changed, 82 insertions(+), 86 deletions(-)
diff --git a/content/en/blog/news/apache-33-release.md
b/content/en/blog/news/apache-33-release.md
index 1aaba507b13..9727bf66e24 100644
--- a/content/en/blog/news/apache-33-release.md
+++ b/content/en/blog/news/apache-33-release.md
@@ -7,180 +7,167 @@ description: >
With Apache Dubbo surpassing 40k Stars, the Apache Dubbo team officially
announces the release of Dubbo 3.3! As a leading open-source microservices
framework, Dubbo has been dedicated to providing developers with
high-performance, scalable, and flexible distributed service solutions. This
release, Dubbo 3.3, through the new upgrade of Triple X, breaks past
limitations, achieving comprehensive support for both north-south and east-west
traffic, and enhancing compatibility with cloud-nat [...]
---
-As Apache Dubbo surpasses 40k Stars, the Apache Dubbo team officially
announces the release of Dubbo 3.3! As a leading open-source microservices
framework, Dubbo has been dedicated to providing developers with
high-performance, scalable, and flexible distributed service solutions. This
release, Dubbo 3.3, through the new upgrade of Triple X, breaks past
limitations, achieving comprehensive support for both north-south and east-west
traffic, and enhancing compatibility with cloud-native a [...]
+Apache Dubbo has surpassed 40,000 stars, and the team is proud to announce the
official release of Dubbo 3.3! As a leading open-source microservices
framework, Dubbo has always been committed to providing developers with
high-performance, scalable, and flexible solutions for distributed services.
The release of Dubbo 3.3, featuring the **Triple X** upgrade, breaks previous
limitations, achieving comprehensive support for both north-south and east-west
traffic, and enhancing compatibility [...]
## Introduction to Dubbo
-**Apache Dubbo** is a high-performance, lightweight microservice framework
originally developed in Java, but now extended to support various languages
such as **Go, Rust, and Python**, providing robust support for building
cross-language and cross-platform distributed systems for enterprises
worldwide. Dubbo offers rich service governance capabilities, including service
registration and discovery, load balancing, fault tolerance, and tracing,
helping developers build efficient and flexib [...]
+**Apache Dubbo** is a high-performance, lightweight microservices framework
that was initially developed in Java. It has since expanded to support multiple
languages, such as **Go, Rust, and Python**, making it ideal for building
cross-language, cross-platform distributed systems. Dubbo provides rich service
governance features, including service registration and discovery, load
balancing, fault tolerance, and call chain tracing, which help developers build
efficient, flexible microservi [...]
-As Dubbo has gradually evolved, its communication capabilities, service
governance, and cross-language compatibility have significantly improved,
making it an ideal tool for supporting modern microservice architectures.
+With its evolution, Dubbo has significantly improved its communication
performance, service governance, and cross-language compatibility, making it a
powerful tool for supporting modern microservices architectures.
-## Background of Triple X Upgrade
+## Background of the Triple X Upgrade
-In the early applications of Dubbo, while it demonstrated excellent
performance in service intercommunication within data centers, the original
architecture gradually exposed some bottlenecks as technology evolved and
application scenarios expanded. These bottlenecks are especially evident in
cross-region and cross-cloud environments, particularly affecting development
complexity and system performance due to frequent switching between web
frameworks and RPC frameworks.
+In its early applications, Dubbo demonstrated excellent performance in data
center service interoperability. However, as technology evolved and application
scenarios expanded, the original architecture began to show bottlenecks. These
limitations became especially evident in cross-region and cross-cloud
environments, where frequent switches between web frameworks and RPC frameworks
led to increased development complexity and decreased system performance.
-**The pain points of traditional architecture mainly include:**
+**Pain Points of the Traditional Architecture:**
-1. **Limited to data center applications**: In cross-regional or cross-cloud
applications, the traditional architecture of Dubbo lacks native support for
wide-area environments, resulting in increased complexity as developers switch
between various protocols and frameworks.
+1. **Limited to Data Center Applications**: In cross-region or cross-cloud
applications, Dubbo's traditional architecture lacked native support for
wide-area environments, forcing developers to switch between multiple protocols
and frameworks, increasing complexity.
-2. **Dual challenges of north-south and east-west traffic**: In modern
microservice architectures, traditional RPC frameworks often focus more on
optimizing north-south traffic, while the performance requirements for
inter-service (east-west) communication are increasing, posing new challenges
to the traditional Dubbo architecture.
+2. **Challenges with North-South and East-West Traffic**: Traditional RPC
frameworks, like Dubbo, often focus more on service-to-service (east-west)
traffic optimization. However, the need for efficient north-south communication
(client-to-server) has increased, creating new challenges.
-3. **Cloud-native and cross-language interoperability requirements**: With
the rise of cloud-native technologies, systems need deeper support for HTTP
protocols and the ability to communicate across languages; however, traditional
Dubbo has not been natively optimized in this regard.
+3. **Cloud-Native and Cross-Language Requirements**: With the growth of
cloud-native technologies, systems require better support for HTTP protocols
and cross-language communication, areas where traditional Dubbo wasn't
optimized.
-**Transformations and breakthroughs of Triple X**: The emergence of Triple X
directly addresses these pain points. It not only continues Dubbo's
longstanding high-performance communication capabilities but also achieves
comprehensive compatibility with the gRPC protocol. By supporting protocols
such as HTTP/1, HTTP/2, and HTTP/3, it provides a more flexible and efficient
solution for a wide range of cross-cloud and cross-region application scenarios.
+**Triple X's Transformation and Breakthroughs:** The **Triple X** upgrade
directly addresses these pain points. It continues Dubbo's high-performance
communication capabilities while achieving full compatibility with the gRPC
protocol, supporting HTTP/1, HTTP/2, and HTTP/3 protocols. This provides more
flexibility and efficiency for cross-cloud and cross-region application
scenarios.
-
+
-## Core Capabilities Overview of Triple X
+## Overview of Triple X Core Capabilities
-* **Comprehensive support for north-south and east-west traffic**: Triple X
seamlessly supports north-south traffic from clients to servers and east-west
communication between services, ensuring flexible conversion and improving the
overall efficiency of communication links.
+* **Comprehensive Traffic Support**: Triple X supports both north-south
(client to server) and east-west (service to service) traffic. This seamless
support ensures flexible conversions, improving the overall efficiency of
communication links.
-* **Adheres to gRPC protocol standards**: Triple X follows gRPC protocol
standards, supporting communication via Protobuf, allowing seamless interaction
with gRPC services and extending Dubbo's cross-language and cross-platform
communication capabilities.
+* **Compliance with gRPC Protocol Standard**: Triple X adheres to the gRPC
protocol standard, allowing communication via Protobuf. This enables seamless
interaction with gRPC services and extends Dubbo's cross-language,
cross-platform communication capabilities.
-* **Based on HTTP protocols, native support for cloud-native
architectures**: Triple X is built atop HTTP/1, HTTP/2, and HTTP/3 protocol
stacks, fully optimizing network communication performance and seamlessly
integrating with modern cloud-native infrastructures, supporting various
gateways and service meshes.
+* **Built on HTTP Protocol, Native Cloud-Native Support**: Triple X is built
on HTTP/1, HTTP/2, and HTTP/3, optimizing network performance and integrating
with cloud-native infrastructures, including support for various gateways and
service meshes.
-* **High performance optimization**: Triple X offers significant performance
improvements, especially excelling in high-concurrency and weak network
environments, greatly enhancing system throughput and response speeds.
+* **High-Performance Optimization**: Triple X provides extreme performance
enhancements, particularly in high-concurrency and weak network environments,
significantly improving system throughput and response speed.
-* **Smooth migration and framework compatibility**: It supports seamless
migration from existing Spring Web projects, allowing developers to switch to
Triple X without changing existing code, improving performance while retaining
support for frameworks like Spring MVC.
+* **Smooth Migration and Framework Compatibility**: Triple X allows developers
to migrate existing Spring Web projects without modifying code, offering a
seamless switch to Triple X while retaining support for frameworks like Spring
MVC.
-* **High scalability**: Triple X introduces over 20 SPI extension points,
supporting custom core behaviors, including routing mapping, parameter parsing,
serialization, and exception handling. This significantly enhances the
flexibility and customizability of the framework, allowing developers to tailor
behaviors to specific business needs and scenarios, improving development
efficiency and reducing customization costs.
+* **High Extensibility**: With over 20 new SPI extension points, Triple X
enables customization of core behaviors, including routing, parameter parsing,
serialization, and exception handling. This enhances flexibility, allowing
developers to adapt the framework to meet specific business needs.
-## Usage Scenarios for Triple X
+## Triple X Usage Scenarios
-**Triple X** provides flexible access methods for microservice architectures
in Dubbo 3.3, adapting to system needs in various scenarios. Depending on the
system architecture, Triple X offers both **centralized access** and
**decentralized access** methods, suitable for multiple application scenarios.
+**Triple X** in Dubbo 3.3 offers flexible integration approaches for
microservices architectures, adapting to different system requirements.
Depending on the system architecture, Triple X provides both **centralized**
and **decentralized** integration approaches, making it suitable for various
application scenarios.
-### 1. Centralized Access
+### 1. Centralized Integration
-In **centralized access**, external traffic enters the Dubbo backend services
through a unified service gateway. The gateway handles HTTP traffic parsing and
forwarding, routing requests to the appropriate backend services. This method
is suitable for systems with high requirements for traffic management, control,
and authentication, allowing centralized control of traffic entry points.
+In a **centralized integration** approach, external traffic enters Dubbo
backend services through a unified service gateway. The gateway handles HTTP
traffic parsing, forwarding, and routing requests to the appropriate backend
services. This approach is suitable for systems with high requirements for
unified traffic management, flow control, and permission verification, allowing
centralized control over incoming traffic.
-
+
-* **Use case**: When the system requires centralized management of external
requests, monitoring and throttling traffic, Triple X can efficiently handle
HTTP/1, HTTP/2, and HTTP/3 traffic through the service gateway and forward it
to Dubbo services for processing.
+* **Usage Scenario**: For systems requiring centralized management of external
requests, such as traffic monitoring and rate limiting, Triple X can
efficiently handle HTTP/1, HTTP/2, and HTTP/3 traffic via a service gateway and
forward it to Dubbo services.
-* **Advantages**: Centralized control, easier management, suitable for
unified traffic governance in large-scale systems.
+* **Advantages**: Centralized control, ease of management, suitable for
large-scale systems needing unified traffic governance.
-### 2. Decentralized Access
+### 2. Decentralized Integration
-In **decentralized access**, external clients can directly access the backend
Dubbo services via HTTP protocols without relying on an intermediate gateway
layer. This approach is suitable for systems requiring high performance and low
latency, reducing communication overhead by directly routing traffic to service
nodes, thus improving system response speed. Eliminating the gateway helps
avoid system unavailability caused by gateway failures, simplifying deployment
architecture and enhanc [...]
+In a **decentralized integration** approach, external clients can access Dubbo
backend services directly via HTTP, without relying on an intermediary gateway.
This approach is suitable for systems with high-performance and low-latency
requirements, as it reduces communication overhead by eliminating the need for
a gateway, thereby improving system response speed. Removing the gateway node
also avoids system unavailability caused by gateway failures, simplifying the
deployment architectur [...]
-
+
-* **Use case**: When a system wishes to access Dubbo services through direct
HTTP traffic, reducing intermediaries to improve response speed, Triple X
provides the ability to expose REST APIs directly, completing service exits
without a gateway.
+* **Usage Scenario**: For systems that need to access Dubbo services directly
via HTTP to reduce intermediate steps and improve response speed, Triple X
allows REST APIs to be exposed without a gateway.
-* **Advantages**: Removing intermediaries enhances performance and response
speed, simplifying architecture, suitable for low-latency application scenarios.
+* **Advantages**: Eliminates intermediate steps, improves performance,
simplifies architecture, suitable for low-latency applications.
-## Detailed Explanation of Triple X Core Capabilities
+## Detailed Breakdown of Triple X Capabilities
-### 1. Comprehensive traffic management and efficient communication support
+### 1. Comprehensive Traffic Management and Efficient Communication
-In complex microservices architectures, north-south traffic (from clients to
servers) and east-west traffic (service-to-service communication) require
different technologies for processing, often facing performance bottlenecks and
complicated development and operational issues.
+In complex microservices architectures, handling both north-south (client to
server) and east-west (service to service) traffic can be challenging. Triple X
uses a unified communication protocol to support both, eliminating the need to
switch between web and RPC frameworks, simplifying the development process, and
improving performance and maintainability.
-The Triple X protocol supports both north-south and east-west traffic through
a unified communication protocol. There is no need to switch between web
frameworks and RPC frameworks, simplifying the development process and
enhancing the overall performance and maintainability of the system.
-
-Developers can achieve comprehensive traffic support through Triple X, whether
handling user-initiated requests or inter-service communications, ensuring
efficient transmission.
+Developers can utilize Triple X for efficient support of both user-initiated
requests and inter-service communication, all transmitted smoothly via Triple X.
```java
package org.apache.test;
@DubboService
public class UserServiceImpl implements UserService {
- // Handle east-west requests
+ // Handles east-west requests
}
-// Triple X also supports north-south traffic processing
+// Triple X also supports north-south traffic
@DubboService
public class OrderService {
- @GetMapping("/order/{orderId}")
- public Order getOrderById(@PathVariable("orderId") String orderId) {}
+ @GetMapping("/order/{orderId}")
+ public Order getOrderById(@PathVariable("orderId") String orderId) {}
}
```
-Invocation methods:
-
-1. The Dubbo Client directly initiates an RPC call.
-
-2. The front end uses HTTP to directly request, targeting the path
`http://server:50051/order/{orderId}`.
-
-3. Using the default published path of Dubbo for the request, targeting the
path
`http://server:50051/org.apache.test.OrderService/getOrderById?orderId=xxx`.
+### 2. Compliance with gRPC Protocol Standard
-### 2. Adherence to gRPC protocol standards
+Communication between cross-language services is often a challenge in
distributed systems, and gRPC is a popular solution. Triple X adheres to the
**gRPC protocol standard**, enabling seamless interaction with gRPC using
Protobuf, which enhances cross-language and cross-platform communication
capabilities.
-Communication between cross-language services often becomes a challenge in
distributed systems. gRPC is one of the commonly used solutions, but
traditional Dubbo requires additional tools to achieve interoperability with
gRPC.
+Services using Triple X can interact directly with gRPC-based services without
extra adaptation, simplifying development.
-Triple X adheres to **gRPC protocol standards**, facilitating seamless
interaction with gRPC through Protobuf, simplifying the development process and
enhancing cross-language and cross-platform communication capabilities.
+### 3. Built on HTTP Protocol, Native Cloud-Native Support
-Services using Triple X can directly interact with gRPC-based services without
additional adaptations, enabling efficient inter-service communication.
+In cloud-native environments, services need to integrate effectively with
various network facilities like API gateways and service meshes, while
supporting different HTTP protocols to enhance performance.
-### 3. Native support for cloud-native architectures based on HTTP protocols
+Triple X supports **HTTP/1, HTTP/2, and HTTP/3**, allowing developers to
leverage the benefits of these protocols, such as long connections,
multiplexing, and header compression, without extra configuration. **HTTP/3**
also resolves head-of-line blocking issues, and its UDP-based communication
maintains high quality and service performance in weak network environments.
-In cloud-native environments, services need efficient integration with various
network infrastructures (such as API gateways, service meshes) while supporting
multiple HTTP protocols to optimize network performance.
-
-Triple X supports both **HTTP/1, HTTP/2, and HTTP/3** protocols, allowing
developers to leverage the advantages of these protocols, including long
connections, multiplexing, and header compression, without additional
configuration for efficient network communication. Using **HTTP/3** can
completely resolve head-of-line blocking issues while being based on UDP
communication, maintaining high connection quality and service performance even
in weak network conditions, whereas TCP may become [...]
-
-Triple X allows reusing existing **Servlet** ports in Spring Boot to access
HTTP traffic, eliminating the need for new Netty listening ports. The
simplification of the network architecture reduces usage and maintenance costs,
improves security, and facilitates traffic through enterprise firewalls and
gateways.
+Triple X allows reusing the existing **Servlet** port of Spring Boot to handle
HTTP traffic, eliminating the need for a separate Netty listening port. This
simplifies the network architecture, reduces maintenance costs, improves
security, and allows traffic to pass through enterprise firewalls and gateways
more easily.
-### 4. High performance optimization, enhancing QPS by 5 times
+### 4. High-Performance Optimization, 5x QPS Improvement
-In high-concurrency scenarios, traditional communication protocols often lack
deep optimization, leading to bottlenecks that affect the overall response time
and throughput of systems.
+In high-concurrency scenarios, traditional communication protocols often lead
to bottlenecks, affecting system response time and throughput.
-Triple X improves system performance significantly by reducing CPU usage and
memory consumption through technologies like **Radix Tree** and **Zero Copy**,
excelling in high-concurrency and weak network environments:
+Triple X uses technologies such as **Radix Tree** and **Zero Copy** to reduce
CPU usage and memory consumption, significantly improving system performance,
especially in high-concurrency and weak network environments:
-* **Efficient routing**: Adopting Radix Tree prefix structures for routing
matching, optimizing key hash algorithms, and supporting dynamic updates,
reducing memory usage and improving matching efficiency.
+* **Efficient Routing**: Uses Radix Tree for route matching, optimizing the
key hash algorithm and supporting dynamic updates, which reduces memory usage
and improves matching efficiency.
-* **Memory usage optimization**: Combining Zero Copy technology with object
reuse techniques minimizes data copying and object creation overhead, reducing
garbage collection pressure and enhancing throughput.
+* **Optimized Memory Usage**: Combines Zero Copy with object reuse, reducing
data copying and object creation overhead, which lowers garbage collection
pressure and increases throughput.
-* **HTTP/3 support**: Introduced based on QUIC, the HTTP/3 protocol
significantly enhances performance in weak network environments, resolves
head-of-line blocking issues, reduces latency, and improves connection
reliability.
+* **HTTP/3 Support**: Utilizes the QUIC-based HTTP/3 protocol, improving
performance in weak network conditions by reducing latency and enhancing
connection reliability.
-* **Multi-protocol performance testing optimization**: The Dubbo team
performed comprehensive performance testing on various protocols, conducting
multiple rounds of performance optimizations based on test results to ensure
the best performance in diverse scenarios.
+* **Multi-Protocol Stress Testing and Optimization**: The Dubbo team conducted
extensive stress tests on multiple protocols and performed several rounds of
optimization, ensuring optimal performance across different scenarios.
-After performance testing, the average response time of a simple Rest service
compared to traditional Spring Boot REST services was reduced to 1/3 for Triple
X services, with QPS improving by 5 times under high pressure, while memory
allocation decreased by 50%, significantly enhancing overall system performance
and resource utilization efficiency.
+Performance tests show that, compared to traditional Spring Boot REST
services, simple REST services using Triple X achieve **five times the QPS**
under high pressure, reduce response times to one-third, and lower memory
allocation by 50%, greatly enhancing system performance and resource efficiency.
-
+
-
+
-
+
-
+
-### 5. Smooth migration and framework compatibility
+### 5. Smooth Migration and Framework Compatibility
-Additionally, Triple X supports the performance improvement of existing Spring
Web projects during migration to microservice architectures without extensive
code modifications.
+Triple X also supports the migration of existing Spring Web projects to a
microservices architecture without significant code changes.
-Triple X offers a zero-intrusive migration solution, allowing developers to
migrate existing Spring Web projects to Triple X without modifying existing
code, while retaining support for frameworks such as Spring MVC.
+Triple X offers a **zero-intrusive migration solution**, allowing developers
to migrate existing Spring Web projects to Triple X without changing existing
code while still supporting frameworks like Spring MVC.
```java
-@DubboService // Just add the service publishing configuration
+@DubboService // Only need to add service publishing configuration
@RestController
public class DemoController {
-
- @GetMapping("/spring-test")
- public String sayHello(@RequestParam("name") String name) {
- return "Hello " + name;
- }
+ @GetMapping("/spring-test")
+ public String sayHello(@RequestParam("name") String name) {
+ return "Hello " + name;
+ }
}
```
-## Overview of Other Capability Optimizations in This Version Upgrade
+## Overview of Other Enhancements in This Release
### 1. Native Image AOT Support
-Dubbo 3.3 introduces support for **Native Image AOT (Ahead-of-Time
Compilation)**, allowing developers to compile Dubbo applications into native
binary files, significantly reducing startup time and memory usage,
particularly suitable for serverless scenarios.
+Dubbo 3.3 introduces support for **Native Image AOT (Ahead-of-Time
Compilation)**, allowing developers to compile Dubbo applications into native
binaries. This significantly reduces startup time and memory usage, making it
ideal for serverless scenarios.
### 2. Project Loom Support
-Dubbo 3.3 provides support for **Project Loom**, optimizing thread management
in high-concurrency scenarios through virtual threads, simplifying asynchronous
programming models, and enhancing concurrent processing capabilities.
+Dubbo 3.3 adds support for **Project Loom**, optimizing thread management in
high-concurrency scenarios with virtual threads, simplifying the asynchronous
programming model, and improving concurrency handling.
### 3. New Routing Rules
-In routing mechanisms, Dubbo 3.3 introduces new routing rules, supporting more
flexible traffic control and service governance, enhancing the adaptability of
microservice systems in large-scale deployments.
+Dubbo 3.3 also introduces new routing rules, supporting more flexible traffic
control and service governance, enhancing adaptability for large-scale
microservices deployments.
## Conclusion
-The release of **Apache Dubbo 3.3** marks a new height in microservices
communication technology. Through **Triple X**, Dubbo not only achieves
comprehensive support for north-south and east-west traffic but also provides
developers with stronger and more flexible tools through seamless gRPC
integration, cloud-native support based on HTTP protocols, and high-performance
optimizations, helping them build modern distributed systems.
+The release of **Apache Dubbo 3.3** marks a significant milestone in
microservices communication technology. With **Triple X**, Dubbo now offers
comprehensive support for both north-south and east-west traffic, seamless
integration with gRPC, cloud-native support via HTTP protocols, and significant
performance optimizations, providing developers with a powerful and flexible
tool for building modern distributed systems.
-Whether enhancing inter-service communication efficiency, achieving
cross-language compatibility, or optimizing communication performance in
cloud-native environments, Dubbo 3.3 is an ideal choice for developers facing
modern distributed system challenges. Upgrade to Dubbo 3.3 now to experience
the transformation brought by **Triple X** and start a new era of microservices
communication!
+Whether you need to enhance the efficiency of inter-service communication,
achieve cross-language compatibility, or optimize cloud-native communication
performance, **Dubbo 3.3** is the ideal choice for tackling the challenges of
modern distributed systems. Upgrade to Dubbo 3.3 today and experience the
transformation brought by **Triple X**, ushering in a new era of microservices
communication!
For more upgrade guides and compatibility information, please refer to [Dubbo
3.2 to 3.3 Upgrade
Guide](/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/version/3.2-to-3.3-compatibility-guide/)。
diff --git a/content/zh-cn/blog/news/apache-33-release.md
b/content/zh-cn/blog/news/apache-33-release.md
index 901bddf0021..fc032ccbc08 100644
--- a/content/zh-cn/blog/news/apache-33-release.md
+++ b/content/zh-cn/blog/news/apache-33-release.md
@@ -23,7 +23,7 @@ description: >
1. **局限于数据中心内的应用场景**：在跨地域或跨云应用中，Dubbo
的传统架构缺乏对广域环境的原生支持，导致开发者需要在多种协议和框架中切换，增加了复杂性。
-2. **南北向与东西向流量的双重挑战**：在现代微服务架构下，传统的 RPC
框架往往更侧重南北向流量优化，而服务间（东西向）通信的性能要求日益增加，对传统 Dubbo 架构提出了新的挑战。
+2. **南北向与东西向流量的双重挑战**：在现代微服务架构下，传统的 RPC
框架往往更侧重服务间（东西向）流量优化，而南北向通信的性能要求日益增加，对传统 Dubbo 架构提出了新的挑战。
3. **云原生与跨语言互操作性要求**：随着云原生技术的普及，系统需要对 HTTP 协议有更深层次的支持，并具备跨语言的通信能力，然而传统 Dubbo
在这一点上并未原生优化。
diff --git a/data/announcements/en/scheduled.yaml
b/data/announcements/en/scheduled.yaml
index 306914df1bd..38fabe14f1e 100755
--- a/data/announcements/en/scheduled.yaml
+++ b/data/announcements/en/scheduled.yaml
@@ -29,6 +29,15 @@
# leave the "announcements" key in place
announcements:
+- name: 3.3 Release
+ startTime: 2024-09-11T00:00:00
+ endTime: 2024-12-31T18:00:00
+ style: >-
+ background-image: linear-gradient(90deg, rgb(0, 150, 255) 0%, rgb(51, 190,
255) 100%);
+ title: |
+ <a href=
"/en/blog/2024/09/11/apache-dubbo-3.3-released-triple-x-leads-a-new-era-of-microservices-communication/">Apache
Dubbo 3.3</a> <em> Released！🔥🔥🔥</em>
+ message: |
+ On the occasion of Apache Dubbo surpassing 40,000 stars, the Apache Dubbo
team is proud to officially announce the release of Dubbo 3.3! As a globally
leading open-source microservices framework, Dubbo has consistently been
dedicated to providing developers with high-performance, scalable, and flexible
distributed service solutions. With the release of Dubbo 3.3, the all-new
upgrade through Triple X breaks previous limitations, achieving comprehensive
support for both north-south and [...]
- name: Brandnew Website
startTime: 2023-02-21T00:00:00
endTime: 2023-04-20T18:00:00
diff --git a/data/announcements/zh/scheduled.yaml
b/data/announcements/zh/scheduled.yaml
index 3469c2bb671..cd5729470e5 100644
--- a/data/announcements/zh/scheduled.yaml
+++ b/data/announcements/zh/scheduled.yaml
@@ -1,5 +1,5 @@
announcements:
- - name: 3.2 Release
+ - name: 3.3 Release
startTime: 2024-09-11T00:00:00
endTime: 2024-12-31T18:00:00
style: >-
diff --git
a/static/imgs/blog/33-release/364921d0-324a-4325-a453-71c111e0312c.png
b/static/imgs/blog/33-release/364921d0-324a-4325-a453-71c111e0312c.png
new file mode 100644
index 00000000000..9e0e7f8a3ba
Binary files /dev/null and
b/static/imgs/blog/33-release/364921d0-324a-4325-a453-71c111e0312c.png differ
diff --git
a/static/imgs/blog/33-release/533a9f55-a98b-4f07-b7b2-63d939338160.png
b/static/imgs/blog/33-release/533a9f55-a98b-4f07-b7b2-63d939338160.png
new file mode 100644
index 00000000000..80301f42b14
Binary files /dev/null and
b/static/imgs/blog/33-release/533a9f55-a98b-4f07-b7b2-63d939338160.png differ
diff --git
a/static/imgs/blog/33-release/53857659-bd89-4e1c-b713-83689378b12f.png
b/static/imgs/blog/33-release/53857659-bd89-4e1c-b713-83689378b12f.png
new file mode 100644
index 00000000000..54bdea07400
Binary files /dev/null and
b/static/imgs/blog/33-release/53857659-bd89-4e1c-b713-83689378b12f.png differ
diff --git
a/static/imgs/blog/33-release/6b3202d2-b703-4708-8d05-7f8445e1ad14.png
b/static/imgs/blog/33-release/6b3202d2-b703-4708-8d05-7f8445e1ad14.png
new file mode 100644
index 00000000000..3db9062ef7e
Binary files /dev/null and
b/static/imgs/blog/33-release/6b3202d2-b703-4708-8d05-7f8445e1ad14.png differ
diff --git
a/static/imgs/blog/33-release/70125f11-14be-4786-bef7-b12462331263.png
b/static/imgs/blog/33-release/70125f11-14be-4786-bef7-b12462331263.png
new file mode 100644
index 00000000000..47bc9271af9
Binary files /dev/null and
b/static/imgs/blog/33-release/70125f11-14be-4786-bef7-b12462331263.png differ
diff --git
a/static/imgs/blog/33-release/cc93cf33-8f19-45dc-970f-1288994bf8a5.png
b/static/imgs/blog/33-release/cc93cf33-8f19-45dc-970f-1288994bf8a5.png
new file mode 100644
index 00000000000..a281b794b61
Binary files /dev/null and
b/static/imgs/blog/33-release/cc93cf33-8f19-45dc-970f-1288994bf8a5.png differ
diff --git
a/static/imgs/blog/33-release/f38f6e7e-997f-4f5b-a888-ddea1ce7c6ca.png
b/static/imgs/blog/33-release/f38f6e7e-997f-4f5b-a888-ddea1ce7c6ca.png
new file mode 100644
index 00000000000..1ac3ffb117e
Binary files /dev/null and
b/static/imgs/blog/33-release/f38f6e7e-997f-4f5b-a888-ddea1ce7c6ca.png differ
