BuildStuff - Lessons Learned from 2000 Event Driven Microservices
0 likes156 views
The document discusses lessons learned from Wix's implementation of event-driven microservices, detailing challenges faced such as message production failures, processing out-of-order messages, and issues with large payloads. It outlines solutions for each challenge, including using robust brokers, employing resilient producers, and enhancing debugging tools. The overall takeaway emphasizes the importance of decoupling, resilience, and scalability achieved through event-driven architecture.
1 of 61
Downloaded 13 times
Ad
Recommended
Introduction to Docker Compose | Docker Intermediate Workshop
Introduction to Docker Compose | Docker Intermediate WorkshopAjeet Singh Raina Docker Compose allows users to define and run multi-container Docker applications. With Docker Compose, a YAML file is used to configure an application's services, and with a single command, all the services can be started from the configuration. Docker Compose is a three step process - services are defined in a Dockerfile, then in a Docker Compose file, and then run with docker-compose up. It supports volumes, networks, and environmental variables. Docker Compose can be used for development, testing, and production environments across different platforms.
FedScoop Public Sector Innovation Summit DOD Enterprise DevSecOps Initiative ...
FedScoop Public Sector Innovation Summit DOD Enterprise DevSecOps Initiative ...scoopnewsgroup This document outlines the DoD Enterprise DevSecOps Initiative, which aims to establish DevSecOps capabilities across the DoD. It discusses establishing shared DevSecOps tools and services to enable rapid and secure application development. This includes selecting best-of-breed tools, creating a standardized security container, and designing a scalable microservices architecture. The initiative will provide DevSecOps pipelines, training, and support to programs to help drive adoption of agile software development practices. Establishing an enterprise DevSecOps capability is intended to enhance cybersecurity, increase operational flexibility, and help modernize the DoD's approach to software development.
Cell-based Architecture: An Emerging Architecture Pattern for Agile Integrati...
Cell-based Architecture: An Emerging Architecture Pattern for Agile Integrati...Asanka Abeysinghe The document discusses cell-based architecture as an emerging pattern for agile integration, highlighting its components such as microservices and integration strategies. It emphasizes the need for a structured approach to address legacy systems and dependency management while improving developer experience and observability. Additionally, it introduces tools like Cellery and Ballerina for building and managing microservices in a cloud-native environment.
Programación Reactiva con Spring WebFlux
Programación Reactiva con Spring WebFluxParadigma Digital El meetup Spring Madrid - Webflux se centra en la programación reactiva utilizando la especificación de 'reactive streams' y la implementación de Spring Webflux. Este documento incluye ejemplos de implementación, describe la diferencia entre Spring MVC y Spring Webflux, y aborda características como el manejo de solicitudes no bloqueantes y el uso de eventos enviados por el servidor. También se discuten aspectos prácticos como la creación de servicios REST, pruebas y el uso de Websockets.
いまさら、AWSのネットワーク設計
いまさら、AWSのネットワーク設計Serverworks Co.,Ltd. AWSに関するお問い合わせ：<a href="https://www.serverworks.co.jp/contact/" >https://www.serverworks.co.jp/contact/</a>
サーバーワークスエンジニアブログ：http://blog.serverworks.co.jp/tech/
当社の髙田が2018年10月27日開催のJAWS-UG関西女子会にて登壇した際の発表資料です。
※免責事項 本書の情報・資料の記載には注意を払っておりますが、記載された情報の内容が正確であるか、更新時期が適切かどうかなどについて一切保証するものではありません。
また、記載された情報またはその誤りなど、本書記載の情報に関連して生じた損害または障害などに関しては、その理由の如何に関わらず、またその損害等が直接的か間接的かを問わず、一切責任を負うものではありません。
Soluciones Dynatrace
Soluciones DynatraceInnovation Strategies This document describes Dynatrace's full-stack application monitoring solution. It can automatically monitor entire application stacks from the user experience down to code level. Dynatrace provides a unified real-time model called Smartscape that maps out the entire environment and all transaction dependencies. It also uses artificial intelligence for anomaly detection since environmental complexity is too much for humans to fully analyze. Deployments can be either SaaS or on-premises to provide flexibility. Dynatrace can monitor dynamic container environments across all major platforms.
CNCF and Cloud Native Intro
CNCF and Cloud Native IntroCloud Native Bangalore This document discusses cloud native computing and the Cloud Native Computing Foundation (CNCF). It defines cloud native as a new paradigm for developing, deploying, and running applications using open source software like microservices, containers, and container orchestration. The CNCF is responsible for building sustainable ecosystems of cloud native software and serves as the home for many fastest growing open source projects like Kubernetes, Prometheus, and Envoy. The document outlines CNCF projects at different maturity levels and describes how cloud native technologies empower organizations to build scalable distributed applications using open standards.
Rego Deep Dive
Rego Deep DiveTorin Sandall This document provides an introduction and overview of Open Policy Agent (OPA). It discusses how OPA can be used to add fine-grained policy controls to other projects. Key points include:
- OPA allows integrating policy decisions from a project into OPA and offloading policy logic. Policies can be authored in OPA and decisions retrieved.
- Policies are invoked by sending decision requests to OPA APIs. The input is JSON and the response is also JSON.
- Simple policies involve looking up values, comparing values, assigning variables, and creating rules with heads and bodies. Rules with the same head are OR'd together.
- Policies can handle arrays and iteration by using an
Designing Cloud Native Applications with Kubernetes
Designing Cloud Native Applications with KubernetesBilgin Ibryam The document discusses the key principles and benefits of designing cloud-native applications using Kubernetes, emphasizing the importance of automation, microservices, and containerization. It outlines key characteristics of cloud-native applications, Kubernetes abstractions, container design principles, and various design patterns. Additionally, it highlights the advantages of using Kubernetes, such as dynamic application placement, declarative service deployments, and application resilience.
마이크로서비스 기반 클라우드 아키텍처 구성 모범 사례 - 윤석찬 (AWS 테크에반젤리스트)
마이크로서비스 기반 클라우드 아키텍처 구성 모범 사례 - 윤석찬 (AWS 테크에반젤리스트) Amazon Web Services Korea 1. The document discusses microservices architecture and how Netflix transitioned from a monolithic architecture to microservices. Key aspects discussed include breaking the monolith into many small, independent services that are loosely coupled.
2. Netflix's microservices architecture is composed of hundreds of microservices running on thousands of servers. Each service focuses on doing a small, well-defined piece of work. Services communicate through well-defined APIs and share no code or databases.
3. The document provides examples of how other companies like Samsung and Vingle have also adopted microservices architectures on AWS, breaking monolithic applications into independent, scalable services. This allows for independent deployments, rapid innovation, and improved resilience.
API Management Part 1 - An Introduction to Azure API Management
API Management Part 1 - An Introduction to Azure API ManagementBizTalk360 The document is a presentation by Kent Weare covering Azure API Management, highlighting its role in enabling applications to communicate and the growth of APIs driven by mobile and cloud technologies. It discusses the importance of API management in businesses, providing services like authentication, analytics, and policy enforcement. Additionally, real-world examples showcase how companies leverage APIs to enhance their operations and customer engagement.
Lessons Learned from 2000 Event Driven Microservices - Reversim
Lessons Learned from 2000 Event Driven Microservices - ReversimNatan Silnitsky The document outlines lessons learned from operating 2000 event-driven microservices at Wix, addressing challenges such as producing message failures, out-of-order processing, and large payload sending. It describes the implementation of tools and techniques for resilience, including the use of Kafka and the development of Greyhound, which provides a resilient producer and consumer retries. Overall, the experience has led to improved decoupling, resilience, and scalability of microservices while maintaining data consistency.
Container Monitoring with Sysdig
Container Monitoring with SysdigSreenivas Makam This document discusses container monitoring using Sysdig. It begins with an introduction of the presenter and overview of existing Linux debugging tools and their limitations for container monitoring. It then summarizes Sysdig's architecture, features and examples for monitoring containers running on Docker, Kubernetes, Mesos and other platforms. The document concludes with references and demonstrations of Sysdig for monitoring a HAProxy load balancer and Kubernetes guestbook application.
Api observability
Api observability Red Hat This document provides an overview of service mesh and the Istio observability tool Kiali. It begins with an introduction to service mesh and what problems it addresses in microservices architectures. Istio is presented as an open source service mesh that provides traffic management, observability, and policy enforcement for microservices. Kiali is specifically discussed as a tool for visualizing the topology and traffic flow of services in an Istio mesh. The rest of the document provides an agenda and then a live demo of Kiali's features using the Bookinfo sample application on Istio.
Configuration As Code - Adoption of the Job DSL Plugin at Netflix
Configuration As Code - Adoption of the Job DSL Plugin at NetflixJustin Ryan The document discusses the adoption of the Job DSL plugin at Netflix to enhance the efficiency and automation of job configurations within their engineering teams. It describes the issues of job duplication, UI challenges, and alternatives, while emphasizing the benefits of using Groovy scripts for creating jobs programmatically. Additionally, it highlights use cases from other companies and outlines best practices for utilizing the Job DSL plugin effectively.
From APM to Business Monitoring with AppDynamics Analytics
From APM to Business Monitoring with AppDynamics AnalyticsAppDynamics The document discusses transitioning from Application Performance Monitoring (APM) to business monitoring utilizing AppDynamics analytics. It covers key topics such as data collection, visualization of business impact, advanced analytics, and troubleshooting infrastructure issues, emphasizing the integration of business and operations data. Additionally, the document outlines the importance of maximizing customer experience through actionable insights derived from analytics metrics.
8. Event Storming (P. Rayner).pdf
8. Event Storming (P. Rayner).pdfMikhail Andronov This document discusses EventStorming, a technique for collaboratively modeling complex domains through visualizing sequences of domain events. Key aspects include placing business-relevant events on a timeline to understand workflows and interactions, inviting both technical and business participants, and using the process to facilitate shared learning, clarify concepts, and smooth the transition to technologies like event sourcing. The primary goals are to uncover gaps and inconsistencies in understanding through conversation rather than documentation alone.
TF에서 팀 빌딩까지 9개월의 기록 : 성장하는 조직을 만드는 여정
TF에서 팀 빌딩까지 9개월의 기록 : 성장하는 조직을 만드는 여정Seongyun Byeon The document is primarily about icons created by Freepik, all licensed under Creative Commons 3.0. It repetitively emphasizes the licensing details for these icons from the Flaticon website. The information is highly redundant without additional content.
API Management in Azure
API Management in AzureTomasso Groenendijk The document discusses the API Management service on Microsoft Azure, launched in September 2014, which has seen significant adoption with over 30x growth compared to projections and several customers already in production. It outlines features including usability improvements, security options, and deployment strategies, as well as plans for future enhancements. The document also provides details on the demo of API management functionalities and contact information for further inquiries.
Kubernetes 101
Kubernetes 101Stanislav Pogrebnyak This document provides an overview of Kubernetes 101. It begins with asking why Kubernetes is needed and provides a brief history of the project. It describes containers and container orchestration tools. It then covers the main components of Kubernetes architecture including pods, replica sets, deployments, services, and ingress. It provides examples of common Kubernetes manifest files and discusses basic Kubernetes primitives. It concludes with discussing DevOps practices after adopting Kubernetes and potential next steps to learn more advanced Kubernetes topics.
Control Kubernetes Ingress and Egress Together with NGINX
Control Kubernetes Ingress and Egress Together with NGINXNGINX, Inc. The document discusses managing ingress and egress traffic in Kubernetes using NGINX, highlighting common challenges and solutions related to networking complexity in Kubernetes environments. It emphasizes the importance of layer 5-7 networking for enhanced security and traffic control, along with a live demo and configuration examples for implementing NGINX policies for traffic management. The document also touches on the growth of Kubernetes adoption and the necessity for integrated service meshes to address networking capabilities.
Fido Technical Overview
Fido Technical OverviewFIDO Alliance The document provides an overview of FIDO (Fast Identity Online) authentication, emphasizing the importance of user verification and secure key management to reduce scalable attacks. It discusses the operation of FIDO, including the use of authenticators, verification methods, and the separation of user verification from authentication, which enables flexibility and enhanced security. Additionally, it highlights the convenience of FIDO authentication through interoperability across different devices and applications.
Becoming a hyperledger aries developer learn things.online
Becoming a hyperledger aries developer learn things.onlinedjaber3 This document provides an overview and introduction to the course "Becoming a Hyperledger Aries Developer". The course focuses on building applications using Hyperledger Aries, which provides tools for decentralized identity and trust on the internet. It discusses key concepts like self-sovereign identity, decentralized identifiers, and zero-knowledge proofs. The course will teach students to understand the Aries architecture, communicate between agents using DIDComm, deploy and extend Aries agents, and issue and verify credentials.
Business Transactions with AppDynamics
Business Transactions with AppDynamicsAppDynamics The document provides an overview of business transactions in AppDynamics version 4.2, detailing confidential guidelines and best practices for monitoring and managing application performance. It outlines critical topics such as transaction detection, metrics, thresholds, and the management of production environments, while also highlighting resources for further learning and troubleshooting. Additionally, the document emphasizes the importance of user feedback for continuous improvement of the training content.
IBM Datapower Security Scenario with JWS & JWE
IBM Datapower Security Scenario with JWS & JWEsandipg123 This document describes setting up a microservices architecture with IBM Datapower for securing communication between services using JSON Web Tokens (JWT). It includes details on:
1) The topology used consisting of a Datapower gateway, MQ server, and laptop.
2) Commands to setup Docker containers for each component and generate keys/certificates.
3) Configuring Datapower policies for JWT signing, verification, encryption, and decryption to secure messages between the MQ server and Datapower gateway.
4) Testing the end-to-end flow by sending sample messages through the Datapower gateway.
DevSum - Lessons Learned from 2000 microservices
DevSum - Lessons Learned from 2000 microservicesNatan Silnitsky The document discusses lessons learned from operating over 2000 event-driven microservices at Wix, highlighting challenges such as message processing failures, out-of-order and duplicate messages, and difficulties in sending large payloads. It outlines various solutions implemented, including robust messaging through Kafka, implementing revision IDs to handle duplicates, and strategies for dealing with large data structures. The main conclusion is that embracing these solutions has resulted in more resilient and scalable microservices while maintaining low complexity and consistent data.
Wix+Confluent Meetup - Lessons Learned from 2000 Event Driven Microservices
Wix+Confluent Meetup - Lessons Learned from 2000 Event Driven MicroservicesNatan Silnitsky The document discusses lessons learned from managing 2000 event-driven microservices at Wix, focusing on challenges such as message failures, out-of-order processing, and large payloads. It highlights solutions like using a robust Kafka broker, compression techniques, and utilizing a resilient producer for better reliability. Overall, it emphasizes the importance of scalable, decoupled architectures that allow developers to maintain data consistency and streamline event processing.
More Related Content
What's hot (20)
CNCF and Cloud Native Intro
CNCF and Cloud Native IntroCloud Native Bangalore This document discusses cloud native computing and the Cloud Native Computing Foundation (CNCF). It defines cloud native as a new paradigm for developing, deploying, and running applications using open source software like microservices, containers, and container orchestration. The CNCF is responsible for building sustainable ecosystems of cloud native software and serves as the home for many fastest growing open source projects like Kubernetes, Prometheus, and Envoy. The document outlines CNCF projects at different maturity levels and describes how cloud native technologies empower organizations to build scalable distributed applications using open standards.
Rego Deep Dive
Rego Deep DiveTorin Sandall This document provides an introduction and overview of Open Policy Agent (OPA). It discusses how OPA can be used to add fine-grained policy controls to other projects. Key points include:
- OPA allows integrating policy decisions from a project into OPA and offloading policy logic. Policies can be authored in OPA and decisions retrieved.
- Policies are invoked by sending decision requests to OPA APIs. The input is JSON and the response is also JSON.
- Simple policies involve looking up values, comparing values, assigning variables, and creating rules with heads and bodies. Rules with the same head are OR'd together.
- Policies can handle arrays and iteration by using an
Designing Cloud Native Applications with Kubernetes
Designing Cloud Native Applications with KubernetesBilgin Ibryam The document discusses the key principles and benefits of designing cloud-native applications using Kubernetes, emphasizing the importance of automation, microservices, and containerization. It outlines key characteristics of cloud-native applications, Kubernetes abstractions, container design principles, and various design patterns. Additionally, it highlights the advantages of using Kubernetes, such as dynamic application placement, declarative service deployments, and application resilience.
마이크로서비스 기반 클라우드 아키텍처 구성 모범 사례 - 윤석찬 (AWS 테크에반젤리스트)
마이크로서비스 기반 클라우드 아키텍처 구성 모범 사례 - 윤석찬 (AWS 테크에반젤리스트) Amazon Web Services Korea 1. The document discusses microservices architecture and how Netflix transitioned from a monolithic architecture to microservices. Key aspects discussed include breaking the monolith into many small, independent services that are loosely coupled.
2. Netflix's microservices architecture is composed of hundreds of microservices running on thousands of servers. Each service focuses on doing a small, well-defined piece of work. Services communicate through well-defined APIs and share no code or databases.
3. The document provides examples of how other companies like Samsung and Vingle have also adopted microservices architectures on AWS, breaking monolithic applications into independent, scalable services. This allows for independent deployments, rapid innovation, and improved resilience.
API Management Part 1 - An Introduction to Azure API Management
API Management Part 1 - An Introduction to Azure API ManagementBizTalk360 The document is a presentation by Kent Weare covering Azure API Management, highlighting its role in enabling applications to communicate and the growth of APIs driven by mobile and cloud technologies. It discusses the importance of API management in businesses, providing services like authentication, analytics, and policy enforcement. Additionally, real-world examples showcase how companies leverage APIs to enhance their operations and customer engagement.
Lessons Learned from 2000 Event Driven Microservices - Reversim
Lessons Learned from 2000 Event Driven Microservices - ReversimNatan Silnitsky The document outlines lessons learned from operating 2000 event-driven microservices at Wix, addressing challenges such as producing message failures, out-of-order processing, and large payload sending. It describes the implementation of tools and techniques for resilience, including the use of Kafka and the development of Greyhound, which provides a resilient producer and consumer retries. Overall, the experience has led to improved decoupling, resilience, and scalability of microservices while maintaining data consistency.
Container Monitoring with Sysdig
Container Monitoring with SysdigSreenivas Makam This document discusses container monitoring using Sysdig. It begins with an introduction of the presenter and overview of existing Linux debugging tools and their limitations for container monitoring. It then summarizes Sysdig's architecture, features and examples for monitoring containers running on Docker, Kubernetes, Mesos and other platforms. The document concludes with references and demonstrations of Sysdig for monitoring a HAProxy load balancer and Kubernetes guestbook application.
Api observability
Api observability Red Hat This document provides an overview of service mesh and the Istio observability tool Kiali. It begins with an introduction to service mesh and what problems it addresses in microservices architectures. Istio is presented as an open source service mesh that provides traffic management, observability, and policy enforcement for microservices. Kiali is specifically discussed as a tool for visualizing the topology and traffic flow of services in an Istio mesh. The rest of the document provides an agenda and then a live demo of Kiali's features using the Bookinfo sample application on Istio.
Configuration As Code - Adoption of the Job DSL Plugin at Netflix
Configuration As Code - Adoption of the Job DSL Plugin at NetflixJustin Ryan The document discusses the adoption of the Job DSL plugin at Netflix to enhance the efficiency and automation of job configurations within their engineering teams. It describes the issues of job duplication, UI challenges, and alternatives, while emphasizing the benefits of using Groovy scripts for creating jobs programmatically. Additionally, it highlights use cases from other companies and outlines best practices for utilizing the Job DSL plugin effectively.
From APM to Business Monitoring with AppDynamics Analytics
From APM to Business Monitoring with AppDynamics AnalyticsAppDynamics The document discusses transitioning from Application Performance Monitoring (APM) to business monitoring utilizing AppDynamics analytics. It covers key topics such as data collection, visualization of business impact, advanced analytics, and troubleshooting infrastructure issues, emphasizing the integration of business and operations data. Additionally, the document outlines the importance of maximizing customer experience through actionable insights derived from analytics metrics.
8. Event Storming (P. Rayner).pdf
8. Event Storming (P. Rayner).pdfMikhail Andronov This document discusses EventStorming, a technique for collaboratively modeling complex domains through visualizing sequences of domain events. Key aspects include placing business-relevant events on a timeline to understand workflows and interactions, inviting both technical and business participants, and using the process to facilitate shared learning, clarify concepts, and smooth the transition to technologies like event sourcing. The primary goals are to uncover gaps and inconsistencies in understanding through conversation rather than documentation alone.
TF에서 팀 빌딩까지 9개월의 기록 : 성장하는 조직을 만드는 여정
TF에서 팀 빌딩까지 9개월의 기록 : 성장하는 조직을 만드는 여정Seongyun Byeon The document is primarily about icons created by Freepik, all licensed under Creative Commons 3.0. It repetitively emphasizes the licensing details for these icons from the Flaticon website. The information is highly redundant without additional content.
API Management in Azure
API Management in AzureTomasso Groenendijk The document discusses the API Management service on Microsoft Azure, launched in September 2014, which has seen significant adoption with over 30x growth compared to projections and several customers already in production. It outlines features including usability improvements, security options, and deployment strategies, as well as plans for future enhancements. The document also provides details on the demo of API management functionalities and contact information for further inquiries.
Kubernetes 101
Kubernetes 101Stanislav Pogrebnyak This document provides an overview of Kubernetes 101. It begins with asking why Kubernetes is needed and provides a brief history of the project. It describes containers and container orchestration tools. It then covers the main components of Kubernetes architecture including pods, replica sets, deployments, services, and ingress. It provides examples of common Kubernetes manifest files and discusses basic Kubernetes primitives. It concludes with discussing DevOps practices after adopting Kubernetes and potential next steps to learn more advanced Kubernetes topics.
Control Kubernetes Ingress and Egress Together with NGINX
Control Kubernetes Ingress and Egress Together with NGINXNGINX, Inc. The document discusses managing ingress and egress traffic in Kubernetes using NGINX, highlighting common challenges and solutions related to networking complexity in Kubernetes environments. It emphasizes the importance of layer 5-7 networking for enhanced security and traffic control, along with a live demo and configuration examples for implementing NGINX policies for traffic management. The document also touches on the growth of Kubernetes adoption and the necessity for integrated service meshes to address networking capabilities.
Fido Technical Overview
Fido Technical OverviewFIDO Alliance The document provides an overview of FIDO (Fast Identity Online) authentication, emphasizing the importance of user verification and secure key management to reduce scalable attacks. It discusses the operation of FIDO, including the use of authenticators, verification methods, and the separation of user verification from authentication, which enables flexibility and enhanced security. Additionally, it highlights the convenience of FIDO authentication through interoperability across different devices and applications.
Becoming a hyperledger aries developer learn things.online
Becoming a hyperledger aries developer learn things.onlinedjaber3 This document provides an overview and introduction to the course "Becoming a Hyperledger Aries Developer". The course focuses on building applications using Hyperledger Aries, which provides tools for decentralized identity and trust on the internet. It discusses key concepts like self-sovereign identity, decentralized identifiers, and zero-knowledge proofs. The course will teach students to understand the Aries architecture, communicate between agents using DIDComm, deploy and extend Aries agents, and issue and verify credentials.
Business Transactions with AppDynamics
Business Transactions with AppDynamicsAppDynamics The document provides an overview of business transactions in AppDynamics version 4.2, detailing confidential guidelines and best practices for monitoring and managing application performance. It outlines critical topics such as transaction detection, metrics, thresholds, and the management of production environments, while also highlighting resources for further learning and troubleshooting. Additionally, the document emphasizes the importance of user feedback for continuous improvement of the training content.
IBM Datapower Security Scenario with JWS & JWE
IBM Datapower Security Scenario with JWS & JWEsandipg123 This document describes setting up a microservices architecture with IBM Datapower for securing communication between services using JSON Web Tokens (JWT). It includes details on:
1) The topology used consisting of a Datapower gateway, MQ server, and laptop.
2) Commands to setup Docker containers for each component and generate keys/certificates.
3) Configuring Datapower policies for JWT signing, verification, encryption, and decryption to secure messages between the MQ server and Datapower gateway.
4) Testing the end-to-end flow by sending sample messages through the Datapower gateway.
Similar to BuildStuff - Lessons Learned from 2000 Event Driven Microservices (20)
DevSum - Lessons Learned from 2000 microservices
DevSum - Lessons Learned from 2000 microservicesNatan Silnitsky The document discusses lessons learned from operating over 2000 event-driven microservices at Wix, highlighting challenges such as message processing failures, out-of-order and duplicate messages, and difficulties in sending large payloads. It outlines various solutions implemented, including robust messaging through Kafka, implementing revision IDs to handle duplicates, and strategies for dealing with large data structures. The main conclusion is that embracing these solutions has resulted in more resilient and scalable microservices while maintaining low complexity and consistent data.
Wix+Confluent Meetup - Lessons Learned from 2000 Event Driven Microservices
Wix+Confluent Meetup - Lessons Learned from 2000 Event Driven MicroservicesNatan Silnitsky The document discusses lessons learned from managing 2000 event-driven microservices at Wix, focusing on challenges such as message failures, out-of-order processing, and large payloads. It highlights solutions like using a robust Kafka broker, compression techniques, and utilizing a resilient producer for better reliability. Overall, it emphasizes the importance of scalable, decoupled architectures that allow developers to maintain data consistency and streamline event processing.
GeeCon - Lessons Learned from 2000 microservices
GeeCon - Lessons Learned from 2000 microservicesNatan Silnitsky This document discusses the lessons learned from managing 2000 event-driven microservices at Wix, highlighting challenges such as message production failures, out-of-order processing, and sending large payloads. It outlines solutions implemented over the years, including resilient producers, compression techniques, and improved monitoring tools. Overall, these experiences have led to more decoupled, resilient, and scalable microservices while maintaining data consistency.
Battle-tested event-driven patterns for your microservices architecture - Sca...
Battle-tested event-driven patterns for your microservices architecture - Sca...Natan Silnitsky Natan Silnitsky discusses event-driven patterns for microservices architecture utilized at Wix, which manages over 200 million registered users and 2,000 microservices. The document outlines how event-driven communication enhances reliability, decoupling, and scalability through the use of message brokers like Kafka. Various use cases and advanced patterns are presented, including 0-latency key-value stores and transaction handling for e-commerce applications.
Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL
Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.ILNatan Silnitsky Wix has transitioned its distributed system to a fully CRUD-based microservices architecture, moving away from a hybrid model of CRUD and event sourcing. This shift emphasizes standardization, managed infrastructure through automated code generation, and a decoupled architecture to enhance system resilience. Advanced tools have been incorporated to improve development speed and optimize scale and performance.
Battle Tested Event-Driven Patterns for your Microservices Architecture
Battle Tested Event-Driven Patterns for your Microservices ArchitectureNatan Silnitsky The document discusses event-driven microservices architecture employed by Wix, showcasing patterns such as consume and project, 0-latency key-value store, and transactional event processing. It highlights the advantages of using message brokers for communication and reliability, emphasizing the scalability and resilience of decoupled microservices. The presentation concludes by referring to various resources on event-driven architecture and the benefits it brings to microservices development.
Battle Tested Event-Driven Patterns for your Microservices Architecture - Ris...
Battle Tested Event-Driven Patterns for your Microservices Architecture - Ris...Natan Silnitsky The document discusses event-driven microservices architecture patterns employed by Wix to enhance scalability, resilience, and decoupling of services. Key topics include the use of message brokers, request-reply communication models, and strategies for managing data with Kafka. It highlights practical use cases, such as idempotent payments and event processing, and provides insights into implementing these patterns effectively.
Building event-driven (Micro)Services with Apache Kafka
Building event-driven (Micro)Services with Apache Kafka Guido Schmutz The document provides an overview of building event-driven (micro)services using Apache Kafka, discussing the transition from traditional architectures to microservices, their benefits, and integration strategies. It covers the challenges of service interactions, streaming data sources, and integrating legacy systems with Kafka's capabilities in handling event streams and data analytics. Additionally, it emphasizes the importance of service autonomy and the advantages of using Kafka as an event broker and store.
Jax london - Battle-tested event-driven patterns for your microservices archi...
Jax london - Battle-tested event-driven patterns for your microservices archi...Natan Silnitsky The document discusses event-driven microservices architecture, detailing patterns and use cases for building decoupled and scalable systems, particularly in the context of Wix.com, which has over 200 million users. Key topics include the implementation of Kafka for message brokering, communication models, and examples of microservices in e-commerce applications. Natan Silnitsky emphasizes the importance of robust communication, reliability, and transaction handling within event-driven systems.
Battle-tested event-driven patterns for your microservices architecture - Sca...
Battle-tested event-driven patterns for your microservices architecture - Sca...Natan Silnitsky The document outlines various event-driven architecture patterns utilized by Wix, including microservices communication, message brokers, and event-driven use cases. It emphasizes the benefits of decoupling, resilience, and scalability through features like zero-latency key-value stores, transactions, and robust data handling. The presentation includes practical examples and discusses a Scala/Java SDK for Apache Kafka developed by Wix developers.
Event driven microservices
Event driven microservicesAnthony Martin Event-driven microservices communicate asynchronously using events published to an event backbone like Apache Kafka. This approach offers benefits like loose coupling, responsiveness, and independent scalability. Various patterns can be used to manage complexity, including having each service store its own data, using Kafka log compaction to replicate data across services, orchestrating multi-step processes through sagas, and separating read and write concerns with CQRS. Event storming helps identify the events, actors, and data in an application to structure it in an event-driven way.
Battle Tested Event-Driven Patterns for your Microservices Architecture - Dev...
Battle Tested Event-Driven Patterns for your Microservices Architecture - Dev...Natan Silnitsky The document discusses event-driven microservices architecture and patterns employed by Wix.com to enhance decoupling, resilience, and scalability in their backend infrastructure which serves over 200 million registered users worldwide. It covers various event-driven patterns such as consume and project, 0-latency key-value stores, and events in transactions, while emphasizing the use of Kafka for message brokering and communication among services. Additionally, it highlights practical examples in e-commerce scenarios showcasing how these patterns facilitate efficient microservices communication and data management.
Pragmatic Event Driven Microservices
Pragmatic Event Driven MicroservicesAllard Buijze The document discusses event-driven microservices, emphasizing the importance of location transparency, command-query responsibility segregation, and event sourcing as architectural patterns. It highlights the complexities of microservices compared to monoliths and suggests that many successful microservice structures originate from well-managed monoliths. Additionally, it outlines the significance of effective messaging patterns and the role of Axon Framework in facilitating these systems through various APIs for event-driven interactions.
Building event-driven (Micro)Services with Apache Kafka
Building event-driven (Micro)Services with Apache KafkaGuido Schmutz The document discusses the architecture and benefits of event-driven microservices utilizing Apache Kafka. It highlights the principles of microservices, including autonomy, data management, and integration with legacy applications, while also detailing Kafka's role as a scalable message broker. The author concludes with insights on data analytics integration and references additional resources for further exploration.
Managing Data at Scale - Microservices and Events
Managing Data at Scale - Microservices and EventsRandy Shoup The document discusses the evolution and challenges of managing data within microservices architectures, particularly focusing on data migration, event-driven systems, and the problems related to shared data, joins, transactions, event duplication, and ordering. It highlights the necessity of single-system ownership for data, along with methods to handle data consistency and reliability as services scale. Several strategies, such as idempotent processing and event sourcing, are proposed to overcome common issues encountered when moving from monolithic to microservices architectures.
Three SOA Case Studies
Three SOA Case StudiesPaul Fremantle The document discusses three case studies of SOA implementations:
1. Integrating legacy systems at Concur for improved reporting using an iterative development approach with WSO2 tools.
2. Building a national SOA in Denmark (OIO SOI) for simplified e-business using a registry, transport protocols, and standard XML.
3. Integrating multiple IT management systems using an event-driven architecture with adapters, a message broker, and master data services.
Event-Driven Service-oriented Architecture (EDSOA)
Event-Driven Service-oriented Architecture (EDSOA)Attune Infocom Pvt Ltd The document outlines an event-driven service-oriented architecture (EDSOA) focusing on the challenges, composition, and deployment of web services in a dynamic business environment. It highlights the importance of event-driven modeling, the need for interoperability, and presents a structured approach for developing and executing services through a six-step process. The conclusion emphasizes the implementation of an event-driven lifecycle to address composition issues and improve resource coordination within business processes.
Event Driven Architecture
Event Driven ArchitectureChris Patterson Chris Patterson presented on event driven architecture. He introduced event driven architecture as a method where events flow between decoupled components and services. He defined events as representations of changes in state that are self-contained and identified. Events can be business events related to real world occurrences, lifecycle events for processes and states, or management events related to time and limits. The presentation discussed how events are published and consumed asynchronously between independent components using messaging systems like MassTransit. Commands were also introduced as messages telling components to perform actions.
Building event-driven Microservices with Kafka Ecosystem
Building event-driven Microservices with Kafka EcosystemGuido Schmutz This document outlines the principles and methodologies for building event-driven microservices using the Kafka ecosystem. It discusses key concepts such as microservices, asynchronous interactions, integration of legacy systems, Command Query Responsibility Segregation (CQRS), and event sourcing. It emphasizes the importance of service autonomy and how Kafka serves as an effective event broker and store for microservices architecture.
Event Driven Architecture at NDDNUG
Event Driven Architecture at NDDNUGChris Patterson The document discusses event driven architecture and how it compares to service oriented architecture. It defines key concepts in event driven architecture like events, commands, autonomous components, event producers and consumers. It also provides an example of how the .NET library MassTransit implements concepts like loose coupling and publish/subscribe using messages and events.
Ad
More from Natan Silnitsky (20)
Async-ronizing Success at Wix - Patterns for Seamless Microservices - Devoxx ...
Async-ronizing Success at Wix - Patterns for Seamless Microservices - Devoxx ...Natan Silnitsky In a world where speed, resilience, and fault tolerance define success, Wix leverages Kafka to power asynchronous programming across 4,000 microservices. This talk explores four key patterns that boost developer velocity while solving common challenges with scalable, efficient, and reliable solutions:
1. Integration Events: Shift from synchronous calls to pre-fetching to reduce query latency and improve user experience.
2. Task Queue: Offload non-critical tasks like notifications to streamline request flows.
3. Task Scheduler: Enable precise, fault-tolerant delayed or recurring workflows with robust scheduling.
4. Iterator for Long-running Jobs: Process extensive workloads via chunked execution, optimizing scalability and resilience.
For each pattern, we’ll discuss benefits, challenges, and how we mitigate drawbacks to create practical solutions
This session offers actionable insights for developers and architects tackling distributed systems, helping refine microservices and adopting Kafka-driven async excellence.
Integration Ignited Redefining Event-Driven Architecture at Wix - EventCentric
Integration Ignited Redefining Event-Driven Architecture at Wix - EventCentricNatan Silnitsky At Wix, we revolutionized our platform by making integration events the backbone of our 4,000-microservice ecosystem. By abandoning traditional domain events for standardized Protobuf events through Kafka, we created a universal language powering our entire architecture.
We'll share how our "single-aggregate services" approach—where every CUD operation triggers semantic events—transformed scalability and extensibility, driving efficient event choreography, data lake ingestion, and search indexing.
We'll address our challenges: balancing consistency with modularity, managing event overhead, and solving consumer lag issues. Learn how event-based data prefetches dramatically improved performance while preserving the decoupling that makes our platform infinitely extensible.
Key Takeaways:
- How integration events enabled unprecedented scale and extensibility
- Practical strategies for event-based data prefetching that supercharge performance
- Solutions to common event-driven architecture challenges
- When to break conventional architectural rules for specific contexts
Reinventing Microservices Efficiency and Innovation with Single-Runtime
Reinventing Microservices Efficiency and Innovation with Single-RuntimeNatan Silnitsky Managing thousands of microservices at scale often leads to unsustainable infrastructure costs, slow security updates, and complex inter-service communication. The Single-Runtime solution combines microservice flexibility with monolithic efficiency to address these challenges at scale.
By implementing a host/guest pattern using Kubernetes daemonsets and gRPC communication, this architecture achieves multi-tenancy while maintaining service isolation, reducing memory usage by 30%.
What you'll learn:
* Leveraging daemonsets for efficient multi-tenant infrastructure
* Implementing backward-compatible architectural transformation
* Maintaining polyglot capabilities in a shared runtime
* Accelerating security updates across thousands of services
Discover how the "develop like a microservice, run like a monolith" approach can help reduce costs, streamline operations, and foster innovation in large-scale distributed systems, drawing from practical implementation experiences at Wix.
Async Excellence Unlocking Scalability with Kafka - Devoxx Greece
Async Excellence Unlocking Scalability with Kafka - Devoxx GreeceNatan Silnitsky How do you scale 4,000 microservices while tackling latency, bottlenecks, and fault tolerance? At Wix, Kafka powers our event-driven architecture with practical patterns that enhance scalability and developer velocity.
This talk explores four key patterns for asynchronous programming:
1. Integration Events: Reduce latency by pre-fetching instead of synchronous calls.
2. Task Queue: Streamline workflows by offloading non-critical tasks.
3. Task Scheduler: Enable precise, scalable scheduling for delayed or recurring tasks.
4. Iterator: Handle long-running jobs in chunks for resilience and scalability.
Learn how to balance benefits and trade-offs, with actionable insights to optimize your own microservices architecture using these proven patterns.
Wix Single-Runtime - Conquering the multi-service challenge
Wix Single-Runtime - Conquering the multi-service challengeNatan Silnitsky The document discusses Wix's strategy for implementing a single-runtime architecture to address multi-service challenges, focusing on seamless backend integration and scalability. It outlines the goals of reducing costs, improving performance, and developing like microservices while operating as a monolith. Additionally, it emphasizes the importance of separation between infrastructure and business logic, and presents solutions such as using Kubernetes and SDL for efficient multi-tenant service management.
WeAreDevs - Supercharge Your Developer Journey with Tiny Atomic Habits
WeAreDevs - Supercharge Your Developer Journey with Tiny Atomic HabitsNatan Silnitsky The document discusses transforming a developer's journey through small, atomic habits, emphasizing the importance of creating effective systems over setting goals. It outlines strategies for building good habits, breaking bad ones, and implementing techniques such as temptation bundling, accountability partners, and environment design. The key takeaway is that consistent, tiny improvements can lead to significant long-term gains in performance and skills.
Effective Strategies for Wix's Scaling challenges - GeeCon
Effective Strategies for Wix's Scaling challenges - GeeConNatan Silnitsky The document discusses effective strategies for overcoming scaling challenges at Wix, focusing on the distinction between vertical and horizontal scaling. It emphasizes the advantages of horizontal scaling, such as workload distribution and improved performance, while outlining various routing and sharding strategies employed to manage data and service requests efficiently. Additionally, it highlights the importance of dynamic routing and data persistence solutions like DynamoDB to handle high-throughput applications.
Taming Distributed Systems: Key Insights from Wix's Large-Scale Experience - ...
Taming Distributed Systems: Key Insights from Wix's Large-Scale Experience - ...Natan Silnitsky Wix has transitioned its distributed system to entirely utilize CRUD-based microservices, moving away from a previous hybrid model combining CRUD and event sourcing. This shift was fueled by an emphasis on standardization, automated infrastructure, and a decoupled system architecture. Enhancements have been made through advanced tools to improve development speed, system resilience, and performance at scale.
Workflow Engines & Event Streaming Brokers - Can they work together? [Current...
Workflow Engines & Event Streaming Brokers - Can they work together? [Current...Natan Silnitsky The document discusses how workflow engines and event streaming brokers can work together. It describes some gaps in using only event streaming at scale for complex business flows and long-running tasks. It then provides an overview of how a workflow engine like Temporal could be integrated to address these gaps, including examples of implementing workflows and activities. Specific opportunities discussed for using Temporal at Wix include long-running processes, cron jobs, and internal microservice tasks.
Migrating to Multi Cluster Managed Kafka - ApacheKafkaIL
Migrating to Multi Cluster Managed Kafka - ApacheKafkaILNatan Silnitsky The document discusses the migration of Wix's Kafka infrastructure to a multi-cluster managed platform without downtime, focusing on the migration process, challenges encountered, and the benefits of improved performance and flexibility. It details Wix's Kafka architecture evolution, the strategies for migration, and best practices to ensure a seamless transition. The use of the Greyhound SDK and various replication tools is highlighted to facilitate this migration process.
Devoxx Ukraine - Kafka based Global Data Mesh
Devoxx Ukraine - Kafka based Global Data MeshNatan Silnitsky The document outlines Wix's implementation of a Kafka-based global data mesh, which supports over 2300 microservices and handles around 70 billion daily events across four regions. It highlights the challenges faced, such as scaling, cluster overloads, and maintaining an event-driven architecture, while introducing tools like Greyhound for improved consumer processes. The goal is to enable efficient data replication and processing across multiple data centers, ensuring that developers can seamlessly integrate within diverse tech stacks.
Devoxx UK - Migrating to Multi Cluster Managed Kafka
Devoxx UK - Migrating to Multi Cluster Managed KafkaNatan Silnitsky The document details Natan Silnitsky's experience and insights on migrating Wix's Kafka infrastructure to a multi-cluster managed platform. The migration aims to enhance cluster performance, scalability, and ease of management, driven by an increasing demand for message processing. Key strategies and best practices are discussed to ensure a seamless and production-safe transition with zero downtime.
Dev Days Europe - Kafka based Global Data Mesh at Wix
Dev Days Europe - Kafka based Global Data Mesh at WixNatan Silnitsky The document discusses the implementation of a Kafka-based global data mesh at Wix, highlighting its infrastructure, scalability, and event-driven architecture supporting a large number of developers and microservices. It outlines the challenges faced, such as traffic overload and the complexity of managing microservices across multiple data centers. Additionally, it emphasizes the use of Greyhound for service resilience and cross-data center replication strategies to enhance performance and reliability.
Kafka Summit London - Kafka based Global Data Mesh at Wix
Kafka Summit London - Kafka based Global Data Mesh at WixNatan Silnitsky The document discusses the implementation of a Kafka-based global data mesh at Wix, which supports a large number of unique visitors and websites. It outlines the architecture's scalability challenges with numerous developers and event-driven systems, specifically regarding data traffic and cluster management. The use of Greyhound as a messaging platform to handle Kafka operations and cross-data center replication is also highlighted.
Migrating to Multi Cluster Managed Kafka - Conf42 - CloudNative
Migrating to Multi Cluster Managed Kafka - Conf42 - CloudNative Natan Silnitsky The document discusses the migration process of a multi-cluster managed Kafka setup at Wix, highlighting the transition from a single self-hosted cluster to a more optimized multi-cluster environment. It provides details on the challenges faced, strategies implemented for seamless migration without downtime, and the benefits realized, such as improved performance and flexibility. The use of Greyhound, a high-level SDK for Apache Kafka, is emphasized throughout the migration process.
5 Takeaways from Migrating a Library to Scala 3 - Scala Love
5 Takeaways from Migrating a Library to Scala 3 - Scala LoveNatan Silnitsky The document details the migration process of a library to Scala 3, highlighting key steps such as making the build tool work with Scala 2.13 first, and then transitioning to Scala 3 using specific migration tools and plugins. It emphasizes the importance of using automated migration tools to save time and suggests a gradual approach to syntax changes. Additional resources and best practices for a smoother migration experience are also provided.
Migrating to Multi Cluster Managed Kafka - DevopStars 2022
Migrating to Multi Cluster Managed Kafka - DevopStars 2022Natan Silnitsky The document outlines the migration process of Wix's Kafka infrastructure from a single self-hosted cluster to a multi-cluster managed environment, emphasizing improvements such as performance, flexibility, and ease of expansion. It provides detailed insights into the challenges faced during migration, including traffic management and the automation processes implemented for a seamless transition. Best practices for ensuring a safe migration are discussed, highlighting the importance of monitoring, rollback strategies, and gradual topic migrations.
Open sourcing a successful internal project - Reversim 2021
Open sourcing a successful internal project - Reversim 2021Natan Silnitsky The document discusses the process of open sourcing a successful internal project called Greyhound at Wix, detailing its architecture, features, and the transition from private to public access. It outlines the steps taken to enable contributions from the developer community and the synchronization between private and public repositories. The content emphasizes the importance of collaboration and encourages developers worldwide to participate in the project.
How to successfully manage a ZIO fiber’s lifecycle - Functional Scala 2021
How to successfully manage a ZIO fiber’s lifecycle - Functional Scala 2021Natan Silnitsky The document discusses the management of ZIO fibers' lifecycle, covering key concepts such as the nature of fibers as lightweight concurrency mechanisms, handling unexpected failures, and the importance of fiber interruption. It provides examples and explains monitoring fiber states and their diagnostics in ZIO applications. The content also emphasizes the need for robust error handling and the integration of monitoring tools for effective management.
Advanced Caching Patterns used by 2000 microservices - Code Motion
Advanced Caching Patterns used by 2000 microservices - Code MotionNatan Silnitsky The document discusses advanced caching patterns for microservices, focusing on improving reliability and performance for services with high traffic and potential database failures. It outlines three main caching strategies: S3 backed static cache, DynamoDB with Change Data Capture (CDC) based cache, and HTTP reverse proxy cache, with specific use cases and implementation examples. The presentation emphasizes the importance of choosing the right caching strategy based on data stability, access patterns, and service architecture.
Ad
Recently uploaded (20)
Emvigo Capability Deck 2025: Accelerating Innovation Through Intelligent Soft...
Emvigo Capability Deck 2025: Accelerating Innovation Through Intelligent Soft...Emvigo Technologies Welcome to Emvigo’s Capability Deck for 2025 – a comprehensive overview of how we help businesses launch, scale, and sustain digital success through cutting-edge technology solutions.
With 13+ years of experience and a presence across the UK, UAE, and India, Emvigo is an ISO-certified software company trusted by leading global organizations including the NHS, Verra, London Business School, and George Washington University.
🔧 What We Do
We specialize in:
Rapid MVP development (go from idea to launch in just 4 weeks)
Custom software development
Gen AI applications and AI-as-a-Service (AIaaS)
Enterprise cloud architecture
DevOps, CI/CD, and infrastructure automation
QA and test automation
E-commerce platforms and performance optimization
Digital marketing and analytics integrations
🧠 AI at the Core
Our delivery model is infused with AI – from workflow optimization to proactive risk management. We leverage GenAI, NLP, and ML to make your software smarter, faster, and more secure.
📈 Impact in Numbers
500+ successful projects delivered
200+ web and mobile apps launched
42-month average client engagement
30+ active projects at any time
🌍 Industries We Serve
Fintech
Healthcare
Education (E-Learning)
Sustainability & Compliance
Real Estate
Energy
Customer Experience platforms
⚙️ Flexible Engagement Models
Whether you're looking for dedicated teams, fixed-cost projects, or time-and-materials models, we deliver with agility and transparency.
📢 Why Clients Choose Emvigo
✅ AI-accelerated delivery
✅ Strong focus on long-term partnerships
✅ Highly rated on Clutch and Google Reviews
✅ Proactive and adaptable to change
✅ Fully GDPR-compliant and security-conscious
🔗 Visit: emvigotech.com
📬 Contact: [email protected]
📞 Ready to scale your tech with confidence? Let’s build the future, together.
Building Geospatial Data Warehouse for GIS by GIS with FME
Building Geospatial Data Warehouse for GIS by GIS with FMESafe Software Data warehouses are often considered the backbone of data-driven decision-making. However, traditional implementations can struggle to meet the iterative and dynamic demands of GIS operations, particularly for Iterative Cross-Division Data Integration (ICDI) processes. At WVDOT, we faced this challenge head-on by designing a Geospatial Data Warehouse (GDW) tailored to the needs of GIS. In this talk, we’ll share how WVDOT developed a metadata-driven, SESSI-based (Simplicity, Expandability, Spatiotemporality, Scalability, Inclusivity) GDW that transforms how we manage and leverage spatial data. Key highlights include: - Simplifying data management with a lean schema structure. - Supporting ad hoc source data variations using JSON for flexibility. - Scaling for performance with RDBMS partitioning and materialized views. - Empowering users with FME Flow-based self-service metadata tools.We’ll showcase real-world use cases, such as pavement condition data and LRS-based reporting, and discuss how this approach is elevating GIS as an integrative framework across divisions. Attendees will walk away with actionable insights on designing GIS-centric data systems that combine the best of GIS and data warehouse methodologies.
Key Challenges in Troubleshooting Customer On-Premise Applications
Key Challenges in Troubleshooting Customer On-Premise ApplicationsTier1 app When applications are deployed in customer-managed environments, resolving performance issues becomes a hidden battle. Limited access to logs, delayed responses, and vague problem descriptions make root cause analysis incredibly challenging.
In this presentation, we walk through:
The six most common hurdles faced in on-prem troubleshooting
A practical 360° artifact collection strategy using the open-source yc-360 script
Real-world case studies covering transaction timeouts, CPU spikes, and intermittent HTTP 502 errors
Benefits of structured data capture in reducing investigation time and improving communication with customers
✅ Whether you're supporting enterprise clients or building tools for distributed environments, this deck offers a practical roadmap to make on-prem issue resolution faster and less frustrating.
Heat Treatment Process Automation in India
Heat Treatment Process Automation in IndiaReckers Mechatronics Automate your heat treatment processes for superior precision, consistency, and cost savings. Explore solutions for furnaces, quench systems. Heat treatment is a critical manufacturing process that alters the microstructure and properties of materials, typically metals, to achieve desired characteristics such as hardness, strength, ductility, and wear resistance.
On-Device AI: Is It Time to Go All-In, or Do We Still Need the Cloud?
On-Device AI: Is It Time to Go All-In, or Do We Still Need the Cloud?Hassan Abid As mobile hardware becomes more powerful, the promise of running advanced AI directly on-device is closer than ever. With Google’s latest on-device model Gemini Nano, accessible through the new ML Kit GenAI APIs and AI Edge SDK, alongside the open-source Gemma-3n models, developers can now integrate lightweight, multimodal intelligence that works even without an internet connection. But does this mean we no longer need cloud-based AI? This session explores the practical trade-offs between on-device and cloud AI for mobile apps.
Canva Pro Crack Free Download 2025-FREE LATEST
Canva Pro Crack Free Download 2025-FREE LATESTgrete1122g 🌍📱👉COPY & PASTE LINK >> https://click4pc.com/after-verification-click-go-to-download-page/
Canva Pro PC Crack is a practical design app to create beautiful montages and compositions with a lot of resources on the platform.
Reimagining Software Development and DevOps with Agentic AI
Reimagining Software Development and DevOps with Agentic AIMaxim Salnikov Key announcements about Developer Productivity from Microsoft Build 2025
Why Every Growing Business Needs a Staff Augmentation Company IN USA.pdf
Why Every Growing Business Needs a Staff Augmentation Company IN USA.pdfmary rojas U.S. staff augmentation companies excel at providing IT professionals with expertise in development, cybersecurity, AI, and more. Whether you need to fill a short-term gap or enhance your team’s capabilities long-term, these firms deliver pre-vetted talent tailored to your tech stack and industry. With an understanding of both global technologies and local compliance, U.S.-based IT staff augmentation bridges the gap between talent shortage and project demand efficiently.
Azure AI Foundry: The AI app and agent factory
Azure AI Foundry: The AI app and agent factoryMaxim Salnikov Discover how Azure AI Foundry is transforming the way organizations innovate and operate. This session explores the pivotal role of AI in reshaping business processes, enhancing employee experiences, and redefining customer engagement. Attendees will gain insights into the strategic value of AI investments, including the measurable returns and the growing momentum behind generative AI experimentation.
The talk introduces the emerging paradigm of agentic AI - intelligent agents that are revolutionizing how we build, manage, and interact with software. Through real-world examples, the session demonstrates how Azure AI Foundry empowers teams to design, customize, and scale AI applications and agents, unlocking new levels of efficiency and creativity across industries.
Enable Your Cloud Journey With Microsoft Trusted Partner | IFI Tech
Enable Your Cloud Journey With Microsoft Trusted Partner | IFI TechIFI Techsolutions Start your cloud journey with IFI Tech—Microsoft’s trusted partner delivering secure, scalable Azure solutions tailored for your business.
Digital Transformation: Automating the Placement of Medical Interns
Digital Transformation: Automating the Placement of Medical InternsSafe Software Discover how the Health Service Executive (HSE) in Ireland has leveraged FME to implement an automated solution for its “Order of Merit” process, which assigns medical interns to their preferred placements based on applications and academic performance. This presentation will showcase how FME validates applicant data, including placement preferences and academic results, ensuring both accuracy and eligibility. It will also explore how FME automates the matching process, efficiently assigning placements to interns and distributing offer letters. Beyond this, FME actively monitors responses and dynamically reallocates placements in line with the order of merit when offers are accepted or declined. The solution also features a self-service portal (FME Flow Gallery App), enabling administrators to manage the entire process seamlessly, make adjustments, generate reports, and maintain audit logs. Additionally, the system upholds strict data security and governance, utilising FME to encrypt data both at rest and in transit.
CodeCleaner: Mitigating Data Contamination for LLM Benchmarking
CodeCleaner: Mitigating Data Contamination for LLM Benchmarkingarabelatso The pdf version of "CodeCleaner: Mitigating Data Contamination for LLM Benchmarking" presented in Internetware 2025.
ERP Systems in the UAE: Driving Business Transformation with Smart Solutions
ERP Systems in the UAE: Driving Business Transformation with Smart Solutionsdheeodoo ERP solutions are driving innovative change for businesses across the UAE through improved efficiency, reduced operational costs, and provide real-time visibility of operational data. By offering native Arabic language support, VAT compliance, and some level of cloud readiness, ERP solutions also supports and are consistent with the initiative for Smart Dubai 2030. Odoo is an example of a flexible & scalable solution. If you're looking for expert support with implementation contact Banibro. www.banibro.com
MOVIE RECOMMENDATION SYSTEM, UDUMULA GOPI REDDY, Y24MC13085.pptx
MOVIE RECOMMENDATION SYSTEM, UDUMULA GOPI REDDY, Y24MC13085.pptxMaharshi Mallela Movie recommendation system is a software application or algorithm designed to suggest movies to users based on their preferences, viewing history, or other relevant factors. The primary goal of such a system is to enhance user experience by providing personalized and relevant movie suggestions.
Advance Doctor Appointment Booking App With Online Payment
Advance Doctor Appointment Booking App With Online PaymentAxisTechnolabs https://www.slideshare.net/slideshow/advance-doctor-appointment-booking-app-with-online-payment/280654375
Automated Migration of ESRI Geodatabases Using XML Control Files and FME
Automated Migration of ESRI Geodatabases Using XML Control Files and FMESafe Software Efficient data migration is a critical challenge in geospatial data management, especially when working with complex data structures. This presentation explores an automated approach to migrating ESRI Geodatabases using FME and XML-based control files. A key advantage of this method is its adaptability: changes to the data model are seamlessly incorporated into the migration process without requiring modifications to the underlying FME workflow. By separating data model definitions from migration logic, this approach ensures flexibility, reduces maintenance effort, and enhances scalability.
Foundations of Marketo Engage - Programs, Campaigns & Beyond - June 2025
Foundations of Marketo Engage - Programs, Campaigns & Beyond - June 2025BradBedford3 Join us for an exciting introductory session on, Foundations of Marketo Engage: Programs, Campaigns & Beyond. Ideal for new and early-stage users looking to build confidence and capability in Marketo Engage.
Our speakers for this session will be:
AJ Navarro
Marketing Operations Manager - Sprout Social
Bobby Coppola
Marketing Manager - Blue Yonder
This event will guide you through the essential steps to build strong, scalable Programs, Channels, Tags, Smart Campaigns, and Reporting Basics in Marketo Engage.
Attendees will gain practical knowledge on how to structure and launch marketing initiatives, leverage templates for efficiency, and implement best practices for campaign execution and measurement. You'll leave with actionable insights you can immediately apply to your own Marketo instance to improve organization, automation, and reporting. Marketo Engage.
Learn how to create impactful programs and understand the best practices for seamless campaign management and effective reporting.
Don’t miss out on this opportunity to gain hands-on guidance from experienced practitioners and to connect with peers who are also new to the platform. Secure your spot today and start building your path to becoming a Marketo pro!
Please feel free to invite colleagues who you think would also benefit from this session.
CodeCleaner: Mitigating Data Contamination for LLM Benchmarking
CodeCleaner: Mitigating Data Contamination for LLM Benchmarkingarabelatso The pdf-version of "CodeCleaner: Mitigating Data Contamination for LLM Benchmarking" presented in Internetware 2025.
Decipher SEO Solutions for your startup needs.
Decipher SEO Solutions for your startup needs.mathai2 A solution deck that gives you an idea of how you can use Decipher SEO to target keywords, build authority and generate high ranking content.
With features like images to product you can create a E-commerce pipeline that is optimized to help your store rank.
With integrations with shopify, woocommerce and wordpress theres a seamless way get your content to your website or storefront.
View more at decipherseo.com
A Guide to Telemedicine Software Development.pdf
A Guide to Telemedicine Software Development.pdfOlivero Bozzelli Learn how telemedicine software is built from the ground up—starting with idea validation, followed by tech selection, feature integration, and deployment.
Know more about this: https://www.yesitlabs.com/a-guide-to-telemedicine-software-development/
BuildStuff - Lessons Learned from 2000 Event Driven Microservices
- 1. Lessons Learned from 2000 event-driven microservices natansil.com twitter@NSilnitsky linkedin/natansilnitsky github.com/natansil Natan Silnitsky Backend Infra TL, Wix.com November 2022
- 2. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky
- 3. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Unique visitors use Wix platform every month ~1B * scale, recovery, issues
- 4. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Unique visitors use Wix platform every month ~1B Daily HTTP Transactions ~500B Kafka messages a day ~70B * scale, recovery, issues
- 5. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Unique visitors use Wix platform every month ~1B Daily HTTP Transactions ~500B Kafka messages a day ~70B GAs every day > 600 Microservices in production 2300 * scale, recovery, issues
- 6. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Challenges of event-driven architecture, that we’ve bumped into 1 Producing message failures Processing out-of-order & duplicates 2 4 Troubleshooting production 3 Sending large payloads * success, tools, faster
- 7. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky How Event-driven Architecture Works
- 8. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Service-to-Service Communication Cart Service User Service Inventory Service Catalog Service
- 9. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Request-Reply Communication HTTP RPC HTTP RPC HTTP RPC Cart Service User Service Inventory Service Catalog Service * issue scale
- 10. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky slow Cart Service * slow, bottleneck, cache HTTP RPC HTTP RPC HTTP RPC
- 11. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky unreliable Cart Service * unreliable, cascade, retr HTTP RPC HTTP RPC HTTP RPC
- 12. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Event-driven Communication Producer Broker Product Updated Topic Event * improve, broker, scale Catalog Service Kafka
- 13. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Broker more robust * DB, decoupling, no impact Cart Service Producer Consumer Kafka Catalog Service Product Updated Topic
- 14. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Broker Event processing is guaranteed Producer Consumer Kafka Catalog Service Cart Service Product Updated Topic
- 15. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky The following is based on a true story *Dates and products were changed for clarity :) * ecom simple linear
- 16. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky 2016 Wix starts using event-driven We can work event-driven!!
- 17. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky It all began when Ecom experienced data issues Data does NOT reflect actual catalog Risk: show wrong prices in cart Cart DB
- 18. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky 2. Produce “Product Updated” Event Broker Cart Service 4. Show updated prices in cart 3. Update Product Price Catalog Service 1. Update status After investigating Cart DB
- 19. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Challenge #1 Producing message failure Kafka
- 20. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Broker Cart Service Catalog Service Make DB Update & Event Producing Atomic
- 21. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Produce event to S3 Broker Catalog Service Resilient Producer Catch Unsent Events
- 22. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Produce event to S3 Broker Produce to Kafka Healer Service Catalog Service Poll Resilient Producer Fallback to S3 and Heal
- 23. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Kafka Broker Service A Service B Greyhound Producer Kafka Producer Greyhound Consumer Kafka Consumer Wrap Kafka with Greyhound* * Open source: https://github.com/wix/greyhound
- 24. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky ➔ Resilient Producer ➔ Parallel Consumption ➔ Batch Consumer ➔ Consumer Retry Strategies ➔ Context Propagation ➔ Metrics reporting Developer Self-Service: Wrap Kafka with Greyhound* * Open source: https://github.com/wix/greyhound
- 25. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky 2016 Wix starts using event-driven 2018 Greyhound Resilient producer & Consumer retries
- 26. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Produce event to S3 Broker Produce to Kafka Healer Service Catalog Service Poll Resilient Producer Fallback to S3 and Heal
- 27. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Broker Catalog Service Healer Service Remove Discount Introduce Discount Then ‘out-of-order’ happened Cart Service
- 28. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Challenge #2 Out-of-order & duplicates processing Kafka
- 29. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Catalog Service Broker Healer Service Introduce Discount Mitigating out-of-order with revision ID # 10 # 9 Cart Service
- 30. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Catalog Service Broker Healer Service Remove Discount Introduce Discount Mitigating out-of-order with revision ID # 11 # 10 # 9 Cart Service * item itself
- 31. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Scan the binlog. For each entry produce a ‘status update’ event Cart Service Broker Catalog Service Mitigating out-of-order with Debezium connector
- 32. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky More Ecom data issues Data does NOT reflect actual inventory Risk: lose potential customers Inventory DB
- 33. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Item 2 Item 1 Broker Payments Service Investigation leads to duplicate processing Payment for: Inventory Service Retry Item 2 5 → 3 Item 1 9 → 7 * not idempotent
- 34. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Item 2 5 → 4 Item 1 9 → 8 Item 2 Item 1 Payment for: Broker txnId - a7g45 Mitigating duplicates with Transaction ID Payments Service Inventory Service txnId - a7g45 txnId - a7g45
- 35. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky 2016 Wix starts using event-driven 2018 Greyhound Resilient producer & Consumer retries 2019 Revisions & Transaction IDs
- 36. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Broker Product Catalog Service Product Update event Cart Service “Dude, I can’t produce large payloads” ... "description": "An apple mobile which is nothing like apple", ...
- 37. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky * 1MB Challenge #3 Failure to send large payloads Broker ... "description": "An apple mobile which is nothing like apple", ...
- 38. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Large Payloads Remedy I Compression → Try several compression types (lz4, snappy, etc.) → Compression on Kafka level is usually better than application level, as payloads can be compressed in batches
- 39. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Large Payloads Remedy II Chunking Broker 1. Split to chunks & produce 2. Consume & reassemble Product Catalog Service Cart Service
- 40. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Large Payloads Remedy III Reference to Object Store 2. Produce with S3 URL 3. Consume & download from S3 1. Upload to S3 Product Catalog Service Cart Service Broker
- 41. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky 2016 Wix starts using event-driven 2018 Greyhound Resilient producer & Consumer retries 2019 We use IDs for ooo & duplicates 2020 Added compression by default
- 42. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky * bottlenecks Challenge #4 It’s hard for developers to debug and maintain event-driven microservices at scale in production
- 43. Our team
- 44. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Stream events with various filters
- 45. How do I investigate this lag? Our team
- 46. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Investigate consumer lag per partition
- 47. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky View a “stuck” event in some partition
- 48. How come this side-effect didn’t happen? Our team
- 49. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Orders Service Propagate the Context Broker Payments Topic Orders Topic Inventory Topic requestId userId Event Header 1. Greyhound produce * monitoring infra
- 50. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky 2. Greyhound consume Propagate the Context Payments Service Broker Payments Topic Orders Topic Inventory Topic 3. produce
- 51. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky 4. Greyhound consume Propagate the Context Inventory Service Broker Payments Topic Orders Topic Inventory Topic
- 52. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky So developers can track events’ route
- 53. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky View event details
- 54. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky 2016 Wix starts using event-driven 2018 We open source Greyhound 2019 We use IDs for ooo & duplicates 2020 Added compression by default 2021-22 Tools in Production
- 55. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Wix developers have embraced event-driven architecture.
- 56. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Meeting these challenges made our microservices more decoupled, resilient and scalable, while keeping complexity low and data consistent.
- 57. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky The Blog Post https://medium.com/wix-engineerin g/event-driven-architecture-5-pitfalls-t o-avoid-b3ebf885bdb1
- 58. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky How to migrate 2000 microservices to Multi Cluster Managed Kafka with 0 Downtime The Next Step https://www.youtube.com/watch?v= XKbG8a-9NRE
- 59. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Greyhound github.com/wix/greyhound
- 60. Lessons Learned from 2000 Event-driven Microservices @NSilnitsky Tomorrow Create Tiny Habits to Become a Better Developer
- 61. Thank You! natansil.com twitter@NSilnitsky linkedin/natansilnitsky github.com/natansil 👉 slideshare.net/NatanSilnitsky Any questions?