KrispauI commented on issue #5022:
URL: https://github.com/apache/eventmesh/issues/5022#issuecomment-2365067358
* Application scenario name
  **Serverless Solution for Connected Vehicle Services**
* Application scenario description
  In the connected vehicle scenario, the huge number of vehicles
and the variety of models from different automakers generate massive amounts of
data. A single vehicle can have hundreds of sensors continuously producing
data, and during peak hours (such as morning and evening rush hours), the
volume of connected vehicle data can surge dramatically. Additionally, the
automotive industry lacks standardized software development kits for connected
vehicles to reduce development costs and shorten time-to-market. This creates a
broad demand for Serverless solutions tailored to connected vehicle services.
  The Serverless solution for connected vehicle services can use
`EventMesh` as an event bus and event center. The vast amounts of data from
vehicle sensors, GPS devices, and cloud platforms can be ingested via API
gateways or IoT devices. Once processed by the event-driven architecture, the
solution provides real-time responses and scales smoothly to handle increased
traffic during peak times(such as morning and evening rush hours).
* Application scenario implementation proposal
  The Serverless solution for connected vehicle services, powered
by `EventMesh`, offers dynamic scaling and high flexibility in an event-driven
architecture. It meets the demand for high concurrency and rapid elasticity.It
can scale dynamically during traffic surges to handle highly concurrent data.
`EventMesh` also provides flexible routing capabilities, allowing events to be
routed to different systems and services based on customizable configuration
rules.
<p align="center">
<img
src="https://github.com/user-attachments/assets/9b14da5d-7b03-40a3-a71a-cc9b728aa7c8";
width="80%" />
</p>
  The diagram above illustrates the Serverless solution for
connected vehicle services. First, data can be cleaned, filtered using the
filter and transformer capabilities of `EventMesh`,then data is processed via
function computation.After processing, the data is stored in distributed object
storage, and events are generated. `EventMesh` routes these events to the
appropriate services based on predefined configuration rules. These services
include peak-shaving and valley-filling consumption services, AI-based
intelligent recommendation services, and multiple departmental business
services. This architecture allows each service to respond only to relevant
events without coupling to the data source directly.
  In addition, this solution offers features such as automatic
scaling, fault tolerance with retry mechanisms, and cross-regional support,
ensuring reliable event delivery even under high-load conditions. With
`EventMesh`, external Webhooks can also be integrated, allowing events to be
pushed to other systems or third-party services, facilitating future service
expansion.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
