This is an automated email from the ASF dual-hosted git repository.
chenguangsheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-eventmesh-site.git
The following commit(s) were added to refs/heads/master by this push:
new e52f72e3 Update introduction.md
e52f72e3 is described below
commit e52f72e3ca544060fb89bba709ca18bd89231ff9
Author: Eason Chen <[email protected]>
AuthorDate: Thu Feb 16 20:02:10 2023 +0800
Update introduction.md
---
docs/introduction.md | 39 ++++++++++++++-------------------------
1 file changed, 14 insertions(+), 25 deletions(-)
diff --git a/docs/introduction.md b/docs/introduction.md
index 991f81e1..e36f37f2 100644
--- a/docs/introduction.md
+++ b/docs/introduction.md
@@ -12,31 +12,20 @@ sidebar_position: 0
[](https://github.com/apache/incubator-eventmesh/releases)
[](https://join.slack.com/t/apacheeventmesh/shared_invite/zt-16y1n77va-q~JepYy3RqpkygDYmQaQbw)
-**Apache EventMesh (Incubating)** is a dynamic event-driven application
runtime used to decouple the application and backend middleware layer, which
supports a wide range of use cases that encompass complex multi-cloud, widely
distributed topologies using diverse technology stacks.
+**Apache EventMesh (Incubating)** is a fully serverless platform used to build
distributed
[event-driven](https://en.wikipedia.org/wiki/Event-driven_architecture)
applications.
## Features
-- **Communication Protocol**: EventMesh could communicate with clients with
TCP, HTTP, or gRPC.
-- **CloudEvents**: EventMesh supports the
[CloudEvents](https://cloudevents.io) specification as the format of the
events. CloudEvents is a specification for describing event data in common
formats to provide interoperability across services, platforms, and systems.
-- **Schema Registry**: EventMesh implements a schema registry that receives
and stores schemas from clients and provides an interface for other clients to
retrieve schemas.
-- **Observability**: EventMesh exposed a range of metrics, such as the average
latency of the HTTP protocol and the number of delivered messages. The metrics
could be collected and analyzed with Prometheus or OpenTelemetry.
-- **Event Workflow Orchestration**: EventMesh Workflow could receive an event
and decide which command to trigger next based on the workflow definitions and
the current workflow state. The workflow definition could be written with the
[Serverless Workflow](https://serverlessworkflow.io) DSL.
-
-## Components
-
-Apache EventMesh (Incubating) consists of multiple components that integrate
different middlewares and messaging protocols to enhance the functionalities of
the application runtime.
-
-- **eventmesh-runtime**: The middleware that transmits events between
producers and consumers, which supports cloud-native apps and microservices.
-- **eventmesh-sdk-java**: The Java SDK that supports HTTP, TCP, and
[gRPC](https://grpc.io) protocols.
-- **eventmesh-connector-plugin**: The collection of plugins that connects
middlewares such as [Apache Kafka](https://kafka.apache.org), [Apache
RocketMQ](https://rocketmq.apache.org), [Apache
Pulsar](https://pulsar.apache.org/), and [Redis](https://redis.io).
-- **eventmesh-registry-plugin**: The collection of plugins that integrate
service registries such as [Nacos](https://nacos.io) and
[etcd](https://etcd.io).
-- **eventmesh-security-plugin**: The collection of plugins that implement
security mechanisms, such as ACL (access control list), authentication, and
authorization.
-- **eventmesh-protocol-plugin**: The collection of plugins that implement
messaging protocols, such as [CloudEvents](https://cloudevents.io) and
[MQTT](https://mqtt.org).
-- **eventmesh-admin**: The control plane that manages clients, topics, and
subscriptions.
-
-## Contributors
-
-Each contributor has played an important role in promoting the robust
development of Apache EventMesh (Incubating). We sincerely appreciate all
contributors who have contributed code and documents. The following is the list
of contributors in EventMesh-related repositories.
-
--
[apache/incubator-eventmesh](https://github.com/apache/incubator-eventmesh/graphs/contributors)
--
[apache/incubator-eventmesh-site](https://github.com/apache/incubator-eventmesh-site/graphs/contributors)
+Apache EventMesh (Incubating) has a vast amount of features to help users
achieve their goals. Let us share with you some of the key features EventMesh
has to offer:
+
+- Built around the [CloudEvents](https://cloudevents.io) specification.
+- Rapidty extendsible language sdk around [gRPC](https://grpc.io) protocols.
+- Rapidty extendsible middleware by connectors such as [Apache
RocketMQ](https://rocketmq.apache.org), [Apache
Kafka](https://kafka.apache.org), [Apache Pulsar](https://pulsar.apache.org),
[RabbitMQ](https://rabbitmq.com), [Redis](https://redis.io),
[Pravega](https://cncf.pravega.io), and
[RDMS](https://en.wikipedia.org/wiki/Relational_database)(in progress) using
[JDBC](https://en.wikipedia.org/wiki/Java_Database_Connectivity).
+- Rapidty extendsible controller such as
[Consul](https://consulproject.org/en/), [Nacos](https://nacos.io),
[ETCD](https://etcd.io) and [Zookeeper](https://zookeeper.apache.org/).
+- Guaranteed at-least-once delivery.
+- Deliver events between multiple EventMesh deployments.
+- Event schema management by catalog service.
+- Powerful event orchestration by [Serverless
workflow](https://serverlessworkflow.io/) engine.
+- Powerful event filtering and transformation.
+- Rapid, seamless scalability.
+- Easy Function develop and framework integration.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
