Most people experience event-driven systems without realizing it. You book a ride, place an order, receive a notification, browse a product, or interact with a social platform\u2014and behind that simple action, multiple systems may respond to what just happened.<\/p>\n\n\n\n
That is the basic idea behind Event-Driven Architecture (EDA)<\/strong>.<\/p>\n\n\n\n Instead of making one system control every step, applications can publish events such as Ride Requested<\/em>, Order Placed<\/em>, Payment Completed<\/em>, or User Viewed Product<\/em>. Other services can listen for those events and take action independently. The concept sounds simple. At large companies, however, it becomes a powerful way to connect services and process large amounts of real-time information.<\/p>\n\n\n\n Let’s look at two real-world examples.<\/p>\n\n\n\n Think about what happens when you request a ride. Your request isn’t relevant to just one system. Pricing, driver matching, notifications, trip processing, payments, analytics, and other services may need information about what is happening.<\/p>\n\n\n\n Uber has publicly described Apache Kafka as a major part of its technology infrastructure. Its engineering teams use Kafka as a messaging and data-streaming layer connecting different parts of the platform. Rider and driver application events can flow through Kafka to different downstream consumers for analytics and other processing.<\/p>\n\n\n\n For example: Ride Requested \u2192 Event Published \u2192 Multiple Services React<\/strong><\/p>\n\n\n\n The important idea isn’t simply the technology being used. It’s that a business event can become useful to multiple systems without requiring the original service to directly coordinate every downstream action. This approach can help large platforms evolve as new services and capabilities are introduced.<\/p>\n\n\n\n Another example can be seen in large professional networking platforms. When users interact with a platform, activities such as page views, searches, clicks, and other application events can become data streams.<\/p>\n\n\n\n LinkedIn developed Apache Kafka as part of its infrastructure and has described Kafka as a central part of its data and messaging ecosystem. Its engineering teams have used Kafka for activity tracking, analytics, monitoring, messaging, and other distributed-system use cases.<\/p>\n\n\n\n Imagine a simple event: User Viewed Job \u2192 Event<\/strong><\/p>\n\n\n\n That event can be useful to different systems for different purposes, such as analytics, recommendations, monitoring, or other downstream processing. The service generating the event doesn’t necessarily need to know everything that will happen afterward.<\/p>\n\n\n\n That is one of the strengths of event-driven thinking: One Event \u2192 Multiple Consumers<\/strong><\/p>\n\n\n\n Although these systems serve different business needs, the underlying challenge is similar:<\/p>\n\n\n\n Something happens\u2014and multiple systems need to know about it.<\/strong><\/p>\n\n\n\n That’s where event-driven architecture becomes useful. A simplified flow looks like this:<\/p>\n\n\n\n Business Action \u2192 Event \u2192 Event Platform \u2192 Multiple Consumers<\/strong><\/p>\n\n\n\n For example:<\/p>\n\n\n\n Order Placed<\/strong> Each service can respond according to its own responsibility. This can reduce unnecessary dependencies between services and make it easier to introduce new consumers later.<\/p>\n\n\n\n One important distinction is worth making.<\/p>\n\n\n\n Event-Driven Architecture is an architectural approach. Apache Kafka is one technology that can be used to implement event-driven systems.<\/strong><\/p>\n\n\n\n Other technologies can also support event-driven architectures, depending on the requirements of the business. The architecture comes first. The technology is selected based on factors such as:<\/p>\n\n\n\n Choosing a technology should therefore come after understanding the actual problem the business needs to solve.<\/p>\n\n\n\n EDA can be particularly useful when an organization needs to:<\/p>\n\n\n\n But EDA isn’t automatically the right answer for every application. Adding event brokers, asynchronous processing, monitoring, schemas, retries, and failure-handling mechanisms also introduces operational complexity. The goal isn’t to make every system event-driven. The goal is to use events where they solve a real business problem.<\/p>\n\n\n\n Event-driven architecture may sound like a purely technical concept, but its real value is business-oriented. Modern digital businesses need systems that can respond quickly when something changes.<\/p>\n\n\n\n An order is placed, payment is completed, customer interacts with an application, transaction is processed. Each of these actions can become an event that other systems can respond to independently. Different businesses may have different requirements and different implementations, but the underlying principle remains the same:<\/p>\n\n\n\n When something important happens, let the systems that care about it respond.<\/strong><\/p>\n\n\n\n That is the idea behind Event-Driven Architecture<\/strong>. As businesses become more distributed, real-time, and connected, designing systems around events can help organizations build applications that are more responsive and easier to extend.<\/p>\n\n\n\n MALtech \u2014 Technology beyond EDGE<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":" Most people experience event-driven systems without realizing it. You book a ride, place an order, receive a notification, browse a product, or interact with a social platform\u2014and behind that simple action, multiple systems may respond to what just happened. That is the basic idea behind Event-Driven Architecture (EDA). Instead of making one system control every […]<\/p>\n","protected":false},"author":7,"featured_media":775,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ocean_front_end_style_editor":"no","ocean_post_layout":"","ocean_both_sidebars_style":"","ocean_both_sidebars_content_width":0,"ocean_both_sidebars_sidebars_width":0,"ocean_sidebar":"","ocean_second_sidebar":"","ocean_disable_margins":"enable","ocean_add_body_class":"","ocean_shortcode_before_top_bar":"","ocean_shortcode_after_top_bar":"","ocean_shortcode_before_header":"","ocean_shortcode_after_header":"","ocean_has_shortcode":"","ocean_shortcode_after_title":"","ocean_shortcode_before_footer_widgets":"","ocean_shortcode_after_footer_widgets":"","ocean_shortcode_before_footer_bottom":"","ocean_shortcode_after_footer_bottom":"","ocean_display_top_bar":"default","ocean_display_header":"default","ocean_header_style":"","ocean_center_header_left_menu":"","ocean_custom_header_template":"","ocean_custom_logo":0,"ocean_custom_retina_logo":0,"ocean_custom_logo_max_width":0,"ocean_custom_logo_tablet_max_width":0,"ocean_custom_logo_mobile_max_width":0,"ocean_custom_logo_max_height":0,"ocean_custom_logo_tablet_max_height":0,"ocean_custom_logo_mobile_max_height":0,"ocean_header_custom_menu":"","ocean_menu_typo_font_family":"","ocean_menu_typo_font_subset":"","ocean_menu_typo_font_size":0,"ocean_menu_typo_font_size_tablet":0,"ocean_menu_typo_font_size_mobile":0,"ocean_menu_typo_font_size_unit":"px","ocean_menu_typo_font_weight":"","ocean_menu_typo_font_weight_tablet":"","ocean_menu_typo_font_weight_mobile":"","ocean_menu_typo_transform":"","ocean_menu_typo_transform_tablet":"","ocean_menu_typo_transform_mobile":"","ocean_menu_typo_line_height":0,"ocean_menu_typo_line_height_tablet":0,"ocean_menu_typo_line_height_mobile":0,"ocean_menu_typo_line_height_unit":"","ocean_menu_typo_spacing":0,"ocean_menu_typo_spacing_tablet":0,"ocean_menu_typo_spacing_mobile":0,"ocean_menu_typo_spacing_unit":"","ocean_menu_link_color":"","ocean_menu_link_color_hover":"","ocean_menu_link_color_active":"","ocean_menu_link_background":"","ocean_menu_link_hover_background":"","ocean_menu_link_active_background":"","ocean_menu_social_links_bg":"","ocean_menu_social_hover_links_bg":"","ocean_menu_social_links_color":"","ocean_menu_social_hover_links_color":"","ocean_disable_title":"default","ocean_disable_heading":"default","ocean_post_title":"","ocean_post_subheading":"","ocean_post_title_style":"","ocean_post_title_background_color":"","ocean_post_title_background":0,"ocean_post_title_bg_image_position":"","ocean_post_title_bg_image_attachment":"","ocean_post_title_bg_image_repeat":"","ocean_post_title_bg_image_size":"","ocean_post_title_height":0,"ocean_post_title_bg_overlay":0.5,"ocean_post_title_bg_overlay_color":"","ocean_disable_breadcrumbs":"default","ocean_breadcrumbs_color":"","ocean_breadcrumbs_separator_color":"","ocean_breadcrumbs_links_color":"","ocean_breadcrumbs_links_hover_color":"","ocean_display_footer_widgets":"default","ocean_display_footer_bottom":"default","ocean_custom_footer_template":"","ocean_post_oembed":"","ocean_post_self_hosted_media":"","ocean_post_video_embed":"","ocean_link_format":"","ocean_link_format_target":"self","ocean_quote_format":"","ocean_quote_format_link":"post","ocean_gallery_link_images":"on","ocean_gallery_id":[],"footnotes":""},"categories":[6],"tags":[64,67,65,61,66,63,62],"class_list":["post-774","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technology","tag-apache-kafka","tag-distributed-systems","tag-eda","tag-enterprise-technology","tag-event-driven-architecture","tag-real-time-systems","tag-software-architecture","entry","has-media"],"yoast_head":"\n1. Uber: When a Ride Becomes an Event<\/strong><\/h2>\n\n\n\n
2. LinkedIn: Turning User Activity Into Data<\/strong><\/h2>\n\n\n\n
What These Examples Have in Common<\/strong><\/h2>\n\n\n\n
<\/strong>\u2193
Event Published<\/strong>
<\/strong> <\/strong>\u2193
Payment | Inventory | Notifications | Analytics | Delivery<\/strong><\/p>\n\n\n\nEDA Is More Than Just Kafka<\/strong><\/h2>\n\n\n\n
\n
When Should a Business Consider EDA?<\/strong><\/h2>\n\n\n\n
\n
The Bigger Picture<\/strong><\/h2>\n\n\n\n