Event driven without microservices
0 likes558 views
Event-driven is about having modules which are communicating via messages (events and commands). There's nothing that forces you to go microservices if you want to go event-driven. In fact, it's actually not needed in most cases. Learn more at http://railsarchitects.com
1 of 14
Download to read offline
Recommended
Blockchain
BlockchainMehul jadav A blockchain is a growing list of records, called blocks, which are linked using cryptography. Each block contains a cryptographic hash of the previous block, a timestamp, and transaction data. By design, a blockchain is resistant to modification of the data.
Understanding Blockchain and why it's so popular? 
Understanding Blockchain and why it's so popular? Harsh Kumar Understanding Blockchain and why it's so popular? Why should you have the knowledge about the blockchain? How can it be revolutionary? To know more about blockchain and learn the Blockchain Technology you can visit: http://www.blazingminds.in/course-detail-blockchain.html.
Ratpack and Grails 3
Ratpack and Grails 3Lari Hotari One of the goals of Grails 3 is to reach out of the servlet container. Grails 3 has a concept of application profiles for choosing a certain set of core plugins to use. In this talk Lari will present how Ratpack fits in Grails 3. He will also talk about how Grails 3 supports micro service architectures.
Kenzan: Architecting for Microservices
Kenzan: Architecting for MicroservicesDarren Bathgate Slides from the October 2016 meetup presentation of the Massachusetts Microservices Meetup group.
Kenzan
Twitter: @kenzanmedia
Linkedin: www.linkedin.com/company/kenzan-media
Blog: techblog.kenzan.com
Facebook: www.facebook.com/kenzanmedia/
CoreData Best Practices (2021)
CoreData Best Practices (2021)deeje cooley Here are some notes on how to structure your iOS apps to use CoreData (and CloudKit), based on years of building and shipping apps to the App Store.
Amazon web services (aws) main developer services
Amazon web services (aws) main developer servicesAnderson Carvalho Developing in the cloud should not be different than on-premise development and AWS services aim to facilitate developers and reduce costs. The main AWS developer services that a developer should know include IAM for managing users and credentials, CloudWatch for monitoring and alarms, EC2 for renting compute resources, VPC for network management, S3 for object storage, DynamoDB for NoSQL database, RDS for relational databases, Elastic Beanstalk for deploying applications, and CloudFront for low-latency content delivery. Additional services are CloudFormation for provisioning via templates and Elasticache for caching.
Microservices
MicroservicesAnderson Carvalho Microservices involve breaking down monolithic applications into smaller, independent services that communicate through defined interfaces. This allows for faster development and deployment cycles, improved scalability, and easier innovation. When adopting a microservices architecture, it is important to understand functional and non-functional requirements to design the overall and micro architectures, company culture to organize teams, and choose technologies like containers, messaging systems, databases to empower the services.
NATS vs HTTP
NATS vs HTTPApcera Presentation from a talk given by Diogo Monteiro (@diogogmt) at a recent NATS Meetup in Toronto. The talk covered why NATS is a simple, fast method for microservices communication, and provides some latency benchmarks from Diogo's design of a solution using NATS.
You can learn more about NATS at http://www.nats.io
Get Off My Cloud - Launching your Startup on The Cloud
Get Off My Cloud - Launching your Startup on The CloudJoe Drumgoole Cloud computing provides infrastructure for startups to launch applications and services quickly and cost effectively by leveraging third party hosting providers and platforms. However, there are also challenges to consider regarding data security, programmer expertise, service reliability, and end user experience. Based on their experience, the author recommends using cloud computing strategically as part of a hybrid infrastructure model to balance cost, control and risk.
Osdc - Meteor Intorduction
Osdc - Meteor IntorductionAyush Narula Meteor is a JavaScript framework for building real-time web applications. It uses a Node.js container on the server and allows developers to write both the client and server code in JavaScript. With Meteor, the same database API can be used from both the client and server, and data is sent over the wire instead of HTML. It compensates for latency by using prefetching and simulation on the client to make interactions feel instantaneous. Common packages used with Meteor include Handlebars for templates and MongoDB for the database, but additional packages can also be installed.
Saga transactions msa_ architecture
Saga transactions msa_ architectureMauro Vocale This document discusses microservices and distributed transactions. It begins by describing microservices and their advantages and disadvantages. It then discusses how traditional distributed transactions using two-phase commit do not work well for microservices due to the distributed and independent nature of microservices. The document introduces the Saga pattern as an alternative approach for distributed transactions across microservices that provides eventual consistency. It describes key aspects of the Saga pattern including compensating actions, lack of isolation, and implementing either choreography or orchestration.
Cloud Native Patterns Using AWS
Cloud Native Patterns Using AWSAnderson Carvalho This document discusses cloud native patterns using AWS. It defines cloud native as architectures that take advantage of cloud capabilities to build scalable applications in dynamic environments. The document outlines characteristics of cloud native applications like being disposable, isolated, globally scalable, and developed by self-sufficient teams. It then describes foundation patterns like having one database per component, using event streaming, event sourcing, data lakes, and trilateral APIs. It also covers boundary patterns such as API gateways, CQRS, backend for frontends, and external service gateways. Finally, it discusses control patterns involving event collaboration and orchestration and provides examples of relevant AWS building blocks.
Advance Features of Hibernate
Advance Features of HibernateMindfire Solutions This document provides an overview of advanced Hibernate concepts including:
1) Mapping types such as many-to-one, one-to-many, and one-to-one relationships.
2) Batch processing and data filtering.
3) Interceptors, events, triggers and stored procedures.
4) Second level caching and query caching.
5) Reverse engineering to generate object relational mappings from an existing database.
Magical monolith
Magical monolithVictor Perepelitsky To tackle challenges such as significant operations overhead, duplication of effort, testability that microservices usually faces, and to achieve the benefits such as code decoupling, easy to scale-out that microservices brings in, In-process microservices is proposed in this fresh presentation by Victor Perepelitsky.
Pragmatic Event Driven Microservices
Pragmatic Event Driven MicroservicesAllard Buijze Allard Buijze outlines an evolutionary approach to microservices, which allows teams to focus on functionality first while keeping the ability to scale out and distribute components when necessary. Allard covers patterns based on domain-driven design (DDD) and command query responsibility segregation (CQRS) that help ensure the correct decoupling stays in place during an application’s lifecycle and explores the value of using events in such an architecture, particularly when used in combination with other types of messages.
Managing Data at Scale - Microservices and Events
Managing Data at Scale - Microservices and EventsRandy Shoup An ambitious attempt at BuildStuff España 2018 to cover, in 50 minutes:
* Migrating to Microservices
* Challenges of Data in Microservices (including shared data, joins, and transactions)
* Challenges of Event-Driven Systems (including event duplication and event ordering)
Event Driven Microservices architecture
Event Driven Microservices architectureNikhilBarthwal4 Event-Driven Microservices architecture has gained a lot of attention recently. The trend in the industry is to move away from Monolithic applications to Microservices to innovate faster. While Microservices have their benefits, implementing them is hard. This talk focuses on the challenges faced and how to solve them.
It covers topics like using Domain Driven Design to break functionality into small parts. Various communication patterns among Microservices are also discussed.
One major drawback is the problem of distributed data management, as each Microservice has its own database. Event-Driven Architecture enables a way to make microservices work together and the talks show how to use architectural patterns like Event Sourcing & CQRS to implement them.
Another implementation challenge is to manage transactions that update entities owned by multiple services in an eventually consistent fashion. This challenge is solved using sagas, which can be thought of as Long running transactions that use compensating actions to handle failures.
The objective of the talk is to show how to implement highly distributed Event Driven Microservices architecture that are scalable and easy to maintain.
Deconstructing Monoliths with Domain Driven Design
Deconstructing Monoliths with Domain Driven DesignVMware Tanzu SpringOne Platform 2017
David Turanski, Pivotal; Rohit Sood, Liberty Mutual; Rohit Kelapure, Pivotal; Justin Stone, Liberty Mutual
This session will detail a synthesis of techniques used to destroy a monolithic BPM and orchestration based application at Liberty Mutual into an event driven microservices based architecture implemented with Event Sourcing and CQRS. The transformation and developer productivity affected by the monolith decomposition and alignment of business capabilities to bounded contexts teaches lessons for all enterprises looking to undergo similar changes.
Whitepaper : Event Driven Micro Services
Whitepaper : Event Driven Micro ServicesNewt Global Consulting LLC There is not much of complexity in terms of processes and communications between services in a Monolithic Application that deal with a single relational database. Most of the relational database use ACID transaction to process each request from the client.
Microservices + Events + Docker = A Perfect Trio (dockercon)
Microservices + Events + Docker = A Perfect Trio (dockercon)Chris Richardson Microservices are an essential enabler of agility but developing and deploying them is a challenge. In order for microservices to be loosely coupled,each service must have its own datastore. This makes it difficult to maintain data consistency across services.
Deploying microservices is also a complex problem since an application typically consists of 10s or 100s of services, written in a variety of languages and frameworks. In this presentation, you will learn how to solve these problems by using an event-driven architecture to maintain data consistency and by using Docker to simplify deployment.
Events and microservices
Events and microservicesSaul Caganoff The document discusses using events and asynchronous messaging to coordinate activities across microservices. It describes how events can be used for loose coupling between services, avoiding the need for centralized orchestration. Events are proposed as a way to handle data synchronization and business processes across bounded contexts. Various options for transporting events such as syndication, web hooks, and message queues are also examined.
An eventful tour from enterprise integration to serverless and functions
An eventful tour from enterprise integration to serverless and functionsChristian Posta In this talk, Marius (@mariusbogoevici) and I (@christianposta) discuss the value of event-driven architectures (both business and technical merits) and how the landscape of integration, streaming, and messaging and now functions/lambdas have evolved to implement EDA while balancing agility, utilization, and simplicity.
Microservices + Events + Docker = A Perfect Trio by Docker Captain Chris Rich...
Microservices + Events + Docker = A Perfect Trio by Docker Captain Chris Rich...Docker, Inc. The document discusses how microservices, events, and Docker form a perfect trio for developing and deploying applications. It covers how microservices can help accelerate development but also introduce complexity that events and Docker can help address. Events are proposed to maintain data consistency between microservices rather than distributed transactions. Docker is presented as a way to containerize microservices for improved isolation, manageability and efficient deployment and scaling. The overall presentation argues this combination of techniques can help build large, complex applications.
From Rails legacy to DDD - Pivorak, Lviv
From Rails legacy to DDD - Pivorak, LvivAndrzej Krzywda Rails is optimised for the first weeks of development. At the later phases it's no longer the speed of adding new views and data that matters. It's often more about the different (and changing!) ways of using the data. The business logic gets more complicated.
DDD has answers to those problems. Detecting the bounded contexts is the crucial skill. Choose which parts of the app leave as CRUD and which could go into more of the tactical DDD.
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.
Beyond Microservices
Beyond MicroservicesEberhard Wolff This presentation shows the properties, advantages and challenges of microservices. It then discusses alternative architectures beyond microservices.
OSDC 2018 | From Monolith to Microservices by Paul Puschmann_
OSDC 2018 | From Monolith to Microservices by Paul Puschmann_NETWAYS Scaling up from two developer teams supporting a monolith to more than 20 developer teams powering a micro-service landscape is not only a matter of technical excellence but also the matter of culture and collaboration. This talk will show the positive aspects of our evolution as well as the things we learned to improve on.
Events on the outside, on the inside and at the core (jaxlondon)
Events on the outside, on the inside and at the core (jaxlondon)Chris Richardson This presentation looks at the importance of events and the role that they play in software applications. We describe how events are a key application integration mechanism and how they are used by applications to communicate with the outside world. You will learn how the microservices inside a system can use events to maintain data consistency. We discuss how easy it is to implement both these mechanisms by developing your core business logic using an event-centric approach.
Events on the outside, on the inside and at the core - Chris Richardson
Events on the outside, on the inside and at the core - Chris RichardsonJAXLondon_Conference The document discusses event sourcing and how it enables an event-driven enterprise architecture. It describes how event sourcing works by having applications persist all state changes as a sequence of events rather than current state. These events can then be used to rebuild state. When requests are received, past events are replayed to determine the current state. New events generated from requests are published for other applications. This allows for distributed transaction processing without two-phase commit and enables eventual consistency across services.
The Road To Event-Driven Architecture
The Road To Event-Driven ArchitectureSheenBrisals - The document discusses the transition of LEGO.com from a monolithic architecture to an event-driven architecture (EDA) on AWS.
- Early issues with the monolith like outages during Black Friday motivated a move to microservices and serverless. An initial serverless implementation using AWS Lambda and SQS proved the value of an event-driven approach.
- The adoption of EDA accelerated over two phases, first using services like Kinesis and Lambda, then adding Amazon EventBridge for improved event routing between services.
- Microservices were developed using a "set pieces" approach, where independent domains are developed separately but coordinated through events.
- Overall the document outlines the challenges of the monolith
More Related Content
What's hot (6)
Get Off My Cloud - Launching your Startup on The Cloud
Get Off My Cloud - Launching your Startup on The CloudJoe Drumgoole Cloud computing provides infrastructure for startups to launch applications and services quickly and cost effectively by leveraging third party hosting providers and platforms. However, there are also challenges to consider regarding data security, programmer expertise, service reliability, and end user experience. Based on their experience, the author recommends using cloud computing strategically as part of a hybrid infrastructure model to balance cost, control and risk.
Osdc - Meteor Intorduction
Osdc - Meteor IntorductionAyush Narula Meteor is a JavaScript framework for building real-time web applications. It uses a Node.js container on the server and allows developers to write both the client and server code in JavaScript. With Meteor, the same database API can be used from both the client and server, and data is sent over the wire instead of HTML. It compensates for latency by using prefetching and simulation on the client to make interactions feel instantaneous. Common packages used with Meteor include Handlebars for templates and MongoDB for the database, but additional packages can also be installed.
Saga transactions msa_ architecture
Saga transactions msa_ architectureMauro Vocale This document discusses microservices and distributed transactions. It begins by describing microservices and their advantages and disadvantages. It then discusses how traditional distributed transactions using two-phase commit do not work well for microservices due to the distributed and independent nature of microservices. The document introduces the Saga pattern as an alternative approach for distributed transactions across microservices that provides eventual consistency. It describes key aspects of the Saga pattern including compensating actions, lack of isolation, and implementing either choreography or orchestration.
Cloud Native Patterns Using AWS
Cloud Native Patterns Using AWSAnderson Carvalho This document discusses cloud native patterns using AWS. It defines cloud native as architectures that take advantage of cloud capabilities to build scalable applications in dynamic environments. The document outlines characteristics of cloud native applications like being disposable, isolated, globally scalable, and developed by self-sufficient teams. It then describes foundation patterns like having one database per component, using event streaming, event sourcing, data lakes, and trilateral APIs. It also covers boundary patterns such as API gateways, CQRS, backend for frontends, and external service gateways. Finally, it discusses control patterns involving event collaboration and orchestration and provides examples of relevant AWS building blocks.
Advance Features of Hibernate
Advance Features of HibernateMindfire Solutions This document provides an overview of advanced Hibernate concepts including:
1) Mapping types such as many-to-one, one-to-many, and one-to-one relationships.
2) Batch processing and data filtering.
3) Interceptors, events, triggers and stored procedures.
4) Second level caching and query caching.
5) Reverse engineering to generate object relational mappings from an existing database.
Magical monolith
Magical monolithVictor Perepelitsky To tackle challenges such as significant operations overhead, duplication of effort, testability that microservices usually faces, and to achieve the benefits such as code decoupling, easy to scale-out that microservices brings in, In-process microservices is proposed in this fresh presentation by Victor Perepelitsky.
Similar to Event driven without microservices (20)
Pragmatic Event Driven Microservices
Pragmatic Event Driven MicroservicesAllard Buijze Allard Buijze outlines an evolutionary approach to microservices, which allows teams to focus on functionality first while keeping the ability to scale out and distribute components when necessary. Allard covers patterns based on domain-driven design (DDD) and command query responsibility segregation (CQRS) that help ensure the correct decoupling stays in place during an application’s lifecycle and explores the value of using events in such an architecture, particularly when used in combination with other types of messages.
Managing Data at Scale - Microservices and Events
Managing Data at Scale - Microservices and EventsRandy Shoup An ambitious attempt at BuildStuff España 2018 to cover, in 50 minutes:
* Migrating to Microservices
* Challenges of Data in Microservices (including shared data, joins, and transactions)
* Challenges of Event-Driven Systems (including event duplication and event ordering)
Event Driven Microservices architecture
Event Driven Microservices architectureNikhilBarthwal4 Event-Driven Microservices architecture has gained a lot of attention recently. The trend in the industry is to move away from Monolithic applications to Microservices to innovate faster. While Microservices have their benefits, implementing them is hard. This talk focuses on the challenges faced and how to solve them.
It covers topics like using Domain Driven Design to break functionality into small parts. Various communication patterns among Microservices are also discussed.
One major drawback is the problem of distributed data management, as each Microservice has its own database. Event-Driven Architecture enables a way to make microservices work together and the talks show how to use architectural patterns like Event Sourcing & CQRS to implement them.
Another implementation challenge is to manage transactions that update entities owned by multiple services in an eventually consistent fashion. This challenge is solved using sagas, which can be thought of as Long running transactions that use compensating actions to handle failures.
The objective of the talk is to show how to implement highly distributed Event Driven Microservices architecture that are scalable and easy to maintain.
Deconstructing Monoliths with Domain Driven Design
Deconstructing Monoliths with Domain Driven DesignVMware Tanzu SpringOne Platform 2017
David Turanski, Pivotal; Rohit Sood, Liberty Mutual; Rohit Kelapure, Pivotal; Justin Stone, Liberty Mutual
This session will detail a synthesis of techniques used to destroy a monolithic BPM and orchestration based application at Liberty Mutual into an event driven microservices based architecture implemented with Event Sourcing and CQRS. The transformation and developer productivity affected by the monolith decomposition and alignment of business capabilities to bounded contexts teaches lessons for all enterprises looking to undergo similar changes.
Whitepaper : Event Driven Micro Services
Whitepaper : Event Driven Micro ServicesNewt Global Consulting LLC There is not much of complexity in terms of processes and communications between services in a Monolithic Application that deal with a single relational database. Most of the relational database use ACID transaction to process each request from the client.
Microservices + Events + Docker = A Perfect Trio (dockercon)
Microservices + Events + Docker = A Perfect Trio (dockercon)Chris Richardson Microservices are an essential enabler of agility but developing and deploying them is a challenge. In order for microservices to be loosely coupled,each service must have its own datastore. This makes it difficult to maintain data consistency across services.
Deploying microservices is also a complex problem since an application typically consists of 10s or 100s of services, written in a variety of languages and frameworks. In this presentation, you will learn how to solve these problems by using an event-driven architecture to maintain data consistency and by using Docker to simplify deployment.
Events and microservices
Events and microservicesSaul Caganoff The document discusses using events and asynchronous messaging to coordinate activities across microservices. It describes how events can be used for loose coupling between services, avoiding the need for centralized orchestration. Events are proposed as a way to handle data synchronization and business processes across bounded contexts. Various options for transporting events such as syndication, web hooks, and message queues are also examined.
An eventful tour from enterprise integration to serverless and functions
An eventful tour from enterprise integration to serverless and functionsChristian Posta In this talk, Marius (@mariusbogoevici) and I (@christianposta) discuss the value of event-driven architectures (both business and technical merits) and how the landscape of integration, streaming, and messaging and now functions/lambdas have evolved to implement EDA while balancing agility, utilization, and simplicity.
Microservices + Events + Docker = A Perfect Trio by Docker Captain Chris Rich...
Microservices + Events + Docker = A Perfect Trio by Docker Captain Chris Rich...Docker, Inc. The document discusses how microservices, events, and Docker form a perfect trio for developing and deploying applications. It covers how microservices can help accelerate development but also introduce complexity that events and Docker can help address. Events are proposed to maintain data consistency between microservices rather than distributed transactions. Docker is presented as a way to containerize microservices for improved isolation, manageability and efficient deployment and scaling. The overall presentation argues this combination of techniques can help build large, complex applications.
From Rails legacy to DDD - Pivorak, Lviv
From Rails legacy to DDD - Pivorak, LvivAndrzej Krzywda Rails is optimised for the first weeks of development. At the later phases it's no longer the speed of adding new views and data that matters. It's often more about the different (and changing!) ways of using the data. The business logic gets more complicated.
DDD has answers to those problems. Detecting the bounded contexts is the crucial skill. Choose which parts of the app leave as CRUD and which could go into more of the tactical DDD.
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.
Beyond Microservices
Beyond MicroservicesEberhard Wolff This presentation shows the properties, advantages and challenges of microservices. It then discusses alternative architectures beyond microservices.
OSDC 2018 | From Monolith to Microservices by Paul Puschmann_
OSDC 2018 | From Monolith to Microservices by Paul Puschmann_NETWAYS Scaling up from two developer teams supporting a monolith to more than 20 developer teams powering a micro-service landscape is not only a matter of technical excellence but also the matter of culture and collaboration. This talk will show the positive aspects of our evolution as well as the things we learned to improve on.
Events on the outside, on the inside and at the core (jaxlondon)
Events on the outside, on the inside and at the core (jaxlondon)Chris Richardson This presentation looks at the importance of events and the role that they play in software applications. We describe how events are a key application integration mechanism and how they are used by applications to communicate with the outside world. You will learn how the microservices inside a system can use events to maintain data consistency. We discuss how easy it is to implement both these mechanisms by developing your core business logic using an event-centric approach.
Events on the outside, on the inside and at the core - Chris Richardson
Events on the outside, on the inside and at the core - Chris RichardsonJAXLondon_Conference The document discusses event sourcing and how it enables an event-driven enterprise architecture. It describes how event sourcing works by having applications persist all state changes as a sequence of events rather than current state. These events can then be used to rebuild state. When requests are received, past events are replayed to determine the current state. New events generated from requests are published for other applications. This allows for distributed transaction processing without two-phase commit and enables eventual consistency across services.
The Road To Event-Driven Architecture
The Road To Event-Driven ArchitectureSheenBrisals - The document discusses the transition of LEGO.com from a monolithic architecture to an event-driven architecture (EDA) on AWS.
- Early issues with the monolith like outages during Black Friday motivated a move to microservices and serverless. An initial serverless implementation using AWS Lambda and SQS proved the value of an event-driven approach.
- The adoption of EDA accelerated over two phases, first using services like Kinesis and Lambda, then adding Amazon EventBridge for improved event routing between services.
- Microservices were developed using a "set pieces" approach, where independent domains are developed separately but coordinated through events.
- Overall the document outlines the challenges of the monolith
Building and deploying microservices with event sourcing, CQRS and Docker (Ha...
Building and deploying microservices with event sourcing, CQRS and Docker (Ha...Chris Richardson In this talk we share our experiences developing and deploying a microservices-based application. You will learn about the distributed data management challenges that arise in a microservices architecture. We will describe how we solved them using event sourcing to reliably publish events that drive eventually consistent workflows and pdate CQRS-based views. You will also learn how we build and deploy the application using a Jenkins-based deployment pipeline that creates Docker images that run on Amazon EC2.
Microservices & Streaming Data
Microservices & Streaming DataLeon Mergen The document discusses microservices and how streaming data is important for microservices. It describes what microservices are and why they are used. It then explains some of the challenges with microservices as systems grow in complexity, such as services overloading or causing distributed deadlocks. The document proposes using an event-driven data-centric approach with event sourcing, CQRS and streaming to help address these challenges by loosely coupling services and handling failures better.
Developing event-driven microservices with event sourcing and CQRS (london Ja...
Developing event-driven microservices with event sourcing and CQRS (london Ja...Chris Richardson This is a talk I gave to the London Java Community in June 2016
In a microservices architecture, each service has its own database. While this ensures that services are loosely coupled it creates a problem: how do you maintain consistency across services without using 2PC? In this talk you will learn more about these issues and how to solve them by using an event-driven architecture. We will describe how event sourcing and Command Query Responsibility Separation (CQRS) are a great way to realize an event-driven architecture. You will learn about a simple yet powerful approach for building, modern, scalable applications.
#hacksummit 2016 - event-driven microservices – Events on the outside, on the...
#hacksummit 2016 - event-driven microservices – Events on the outside, on the...Chris Richardson This is my presentation from #hacksummit 2016
This presentation looks at the importance of events and the role that they play in applications. We describe how events are a key application integration mechanism and how they are used by applications to communicate with the outside world. You will learn how the microservices inside a system can use events to maintain data consistency. We discuss how easy it is to implement both of these mechanisms by developing your core business logic using an event-centric approach known as event sourcing.
More from Andrzej Krzywda (20)
[PL] PRUG Luty 2022 - Service objecty to za mało - jak żyć z Railsami?![[PL] PRUG Luty 2022 - Service objecty to za mało - jak żyć z Railsami?](https://cdn.slidesharecdn.com/ss_thumbnails/prugluty2022serviceobjectytozamalo-220227193403-thumbnail.jpg?width=560&fit=bounds)
[PL] PRUG Luty 2022 - Service objecty to za mało - jak żyć z Railsami?Andrzej Krzywda Service objecty dają nam sporo korzyści, ale nie rozwiązują problemów typowych dla dużych aplikacji Railsowych. Ta prezentacja podsumowuje pozostałe problemy oraz prezentuję docelową wizję opartą na DDD/CQRS.
[PL] Service objecty to za mało - jak żyć z Railsami?![[PL] Service objecty to za mało - jak żyć z Railsami?](https://cdn.slidesharecdn.com/ss_thumbnails/druglistopad2021serviceobjectytozamalo-211118112546-thumbnail.jpg?width=560&fit=bounds)
[PL] Service objecty to za mało - jak żyć z Railsami?Andrzej Krzywda Slajdy z prezentacji na DRUG #105 (zapraszamy co trzeci poniedziałek każdego miesiąca do Wrocławia).
Podczas prezentacji omawiany był etap serwisy i serwisy+ jaki można zobaczyć w wielu projektach Rails. Wskazuję na zalety tego podejścia, ale też wiele nierozwiązanych problemów.
Zanim jednak rzucimy się na kolejne kroki warto zobaczyć las zamiast pojedynczych drzew.
Tym lasem jest Domain Driven Design połączone z CQRS.
Warto zobaczyć jak wygląda taki DDD projekt aby się upewnić czy chce się w tą stronę iść.
Szczęśliwie już mamy taki nietrywialny projekt:
https://github.com/RailsEventStore/ecommerce
Warto go uruchomić, przejrzeć kod - wziąć przykładowy issue do zrobienia. A dopiero po tych doświadczeniach wdrażać kolejne kroki u siebie.
Najlepszą strategią może być strategia "readmodelowa" oparta o eventy.
Audit log with event sourcing
Audit log with event sourcingAndrzej Krzywda Audit logs are an often requested features in many apps.
When you use event sourcing, adding an event log is fairly simple.
Here I'm showing how I'm adding an audit log for an Order in an Ecommerce application. It's a Ruby on Rails application implemented using DDD and CQRS and Event Sourcing
From legacy to DDD - 5 starting steps
From legacy to DDD - 5 starting stepsAndrzej Krzywda The slides from my talk at the awesome Boiling Frogs conference in January, Wrocław, Poland. Powered by ITCorner.
Slack protips from Arkency
Slack protips from ArkencyAndrzej Krzywda We are a remote and async team of 18 developers. Our work and collaboration relies on Slack (before that we'ved used IRC).
Here are some lessons we learnt.
From legacy to DDD (slides for the screencast)
From legacy to DDD (slides for the screencast)Andrzej Krzywda This document discusses transitioning from legacy code to domain-driven design (DDD). It covers strategic and tactical DDD, including using entities, value objects, aggregates, domain events, services, and repositories. It recommends drawing context maps, deciding which contexts require more logic versus CRUD, escaping CRUD verbs, improving test coverage with mutation testing, and separating reads from writes. Key steps include wrapping legacy contexts in application services, using events between bounded contexts, and treating the frontend as a separate context. Distributed transactions and querying between contexts should be avoided. The document emphasizes an ongoing, incremental process over big rewrites.
From legacy to DDD
From legacy to DDDAndrzej Krzywda This talk was delivered at the PHPers meetup in Wroclaw, 10 August 2015.
I presented a set of techniques which help you transition from a legacy codebase to DDD. I focused more on the strategic DDD patterns like bounded contexts.
The main idea in such refactorings is to:
1. List all your (potential) bounded contexts
2. Decide which ones are deserving the DDD tactical patterns
3. Decide which ones can stay as CRUD
4. Communicate between the BCs via events
DCI - the architecture from the future
DCI - the architecture from the futureAndrzej Krzywda DCI can be seen as one of the most inspiring software architectures nowadays. Is it of any practical use?
Refactoring Rails applications with RubyMine
Refactoring Rails applications with RubyMineAndrzej Krzywda Rails applications are always fun for the first 2 months. After some time, the initial conventions don't always fit the project. The controllers get fat, the models get fat, and the views gather more logic. How to deal with this complexity?
We'll show how to apply typical refactoring recipes to put the code back in order. You'll see examples of service objects and other patterns. All of that using the RubyMine refactoring support, extended with custom shortcuts.
The slides from the JetBrains webinar - http://info.jetbrains.com/RubyMine-Webinar-June2015-registration.html
Beyond The Rails Way
Beyond The Rails WayAndrzej Krzywda The Rails Way is the reason of Rails success. It's also the reason of Rails disappointment. Why is it so?
Is there any alternative?
Service objects in Rails tests - factory_girl replacement
Service objects in Rails tests - factory_girl replacementAndrzej Krzywda Service objects provide a way to test Rails applications by encapsulating business logic and hiding implementation details. They represent use cases or scenarios and allow writing tests that are fast, easy to write, and stay in sync with production code by testing below the controller layer. However, extracting existing Rails code into service objects can be challenging.
Developer oriented
Developer orientedAndrzej Krzywda This document discusses developer-oriented project management approaches that aim to make developers happy which leads to a happy team, project, and ultimately happy customers. It touches on breaking big tasks into smaller stories, having iterations or sprints, maintaining a stream of work, assigning tasks, and the roles of project managers versus developers as managers. It also addresses balancing communication between developers and customers to avoid lack of or overcommunication through limiting meetings and using asynchronous communication when possible.
Can you TDD Rails?
Can you TDD Rails?Andrzej Krzywda The document discusses how test-driven development (TDD) can help address common fears and issues developers experience when working with existing or new code. It argues that while TDD may seem difficult with Rails, the challenges are likely due more to issues with the code structure rather than limitations of TDD or Rails. The document differentiates between hard skills related to TDD tools and techniques versus softer skills around understanding requirements, isolating business logic, continuous delivery, and refactoring tests. It provides suggestions for improving TDD skills like practicing with code katas, extracting business logic into gems, and doing "domain spikes" with in-memory objects to focus on logic alone.
A programmer or a business consultant?
A programmer or a business consultant?Andrzej Krzywda David Chappell began his career as a musician playing in bars, but realized he was more of a "liquor salesman" promoting the bars rather than an artist. As a programmer or business consultant, the focus should be on helping customers achieve their goals within budget constraints by questioning requirements, cutting unnecessary scope, and working as one team with the customer rather than just delivering features.
Rails refactoring call for help
Rails refactoring call for helpAndrzej Krzywda I'm working on techniques that help you safely refactor your Rails codebase. At the start I'm mostly focusing on the Rails controllers.
You can sign up at http://rails-refactoring.com/ for free rails refactoring lessons.
Meanwhile, please send me more examples of Rails controllers, so that I can discover better patterns.
[email protected]
![[Polish] Praca zdalna, praca asynchroniczna](https://cdn.slidesharecdn.com/ss_thumbnails/andrzejkrzywda-130723173400-phpapp02-thumbnail.jpg?width=560&fit=bounds)
Use cases in the code with AOP
Use cases in the code with AOPAndrzej Krzywda The document discusses the importance of use cases in code. It provides an example use case class for playing a team game that defines roles, algorithms, and domain objects without mentioning the GUI, persistence, or external API calls. The goal is clean use case code, and aspects like the GUI and persistence can be handled separately through aspect-oriented programming and dependency injection of roles at runtime.
Single Page Applications with CoffeeScript [Polish]![Single Page Applications with CoffeeScript [Polish]](https://cdn.slidesharecdn.com/ss_thumbnails/confitura2012singlepageapps-120702095109-phpapp02-thumbnail.jpg?width=560&fit=bounds)
Single Page Applications with CoffeeScript [Polish]Andrzej Krzywda Slides from my talk at the Confitura conference in Warsaw.
Fallout icons are from http://wikia.fallout.com
Madeleine on Rails
Madeleine on RailsAndrzej Krzywda This document discusses a work in progress plugin called Off the Rails that aims to use the Madeleine object database with Ruby on Rails. Madeleine allows objects to live in memory and be serialized to files, providing extremely fast performance if enough RAM is available. Changes are serialized as "command objects" and the overall concept is called "Prevalence," similar to the Java implementation Prevayler. The plugin would integrate Madeleine into Rails by having a single process read from a snapshot file and start the AppService to begin the application.
TDD with Rails
TDD with RailsAndrzej Krzywda Andrzej Krzywda is a software developer who has been using Test Driven Development (TDD) since 2001. TDD involves writing tests before production code to help visualize goals and requirements. The tests help achieve project goals and requirements by ensuring the code works as intended. TDD uses both acceptance tests to verify functionality meets requirements, and unit tests to ensure code quality.
Recently uploaded (20)
UberEats clone app Development TechBuilder
UberEats clone app Development TechBuilderTechBuilder Our food delivery app development solutions are designed to cater to varied business models, whether you are a startup aiming to scale, an enterprise-class business, or a niche player. With scalability, easy-to-use interfaces, and powerful AI capabilities, our solutions scale with your vision.
For more Please Visit Here : https://techbuilder.ai/food-delivery-app-development/
And overview of Nasdanika Models and their applications
And overview of Nasdanika Models and their applicationsPavel Vlasov This presentation provides an overview of Nasdanika metamodels and their applications - reference documentation, analysis, code generation, use with GenAI operating on complex structures instead of text - humans don't think in text, they think in images (diagrams) - objects and their relationships. Translating human thoughts to text is an "expensive" and error prone process. And this is where diagramming, modeling, and generation of textual description from a model can help humans and GenAI to communicate better.
Intranet Examples That Are Changing the Way We Work
Intranet Examples That Are Changing the Way We WorkBizPortals Solutions In today’s workplace, staying connected is more important than ever. Whether teams are remote, hybrid, or back in the office, communication and collaboration are at the heart of getting things done. But here’s the truth — outdated intranets just don’t cut it anymore.
wAIred_LearnWithOutAI_LunchAndLearn_27052025.pptx
wAIred_LearnWithOutAI_LunchAndLearn_27052025.pptxSimonedeGijt In today’s world, artificial intelligence (AI) is transforming the way we learn. This talk will explore how we can use AI tools to enhance our learning experiences.
But as we embrace these new technologies, we must also ask ourselves: Are we becoming less capable of thinking for ourselves? Do these tools make us smarter, or do they risk dulling our critical thinking skills? This talk will encourage us to think critically about the role of AI in our education. Together, we will discover how to use AI to support our learning journey while still developing our ability to think critically.
Offensive Security Penetration Testing 
Offensive Security Penetration Testing Purple Box Purple Box offers expert offensive security penetration testing to proactively identify and exploit weaknesses in your systems—just like a real attacker would. Our ethical hackers simulate advanced threats to uncover hidden vulnerabilities, test your defenses, and deliver actionable insights to strengthen your security posture.
🤖🤖🤖Charasteristic of Agentic AI 🤖🤖🤖
🤖🤖🤖Charasteristic of Agentic AI 🤖🤖🤖MOSIUOA WESI This presentation provides an overview of Agentic AI, intelligent systems capable of autonomous decision-making and action with minimal supervision. It highlights how these systems interact with their environment, learn over time, and adapt to complex situations. The content outlines the transformative potential of Agentic AI across industries and emphasizes the importance of understanding its core features and challenges.
Optimising Claims Management with Claims Processing Systems
Optimising Claims Management with Claims Processing SystemsInsurance Tech Services A Claims Processing System enhances customer satisfaction, efficiency, and compliance by automating the claims lifecycle—enabling faster settlements, fewer errors, and greater transparency. Explore More - https://www.damcogroup.com/insurance/claims-management-software
List Unfolding - 'unfold' as the Computational Dual of 'fold', and how 'unfol...
List Unfolding - 'unfold' as the Computational Dual of 'fold', and how 'unfol...Philip Schwarz In this deck we look at the following:
* how unfolding lists is the computational dual of folding lists
* different variants of the function for unfolding lists
* how they relate to the iterate function
Techdebt handling with cleancode focus and as risk taker
Techdebt handling with cleancode focus and as risk takerRajaNagendraKumar ShivohamAI to handle techdebt with single handedly and with 2 decades of code vibe coding excellence
How to Recover Hacked Gmail Account || Help Email Tales
How to Recover Hacked Gmail Account || Help Email TalesRoger Reed Due to weak security measures, there is a high chance that your email account will get hacked. If you are also unable to access your Gmail account, then various solutions might help you get back to your account. So, keep reading to learn everything in great detail.
Why-Choose-an-Authorised-Microsoft-Reseller.pptx
Why-Choose-an-Authorised-Microsoft-Reseller.pptxMichael cole Choosing an authorized Microsoft reseller ensures that your business gets authentic software, professional licensing guidance, and constant technical support.Certified resellers offer secure deployment, compliance with Microsoft standards, and tailored cloud solutions — helping businesses maximize ROI, reduce risks, and stay up to date with the latest Microsoft innovations.
Salesforce Experience Cloud Consulting.pdf
Salesforce Experience Cloud Consulting.pdfVALiNTRY360
VALiNTRY360’s Salesforce Experience Cloud Consulting services empower organizations to build personalized, engaging digital experiences for customers, partners, and employees. Our certified Salesforce experts help you design, implement, and optimize Experience Cloud portals tailored to your business goals. From self-service communities to partner collaboration hubs, we ensure seamless integration, enhanced user engagement, and scalable solutions. Whether you're improving customer support or streamlining partner communication, VALiNTRY360 delivers strategic consulting to maximize the value of Salesforce Experience Cloud. Trust us to transform your digital experiences into powerful tools that drive loyalty, efficiency, and growth. Partner with VALiNTRY360 to elevate every user interaction.
For more info visit us https://valintry360.com/salesforce-experience-cloud
ICDL FULL STANDARD 2025 Luisetto mauro - Academia domani- 55 HOURS LONG pdf
ICDL FULL STANDARD 2025 Luisetto mauro - Academia domani- 55 HOURS LONG pdfM. Luisetto Pharm.D.Spec. Pharmacology .
German Marketo User Group - May 2025 survey results
German Marketo User Group - May 2025 survey resultsBradBedford3 Survey results from the May 2025 German Marketo user Group
Climate-Smart Agriculture Development Solution.pptx
Climate-Smart Agriculture Development Solution.pptxjulia smits A technology-driven solution designed to promote sustainable, resilient, and productive farming practices. It integrates data, smart tools, and climate insights to help farmers adapt to climate change, optimize resource use, and boost yields sustainably.
How to Create a White Label Crypto Exchange.pdf
How to Create a White Label Crypto Exchange.pdfzak jasper This comprehensive guide will walk you through the 15 essential steps to develop your White Label Exchange, providing insights, tips, and crucial considerations for a successful venture.
grade 9 ai project cycle Artificial intelligence.pptx
grade 9 ai project cycle Artificial intelligence.pptxmanikumar465287 AI project cycle Artificial intelligence Artificial intelligence Artificial intelligence Artificial intelligenceArtificial intelligence Artificial intelligence Artificial intelligence Artificial intelligence Artificial intelligence Artificial intelligence Artificial intelligence Artificial intelligence Artificial intelligence Artificial intelligence Artificial intelligence Artificial intelligence
ICDL FULL STANDARD 2025 Luisetto mauro - Academia domani- 55 HOURS LONG pdf
ICDL FULL STANDARD 2025 Luisetto mauro - Academia domani- 55 HOURS LONG pdfM. Luisetto Pharm.D.Spec. Pharmacology
Event driven without microservices
- 2. Event-driven requires modules and events
- 3. Modules can be deployed as microservices but in most cases it’s overkill 😎
- 4. You can be event-driven in a monolithic server
- 5. A monolith with modules is called a modulith
- 6. Modulith is the way to go unless you really have strong arguments for the microservices overhead
- 7. In short: Event-driven is orthogonal to microservices
- 9. You can go microservices without going event-driven But that’s the worst possible choice 😂
- 10. You can go event-driven within one modulith Best choice 💰
- 11. What about event stores or message buses? Do we need external tools like Kafka or RabbitMQ? NO 😡 In most cases that’s an overkill
- 12. All you need is some way of: • publishing events (in memory) • storing events (in db tables is fine)
- 13. RailsEventStore is exactly this • Keeps events and streams in relational db (postgres is great, mysql too) • Helps with publishing events
- 14. Conclusion • Don’t go for microservices • Build a modulith • Go event-driven and decouple modules • Enjoy a simple infrastructure and great modularity