Microservices and Redis #redisconf Keynote

•

6 recomendaciones•14,417 vistas

This is a keynote talk that I gave at RedisConf 2016. It answers three questions: What are microservices? Why should you use them? Where does Redis fit into a microservices architecture? You can find the example code here: https://github.com/eventuate-examples/eventuate-examples-restaurant-management

Software

Microservices and Redis
Chris Richardson
Founder of Eventuate.io
Founder of the original CloudFoundry.com
Author of POJOs in Action
@crichardson
chris@chrisrichardson.net
http://eventuate.io

@crichardson
The monolithic architecture
Tomcat
Browser
WAR
SQL
database
HTML
REST/JSON
Client
App
Simple to ….
Develop
Test
Deploy
Scale
Catalog
Module
Reviews
Module
Orders
Module
StoreFront UI
Module

@crichardson
But successful
applications
keep growing
….
Eventually, agile
development
and
deployment
becomes
impossible

@crichardson
Microservice architecture = functional
decomposition
Browser
Mobile
Device
Store
Front UI
API
Gateway
Catalog
Service
Review
Service
Order
Service
…
Service
Catalog
Database
Review
Database
Order
Database
…
Database
HTML
REST
REST

@crichardson
Microservices are not a free lunch
BUT
for most large, complex applications are good
choice

Using Redis within a service
Caching
High performance messaging
High performance database
Catalog
Service
Catalog
DB

@crichardson
Using Redis for inter-service communication
API
Gateway
Catalog
Service
Review
Service
…
Service
Pub/Sub
Need Product
Details X
GET /product/X
Need … Need … Need …Info Info Info

@crichardson
Redis and the API Gateway
API
Gateway
Caching
Rate limiting
Routing

@crichardson
How to maintain data consistency?

@crichardson
Database per service
Catalog
Service
Review
Service
Order
Service
…
Service
Catalog
Database
Review
Database
Order
Database
…
Database
How to maintain data
consistency without
2PC?

@crichardson
Customer DB
How to maintain data consistency without
2PC?
Order DB
Order Service
placeOrder()
Customer Service
updateCreditLimit()
Customer
creditLimit
...
has ordersbelongs toOrder
total
Invariant:
sum(open order.total) <= customer.creditLimit
?

@crichardson
Use event-driven, eventually consistent order
processing
Order
Service
Customer
Service
Order created
Credit Reserved
Credit Check Failed
Place Order
OR

@crichardson
How to atomically update database and
publish an event without 2PC?
Order Service
Order
Database
Message Broker
insert Order
publish
OrderCreatedEvent
dual write problem
?

@crichardson
Use event sourcing
Order Service
Order
Database
Event Store
insert Order
Save
OrderCreatedEvent
X
Persistence
and notiﬁcation

@crichardson
Event sourcing: persists events
NOT current state
Event table
Entity type
Event
id
Entity
id
Event
data
Order 902101 …OrderApproved
Order 903101 …OrderShipped
Event
type
Order 901101 …OrderCreated Order
state
total
Replay

@crichardson
Find recent, valuable customers
SELECT *
FROM CUSTOMER c, ORDER o
WHERE
c.id = o.ID
AND o.ORDER_TOTAL > 100000
AND o.STATE = 'SHIPPED'
AND c.CREATION_DATE > ?
Customer Service
Order Service
What if event
sourcing is used?
…. is no longer easy

@crichardson
Command Query Responsibility Segregation
(CQRS)
Command side
Commands
Aggregate
Event Store
Events
Query side
Queries
Materialized
View
Events
POST
PUT
DELETE GET

@crichardson
Food to Go example - on github.com
http://bit.ly/redis-pia
94619:Monday [0700_2:1430, 1130_1:1430, ...]
94619:Tuesday [0700_2:1430, 1130_1:1430, ...]
… …
Restaurant
View
Updater
Service
Restaurant
View
Query
Service
ZRANGEBYSCORE
Event Store
Restaurant
events Materialized view of
restaurant locations
and opening hours
GET
available
restaurants
ZADD
ZREM
Sorted sets

@crichardson
Summary
Organize into small, agile, autonomous teams responsible for one or more
microservices
Use an event-driven architecture, based on event sourcing and CQRS
Use Redis throughout a microservices architecture

Thank you!
@crichardson
http://eventuate.io

Más contenido relacionado

La actualidad más candente

This is a talk I gave at QCON ArchSummit in Shenzhen. The microservice architecture structures an application as a set of loosely coupled, collaborating services. Maintaining data consistency is challenging since each service has its own database to ensure loose coupling. To make matters worse, for a variety of reasons distributed transactions using JTA are not an option for modern applications. In this talk we describe an alternative transaction model known as a saga. You will learn about the benefits and drawbacks of using sagas. We describe how sagas are eventually consistent rather than ACID and what this means for developers. You will learn how to design and implement sagas in a Java application.

ArchSummit Shenzhen - Using sagas to maintain data consistency in a microserv...

Chris Richardson

This is a keynote I gave at Oracle Code 2017 in New York: https://developer.oracle.com/code/newyork The microservice architecture is becoming increasingly popular. However, frequent references to using “a microservice to solve a problem” suggest that the concept is not universally well understood. In this talk we define the microservice architecture as an architectural style and explain what that actually means. You will learn why the architecture that you pick for your application matters. We describe how the primary goal of the microservice architecture is to enable continuous delivery/deployment and how it achieves that. You will learn how to solve key challenges with decomposing an application into microservices. We describe why there is no such thing as a microservice!

There is no such thing as a microservice! (oracle code nyc)

Chris Richardson

Microservices in Java and Scala (sfscala)

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. This talk was given at the Berlin Microxchg conference and the Munich microservices meetup.

Building and deploying microservices with event sourcing, CQRS and Docker (Be...

Chris Richardson

The Domain Model pattern is a great way to develop complex business logic. Unfortunately, a typical domain model is a tangled, birds nest of classes. It can’t be decomposed into microservices. Moreover, business logic often relies on ACID transactions to maintain consistency. Fortunately, there is a solution to this problem: aggregates. An aggregate is an often overlooked modeling concept from the must read book Domain Driven Design. In this talk you will learn how aggregates enable you to develop business logic for the modern world of microservices and NoSQL. We will describe how to use aggregates to design modular business logic that can be partitioned into microservices. You will learn how aggregates enable you to use eventual consistency instead of ACID. We will describe the design of a microservice that is built using aggregates, and Spring Cloud.

Developing microservices with aggregates (SpringOne platform, #s1p)

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.

Developing event-driven microservices with event sourcing and CQRS (london Ja...

Chris Richardson

he Domain Model pattern is a great way to develop complex business logic. Unfortunately, a typical domain model is a tangled, birds nest of classes. It can’t be decomposed into microservices. Moreover, business logic often relies on ACID transactions to maintain consistency. Fortunately, there is a solution to this problem: aggregates. An aggregate is an often overlooked modeling concept from the must read book Domain Driven Design. In this talk you will learn how aggregates enable you to develop business logic for the modern world of microservices and NoSQL. We will describe how to use aggregates to design modular business logic that can be partitioned into microservices. You will learn how aggregates enable you to use eventual consistency instead of ACID. We will describe the design of a microservice that is built using aggregates, and Spring Cloud.

Developing microservices with aggregates (devnexus2017)

Chris Richardson

In this presentation, I describe the essential characteristics of the microservice architecture. You will learn about the benefits and drawbacks of the microservice architecture and when it makes sense to use it. I discuss how the microservice architecture is not a silver bullet. You will learn about the microservice pattern language, which is a collection of patterns that solve architecture and design issues that you will encounter when using microservices.

Kong Summit 2018 - Microservices: decomposing applications for testability an...

Chris Richardson

An overview of the Eventuate Platform

Chris Richardson

This is a presentation I gave at QCONSF 2017 The services in a microservice architecture must be loosely coupled and so cannot share database tables. What’s more, two phase commit (a.k.a. a distributed transaction) is not a viable option for modern applications. Consequently, a microservices application must use the Saga pattern, which maintains data consistency using a series of local transactions. In this presentation, you will learn how sagas work and how they differ from traditional transactions. We describe how to use sagas to develop business logic in a microservices application. You will learn effective techniques for orchestrating sagas and how to use messaging for reliability. We will describe the design of a saga framework for Java and show a sample application.

QCONSF - ACID Is So Yesterday: Maintaining Data Consistency with Sagas

Chris Richardson

To deliver a large complex application rapidly, frequently and reliably, you often must use the microservice architecture. The microservice architecture is an architectural style that structures the application as a collection of loosely coupled services. One challenge with using microservices is that in order to be loosely coupled each service has its own private database. As a result, implementing transactions and queries that span services is no longer straightforward. In this presentation, you will learn how event-driven microservices address this challenge. I describe how to use sagas, which is an asynchronous messaging-based pattern, to implement transactions that span services. You will learn how to implement queries that span services using the CQRS pattern, which maintain easily queryable replicas using events.

Events to the rescue: solving distributed data problems in a microservice arc...

Chris Richardson

The microservice architecture structures an application as a set of loosely coupled, collaborating services. Maintaining data consistency is challenging since each service has its own database to ensure loose coupling. To make matters worse, for a variety of reasons distributed transactions using JTA are not an option for modern applications. In this talk we describe an alternative transaction model known as a saga. You will learn about the benefits and drawbacks of using sagas. We describe how sagas are eventually consistent rather than ACID and what this means for developers. You will learn how to design and implement sagas in a Java application.

Gluecon: Using sagas to maintain data consistency in a microservice architecture

Chris Richardson

This is a keynote I gave at the SATURN 2017 in Denver: https://www.sei.cmu.edu/saturn/2017/ The microservice architecture is becoming increasingly popular. However, frequent references to using “a microservice to solve a problem” suggest that the concept is not universally well understood. In this talk we define the microservice architecture as an architectural style and explain what that actually means. You will learn why the architecture that you pick for your application matters. We describe how the primary goal of the microservice architecture is to enable continuous delivery/deployment and how it achieves that. You will learn how to solve key challenges with decomposing an application into microservices. We describe why there is no such thing as a microservice!

Saturn2017: No such thing as a microservice!

Chris Richardson

Events are very much on the edge of traditional applications, which use them as an application integration mechanism. The classic example is an ecommerce system. When a customer places an order, the order management application publishes an event, which triggers the fulfillment application to action. But today, microservices and DDD—which is a great foundation for microservices—are at the core of the application. Events play an essential role in modern applications. Chris Richardson explains why events are a key application integration mechanism and how they are used by applications to communicate with the outside world. You’ll learn how the microservices inside an application use events to maintain data consistency and discover how to go one step further and make events an integral part of your domain logic.

OReilly SACON2018 - Events on the outside, on the inside, and at the core

Chris Richardson

When architecting an application, you need to choose between the traditional monolithic architecture consisting of a single large application, or the more fashionable microservices architecture consisting of many smaller services. But rather than blindly picking the familiar or the fashionable, it's important to remember what Fred Books said almost 30 years ago: there are no silver bullets in software. Every architectural decision has both benefits and drawbacks. Whether the benefits of one approach outweigh the drawbacks greatly depends upon the context of your particular project. Moreover, even if you adopt the microservices architecture, you must still make numerous other design decisions, each with their own trade-offs.

A Pattern Language for Microservices (@futurestack)

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.

Microservices + Events + Docker = A Perfect Trio (dockercon)

Chris Richardson

Event sourcing persists each entity as a sequence of state changing events. An entity’s current state is derived by replaying those events. Event sourcing is a great way to implement event-driven microservices. When one service updates an entity, the new events are consumed by other services, which then update their own state. In this talk we describe how to implement business logic using event sourcing. You will learn how to write functional, immutable domain models in Scala. We will compare and contrast a hybrid OO/FP design with a purely functional approach.

Developing functional domain models with event sourcing (oakjug, sfscala)

Chris Richardson

Modern, cloud-native applications typically use a microservices architecture in conjunction with NoSQL and/or sharded relational databases. However, in order to successfully use this approach you need to solve some distributed data management problems including how to maintain consistency between multiple databases 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.

Developing Event-driven Microservices with Event Sourcing & CQRS (gotoams)

Chris Richardson

The services in a microservice architecture must be loosely coupled and so cannot share database tables. What’s more, two-phase commit (aka a distributed transaction) is not a viable option for modern applications. Consequently, a microservice-based application must use so-called sagas to maintain data consistency between services. In this presentation, you will learn how sagas work and how they differ from traditional ACID transactions. You will also learn how to design and implement sagas for your applications.

JavaOne2017: ACID Is So Yesterday: Maintaining Data Consistency with Sagas

Chris Richardson

The microservice architecture functionally decomposes an application into a set of services. Each service has its own private database that’s accessible only indirectly through the services API. Consequently, implementing queries and transactions that span multiple services is challenging. In this session, you will learn how to solve these distributed data management challenges by using asynchronous messaging. The presentation describes how to implement transactions with sagas, which are sequences of local transactions coordinated by use of messages. You will learn how to implement queries using command query responsibility segregation (CQRS), which uses events to maintain replicas, and will hear about the key role messaging plays in a microservice architecture.

Oracle Code One: Events and commands: developing asynchronous microservices

Chris Richardson

La actualidad más candente (20)

ArchSummit Shenzhen - Using sagas to maintain data consistency in a microserv...

There is no such thing as a microservice! (oracle code nyc)

Microservices in Java and Scala (sfscala)

Building and deploying microservices with event sourcing, CQRS and Docker (Be...

Developing microservices with aggregates (SpringOne platform, #s1p)

Developing event-driven microservices with event sourcing and CQRS (london Ja...

Developing microservices with aggregates (devnexus2017)

Kong Summit 2018 - Microservices: decomposing applications for testability an...

An overview of the Eventuate Platform

QCONSF - ACID Is So Yesterday: Maintaining Data Consistency with Sagas

Events to the rescue: solving distributed data problems in a microservice arc...

Gluecon: Using sagas to maintain data consistency in a microservice architecture

Saturn2017: No such thing as a microservice!

OReilly SACON2018 - Events on the outside, on the inside, and at the core

A Pattern Language for Microservices (@futurestack)

Microservices + Events + Docker = A Perfect Trio (dockercon)

Developing functional domain models with event sourcing (oakjug, sfscala)

Developing Event-driven Microservices with Event Sourcing & CQRS (gotoams)

JavaOne2017: ACID Is So Yesterday: Maintaining Data Consistency with Sagas

Oracle Code One: Events and commands: developing asynchronous microservices

Destacado

Microservices - it's déjà vu all over again

Arnon Rotem-Gal-Oz

Wix.com Back-end Engineering Guild Manifesto

Aviran Mordo

Scaling wix.com to 100 million users

Aviran Mordo

Building reliable systems from unreliable components

Arnon Rotem-Gal-Oz

Working in a fast-growing company that doubles in size every year, maintaining the quality of products and engineers is a very challenging task. In this talk I will describe how Wix corporate structure evolved from functional teams to gangs, cross-functional teams responsible for end-to-end delivery; guilds, professional groups responsible for methodology, best practices, and training; and mini-companies that serve as internal startups to support rapid growth while maintaining velocity. I will also discuss how we poured our culture into a game-like “guild day”, that helps us maintain alignment, keep the high quality of our work and people, share knowledge, recruit and preserve the best developers, and support a quality-based culture of innovation.

Scaling Wix engineering

Aviran Mordo

Many small startups build their systems on top of a traditional toolset like Tomcat, Hibernate, and MySQL. These systems are used because they facilitate easy development and fast progress, but many of them are monolithic and have limited scalability. So as a startup grows, the team is confronted with the problem of how to evolve the system and make it scalable. Facing the same dilemma, Wix.com grew from 0 to 60 million users in just a few years. Facing some interesting challenges, like performance and availability. Traditional performance solutions, such as caching, would not help due to a very long tail problem which causes caching to be highly inefficient. And because every minute of downtime means customers lose money, the product needed to have near 100% availability. Solving these issues required some interesting and out-of-the-box thinking, and this talk will discuss some of these strategies: building a highly preformant, highly available and highly scalable system; and leveraging microservices architecture and multi-cloud platforms to help build a very efficient and cost-effective system.

Scaling wix with microservices architecture devoxx London 2015

Aviran Mordo

Destacado (6)

Microservices - it's déjà vu all over again

Wix.com Back-end Engineering Guild Manifesto

Scaling wix.com to 100 million users

Building reliable systems from unreliable components

Scaling Wix engineering

Scaling wix with microservices architecture devoxx London 2015

Similar a Microservices and Redis #redisconf Keynote

Today, there are several trends that are forcing application architectures to evolve. Users expect a rich, interactive and dynamic user experience on a wide variety of clients including mobile devices. Applications must be highly scalable, highly available and run on cloud environments. Organizations often want to frequently roll out updates, even multiple times a day. Consequently, it's no longer adequate to develop simple, monolithic web applications that serve up HTML to desktop browsers.In this talk we describe the limitations of a monolithic architecture. You will learn how to use the scale cube to decompose your application into a set of narrowly focused, independently deployable services. We will also discuss how an event-based approach addresses the key challenges of developing applications with this architecture.

Microservices: Decomposing Applications for Deployability and Scalability (ja...

Chris Richardson

The micro-service architecture, which structures an application as a set of small, narrowly focused, independently deployable services, is becoming an increasingly popular way to build applications. This approach avoids many of the problems of a monolithic architecture. It simplifies deployment and let’s you create highly scalable and available applications. In this talk we describe the micro-service architecture and how to use it to build complex applications. You will learn how techniques such as Command Query Responsibility Segregation (CQRS) and Event Sourcing address the key challenges of developing applications with this architecture. We will also cover some of the various frameworks such as NodeJS and Spring Boot that you can use to implement micro-services.

Developing applications with a microservice architecture (svcc)

Chris Richardson

Developing applications with a microservice architecture (SVforum, microservi...

Chris Richardson

Successful applications have a habit of growing. What’s more, the rate of growth increases over time because the development team typically gets larger. Eventually, the application will become extremely large and the organization ends up in monolithic hell. All aspects of development, testing and deployment are slow and painful. It’s impossible for the developers to keep up with the demands of the business. And, to make matters worse the application uses a technology stack that is increasingly obsolete. The way to escape monolithic hell is to migrate to the microservice architecture. In this talk, you will learn about the essential characteristics of microservices. I describe the benefits and drawbacks of the microservice architecture and when it makes sense to use it. You will learn about the design problems you will encounter when using microservices. I describe how to solve this problems by applying the microservices pattern language. You will learn how the microservice architecture accelerates the delivery of large, complex applications. Given at Silicon Valley Code Camp 2018

SVCC Microservices: Decomposing Applications for Testability and Deployability

Chris Richardson

This is a talk I gave at Code Freeze 2018: The microservice architecture is becoming increasingly popular. However, frequent references to using “a microservice to solve a problem” suggest that the concept is not universally well understood. In this talk, I define the microservice architecture as an architectural style and explain what that actually means. I also describe how the primary goal of the microservice architecture is to enable continuous delivery and deployment, and how it achieves that. You will learn why the architecture that you pick for your application matters. And you will learn how to solve key challenges with decomposing an application into microservices. This talk explains why there is no such thing as a microservice!

Code Freeze 2018: There is no such thing as a microservice!

Chris Richardson

The micro-service architecture, which structures an application as a set of small, narrowly focused, independently deployable services, is becoming an increasingly popular way to build applications. This approach avoids many of the problems of a monolithic architecture. It simplifies deployment and let’s you create highly scalable and available applications. In this keynote we describe the micro-service architecture and how to use it to build complex applications. You will learn how techniques such as Command Query Responsibility Segregation (CQRS) and Event Sourcing address the key challenges of developing applications with this architecture. We will also cover some of the various frameworks such as Spring Boot that you can use to implement micro-services.

#JaxLondon keynote: Developing applications with a microservice architecture

Chris Richardson

Developing Applications with a Micro Service Architecture - Chris Richardson

JAXLondon2014

Microservices + Events + Docker = A Perfect Trio by Docker Captain Chris Rich...

Docker, Inc.

Today, there are several trends that are forcing application architectures to evolve. Users expect a rich, interactive and dynamic user experience on a wide variety of clients including mobile devices. Applications must be highly scalable, highly available and run on cloud environments. Organizations often want to frequently roll out updates, even multiple times a day. Consequently, it’s no longer adequate to develop simple, monolithic web applications that serve up HTML to desktop browsers. In this talk we describe the limitations of a monolithic architecture. You will learn how to use the scale cube to decompose your application into a set of narrowly focused, independently deployable back-end services and an HTML 5 client. We will also discuss the role of technologies such as Spring and AMQP brokers. You will learn how a modern PaaS such as Cloud Foundry simplifies the development and deployment of this style of application.

Decomposing applications for deployability and scalability(SpringSource webinar)

Chris Richardson

My talk from http://microxchg.io/2016/index.html. Here is the video - https://www.youtube.com/watch?v=1mcVQhbkA2U When architecting an enterprise Java application, you need to choose between the traditional monolithic architecture consisting of a single large WAR file, or the more fashionable microservices architecture consisting of many smaller services. But rather than blindly picking the familiar or the fashionable, it’s important to remember what Fred Books said almost 30 years ago: there are no silver bullets in software. Every architectural decision has both benefits and drawbacks. Whether the benefits of one approach outweigh the drawbacks greatly depends upon the context of your particular project. Moreover, even if you adopt the microservices architecture, you must still make numerous other design decisions, each with their own trade-offs. A software pattern is an ideal way of describing a solution to a problem in a given context along with its tradeoffs. In this presentation, we describe a pattern language for microservices. You will learn about patterns that will help you decide when and how to use microservices vs. a monolithic architecture. We will also describe patterns that solve various problems in a microservice architecture including inter-service communication, service registration and service discovery.

Microservices pattern language (microxchg microxchg2016)

Chris Richardson

CHRIS RICHARDSON FOUNDER, EVENTUATE When architecting an enterprise Java application, you need to choose between the traditional monolithic architecture consisting of a single large WAR file, or the more fashionable microservices architecture consisting of many smaller services. But rather than blindly picking the familiar or the fashionable, it’s important to remember what Fred Books said almost 30 years ago: there are no silver bullets in software. Every architectural decision has both benefits and drawbacks. Whether the benefits of one approach outweigh the drawbacks greatly depends upon the context of your particular project. Moreover, even if you adopt the microservices architecture, you must still make numerous other design decisions, each with their own trade-offs. A software pattern is an ideal way of describing a solution to a problem in a given context along with its tradeoffs. In this presentation, we describe a pattern language for microservices. You will learn about patterns that will help you decide when and how to use microservices vs. a monolithic architecture. We will also describe patterns that solve various problems in a microservice architecture including inter-service communication, service registration and service discovery.

A pattern language for microservices

VMware Tanzu

When architecting an enterprise Java application, you need to choose between the traditional monolithic architecture consisting of a single large WAR file, or the more fashionable microservices architecture consisting of many smaller services. But rather than blindly picking the familiar or the fashionable, it’s important to remember what Fred Books said almost 30 years ago: there are no silver bullets in software. Every architectural decision has both benefits and drawbacks. Whether the benefits of one approach outweigh the drawbacks greatly depends upon the context of your particular project. Moreover, even if you adopt the microservices architecture, you must still make numerous other design decisions, each with their own trade-offs. A software pattern is an ideal way of describing a solution to a problem in a given context along with its tradeoffs. In this presentation, we describe a pattern language for microservices. You will learn about patterns that will help you decide when and how to use microservices vs. a monolithic architecture. We will also describe patterns that solve various problems in a microservice architecture including inter-service communication, service registration and service discovery.

A pattern language for microservices (melbourne)

Chris Richardson

The microservice architecture is becoming increasing important. But what is it exactly? Why should you care about microservices? And, what do you need to do to ensure that your organization uses the microservice architecture successfully? In this talk, I’ll answer these and other questions using shapes as visual metaphors. You will learn about the motivations for the microservice architecture and why simply adopting microservices is insufficient. I describe essential characteristics of microservices, You will learn how a successful microservice architecture consist of loosely coupled services with stable APIs that communicate asynchronous. I will cover strategies for effectively testing microservices.

JFokus: Cubes, Hexagons, Triangles, and More: Understanding Microservices

Chris Richardson

Oracle Code Sydney - There is no such thing as a microservice!

Chris Richardson

It’s no longer acceptable to develop large, monolithic, single-language, single-framework Web applications. In this session, you will learn how to use the scale cube to decompose your monolithic Web application into a set of narrowly focused, independently deployable services. The presentation discusses how a modular architecture makes it easy to adopt newer and better languages and technologies. You will learn about the various communication mechanisms—synchronous and asynchronous—that these services can use.

Decompose That WAR! Architecting for Adaptability, Scalability, and Deployabi...

Chris Richardson

Introduction to MicroServices (Oakjug)

Chris Richardson

RedisConf17 - A pattern language for microservices - Chris Richardson

Redis Labs

YOW! Perth 2019 presentation The microservice architecture is becoming increasing important. But what is it exactly? Why should you care about microservices? And, what do you need to do to ensure that your organization uses the microservice architecture successfully? In this talk, I’ll answer these and other questions using shapes as visual metaphors. You will learn about the motivations for the microservice architecture and why simply adopting microservices is insufficient. I describe essential characteristics of microservices, You will learn how a successful microservice architecture consist of loosely coupled services with stable APIs that communicate asynchronous. I will cover strategies for effectively testing microservices.

YOW! Perth: Cubes, Hexagons, Triangles, and More: Understanding the Microserv...

Chris Richardson

The microservice architecture is growing in popularity. It is an architectural style that structures an application as a set of loosely coupled services that are organized around business capabilities. Its goal is to enable the continuous delivery of large, complex applications. However, the microservice architecture is not a silver bullet and it has some significant drawbacks. The goal of the microservices pattern language is to enable software developers to apply the microservice architecture effectively. It is a collection of patterns that solve architecture, design, development and operational problems. In this talk, I’ll provide an overview of the microservice architecture and describe the motivations for the pattern language. You will learn about the key patterns in the pattern language.

A pattern language for microservices - June 2021

Chris Richardson

The microservice architecture is becoming increasingly important. But what is it exactly? Why should you care about microservices? And, what do you need to do to ensure that your organization uses the microservice architecture successfully? In this talk, I’ll answer these and other questions. You will learn about the motivations for the microservice architecture and why simply adopting microservices is insufficient. I describe essential characteristics of microservices, You will learn how a successful microservice architecture consists of loosely coupled services with stable APIs that communicate asynchronously.

TDC2020 - The microservice architecture: enabling rapid, reliable, frequent a...

Chris Richardson

Similar a Microservices and Redis #redisconf Keynote (20)

Microservices: Decomposing Applications for Deployability and Scalability (ja...

Developing applications with a microservice architecture (svcc)

Developing applications with a microservice architecture (SVforum, microservi...

SVCC Microservices: Decomposing Applications for Testability and Deployability

Code Freeze 2018: There is no such thing as a microservice!

#JaxLondon keynote: Developing applications with a microservice architecture

Developing Applications with a Micro Service Architecture - Chris Richardson

Microservices + Events + Docker = A Perfect Trio by Docker Captain Chris Rich...

Decomposing applications for deployability and scalability(SpringSource webinar)

Microservices pattern language (microxchg microxchg2016)

A pattern language for microservices

A pattern language for microservices (melbourne)

JFokus: Cubes, Hexagons, Triangles, and More: Understanding Microservices

Oracle Code Sydney - There is no such thing as a microservice!

Decompose That WAR! Architecting for Adaptability, Scalability, and Deployabi...

Introduction to MicroServices (Oakjug)

RedisConf17 - A pattern language for microservices - Chris Richardson

YOW! Perth: Cubes, Hexagons, Triangles, and More: Understanding the Microserv...

A pattern language for microservices - June 2021

TDC2020 - The microservice architecture: enabling rapid, reliable, frequent a...

Más de Chris Richardson

The microservice architecture: what, why, when and how?

Chris Richardson

A common microservice architecture anti-pattern is more the merrier. It occurs when an organization team builds an excessively fine-grained architecture, e.g. one service-per-developer. In this talk, you will learn about the criteria that you should consider when deciding service granularity. I'll discuss the downsides of a fine-grained microservice architecture. You will learn how sometimes the solution to a design problem is simply a JAR file.

More the merrier: a microservices anti-pattern

Chris Richardson

This is a talk I gave at YOW! London 2022. Let's imagine that you are responsible for an aging monolithic application that's critical to your business. Sadly, getting changes into production is a painful ordeal that regularly causes outages. And to make matters worse, the application's technology stack is growing increasingly obsolete. Neither the business nor the developers are happy. You need to modernize your application and have read about the benefits of microservices. But is the microservice architecture a good choice for your application? In this presentation, I describe the dark energy and dark matter forces (a.k.a. concerns) that you must consider when deciding between the monolithic and microservice architectural styles. You will learn about how well each architectural style resolves each of these forces. I describe how to evaluate the relative importance of each of these forces to your application. You will learn how to use the results of this evaluation to decide whether to migrate to the microservice architecture.

YOW London - Considering Migrating a Monolith to Microservices? A Dark Energy...

Chris Richardson

Dark matter and dark energy are mysterious concepts from astrophysics that are used to explain observations of distant stars and galaxies. The Microservices pattern language - a collection of patterns that solve architecture, design, development, and operational problems — enables software developers to use the microservice architecture effectively. But how could there possibly be a connection between microservices and these esoteric concepts from astrophysics? In this presentation, I describe how dark energy and dark matter are excellent metaphors for the competing forces (a.k.a. concerns) that must be resolved by the microservices pattern language. You will learn that dark energy, which is an anti-gravity, is a metaphor for the repulsive forces that encourage decomposition into services. I describe how dark matter, which is an invisible matter that has a gravitational effect, is a metaphor for the attractive forces that resist decomposition and encourage the use of a monolithic architecture. You will learn how to use the dark energy and dark matter forces as guide when designing services and operations.

Dark Energy, Dark Matter and the Microservices Patterns?!

Chris Richardson

Dark energy and dark matter are useful metaphors for the repulsive forces, which encourage decomposition into services, and the attractive forces, which resist decomposition. You must balance these conflicting forces when defining a microservice architecture including when designing system operations (a.k.a. requests) that span services. In this talk, I describe the dark energy and dark matter forces. You will learn how to design system operations that span services using microservice architecture collaboration patterns: Saga, Command-side replica, API composition, and CQRS patterns. I describe how each of these patterns resolve the dark energy and dark matter forces differently.

Dark energy, dark matter and microservice architecture collaboration patterns

Chris Richardson

It sounds dull but good architecture documentation is essential. Especially when you are actively trying to improve your architecture. For example, I spend a lot time helping clients modernize their software architecture. More often than I like, I’m presented with a vague and lifeless collection of boxes and lines. As a result, it’s sometimes difficult to discuss the architecture in a meaningful and productive way. In this presentation, I’ll describe techniques for creating minimal yet effective documentation for your application’s microservice architecture. In particular, you will learn how documenting scenarios can bring your architecture to life.

Scenarios_and_Architecture_SkillsMatter_April_2022.pdf

Chris Richardson

This is a presentation that gave at the O'Reilly Software Architecture Superstream: Software Architecture Patterns. The talk's focus is the microservices pattern language. However, it also shows how thinking with the pattern mindset - context/problem/forces/solution/consequences - leads to better technically decisions. The microservices architecture offers tremendous benefits, but it’s not a silver bullet. It also has some significant drawbacks. The microservices pattern language—a collection of patterns that solve architecture, design, development, and operational problems—enables software developers to apply the microservices architecture effectively. I provide an overview of the microservices architecture and examines the motivations for the pattern language, then takes you through the key patterns in the pattern language.

Using patterns and pattern languages to make better architectural decisions

Chris Richardson

Rapid, reliable, frequent and sustainable software development requires an architecture that is loosely coupled and modular. Teams need to be able complete their work with minimal coordination and communication with other teams. They also need to be able keep the software’s technology stack up to date. However, the microservice architecture isn’t always the only way to satisfy these requirements. Yet, neither is the monolithic architecture. In this talk, I describe loose coupling and modularity and why they are is essential. You will learn about three architectural patterns: traditional monolith, modular monolith and microservices. I describe the benefits, drawbacks and issues of each pattern and how well it supports rapid, reliable, frequent and sustainable development. You will learn some heuristics for selecting the appropriate pattern for your application.

iSAQB gathering 2021 keynote - Architectural patterns for rapid, reliable, fr...

Chris Richardson

Delivering large, complex software rapidly, frequently and reliably requires a loosely coupled organization. DevOps teams should rarely need to communicate and coordinate in order to get work done. Conway's law states that an organization and the architecture that it develops mirror one another. Hence, a loosely coupled organization requires a loosely coupled architecture. In this presentation, you will learn about design-time coupling in a microservice architecture and why it's essential to minimize it. I describe how to design service APIs to reduce coupling. You will learn how to minimize design-time coupling by applying a version of the DRY principle. I describe how key microservices patterns potentially result in tight design time coupling and how to avoid it.

QConPlus 2021: Minimizing Design Time Coupling in a Microservice Architecture

Chris Richardson

In order to explain certain astronomical observations, physicists created the mysterious concepts of dark energy and dark matter. Dark energy is a repulsive force. It’s an anti-gravity that is forcing matter apart and accelerating the expansion of the universe. Dark matter has the opposite attraction effect. Although it’s invisible, dark matter has a gravitational effect on stars and galaxies. In this presentation, you will learn how these metaphors apply to the microservice architecture. I describe how there are multiple repulsive forces that drive the decomposition of your application into services. You will learn, however, that there are also multiple attractive forces that resist decomposition and bind software elements together. I describe how as an architect you must find a way to balance these opposing forces.

Mucon 2021 - Dark energy, dark matter: imperfect metaphors for designing micr...

Chris Richardson

Skillsmatter CloudNative eXchange 2020 The microservice architecture is a key part of cloud native. An essential principle of the microservice architecture is loose coupling. If you ignore this principle and develop tightly coupled services the result will mostly likely be yet another "microservices failure story”. Your application will be brittle and have all of disadvantages of both the monolithic and microservice architectures. In this talk you will learn about the different kinds of coupling and how to design loosely coupled microservices. I describe how to minimize design time and increase the productivity of your DevOps teams. You will learn how how to reduce runtime coupling and improve availability. I describe how to improve availability by minimizing the coupling caused by your infrastructure.

Designing loosely coupled services

Chris Richardson

Microservices - an architecture that enables DevOps (T Systems DevOps day)

Chris Richardson

DDD SoCal: Decompose your monolith: Ten principles for refactoring a monolith...

Chris Richardson

Decompose your monolith: Six principles for refactoring a monolith to microse...

Chris Richardson

Overview of the Eventuate Tram Customers and Orders application

Chris Richardson

#DevNexus202 Decompose your monolith

Chris Richardson

This is a presentation that I gave at Tide.co, London - January 2020 A typical mission-critical enterprise application is a large, complex monolith developed by large team. Software delivery is usually slow, and the team struggles to keep up with the demands of the business. Consequently, many enterprise applications are good candidates to be migrated to the microservice architecture. But how do you know whether it makes sense to migrate to microservices? And, how to get there? In this presentation, I describe when you should consider migrating to microservices. You will learn strategies for migrating a monolith application to a microservice architecture. I explain how to implement new functionality as services. You will learn how to incrementally break apart a monolith one service at a time.

Decompose your monolith: strategies for migrating to microservices (Tide)

Chris Richardson

The primary goal of the microservice architecture is to enable the rapid, reliable delivery of software with DevOps. One of the pillars of DevOps is automated testing, yet many organizations attempt to adopt microservices while still doing manual testing. What’s more, the microservice architecture has its own distinctive automated testing challenges. This presentation describes how to descend the testing pyramid and replace slow, brittle, end-to-end tests with faster, more reliable tests for individual services. You will learn how to write tests that ensure that service APIs evolve while preserving backward compatibility. You’ll learn how, by running these tests in a deployment pipeline, you will fully benefit from microservices.

Oracle CodeOne 2019: Descending the Testing Pyramid: Effective Testing Strate...

Chris Richardson

A typical mission-critical enterprise application is a large, complex monolith developed by a large team. Software delivery is usually slow, and the team struggles to keep up with the demands of the business. Consequently, many enterprise applications are good candidates to be migrated to the microservice architecture. But how do you know whether it makes sense to migrate to microservices and how to get there? This session describes when you should consider migrating to microservices. You will learn strategies for migrating a monolith application to a microservice architecture. The presentation explains how to implement new functionality as services, and you will also learn how to incrementally break apart a monolith, one service at a time.

Oracle CodeOne 2019: Decompose Your Monolith: Strategies for Migrating to Mic...

Chris Richardson

The services in a microservice architecture must be loosely coupled and so cannot share database tables. What’s more, two-phase commit (aka a distributed transaction) is not a viable option for modern applications. Consequently, a microservices application must use the Saga pattern, which maintains data consistency using a series of local transactions. In this presentation, you will learn how sagas work and how they differ from traditional transactions. We describe how to use sagas to develop business logic in a microservices application. You will learn effective techniques for orchestrating sagas and how to use messaging for reliability. We will describe the design of a saga framework for Java and show a sample application.

MicroCPH - Managing data consistency in a microservice architecture using Sagas

Chris Richardson

Más de Chris Richardson (20)

The microservice architecture: what, why, when and how?

More the merrier: a microservices anti-pattern

YOW London - Considering Migrating a Monolith to Microservices? A Dark Energy...

Dark Energy, Dark Matter and the Microservices Patterns?!

Dark energy, dark matter and microservice architecture collaboration patterns

Scenarios_and_Architecture_SkillsMatter_April_2022.pdf

Using patterns and pattern languages to make better architectural decisions

iSAQB gathering 2021 keynote - Architectural patterns for rapid, reliable, fr...

QConPlus 2021: Minimizing Design Time Coupling in a Microservice Architecture

Mucon 2021 - Dark energy, dark matter: imperfect metaphors for designing micr...

Designing loosely coupled services

Microservices - an architecture that enables DevOps (T Systems DevOps day)

DDD SoCal: Decompose your monolith: Ten principles for refactoring a monolith...

Decompose your monolith: Six principles for refactoring a monolith to microse...

Overview of the Eventuate Tram Customers and Orders application

#DevNexus202 Decompose your monolith

Decompose your monolith: strategies for migrating to microservices (Tide)

Oracle CodeOne 2019: Descending the Testing Pyramid: Effective Testing Strate...

Oracle CodeOne 2019: Decompose Your Monolith: Strategies for Migrating to Mic...

MicroCPH - Managing data consistency in a microservice architecture using Sagas

Último

%in Soweto+277-882-255-28 abortion pills for sale in soweto

masabamasaba

Define the academic and professional writing..pdf

PearlKirahMaeRagusta1

We specialize in Psychic Readings, Psychic Love Spells, Binding Love Spells, Obsession Spells, Voodoo Spells, Lottery Spells, Marriage Spells, Black Magic Spells, Palm Readings & much more. Are you depressed? We perform this come-to-me love spell that works instantly with the aim of Winnipeg back the victim to the person performing the magic. Have you lost your lover? We perform this come-to-me love spell that works instantly with the aim of bringing back the victim to the person performing the magic. Have you lost your lover? Do u need to solve any relationship problem? Contact the powerful spells caster chief kule with love spells that work overnight and love spells that really work. Have you found yourself infatuated with a special someone you think could be the one? Are you looking for a spell to provide them with a nudge in the right direction? Or maybe the spell you cast didn’t achieve the results you were hoping for? Whether you’re new or versed in the ways of spell casting, we’re here to help. Today we’re going to provide you with a detailed guide on the types of love spells to cast. Not only that but there’s something for those who wish to find outside advice from more advanced spell casters. We’re also going to provide you with the top sites available to help you with your dilemma. Let’s begin our journey by educating ourselves on love magic and what a real love caster looks like. Love Magic and Love Casters Love magic made its first appearance back in Ancient Egypt and has been an active practice since. This type of magic is a branch of traditional magic and can be practiced in various ways. Typically the more common use of love magic is through the work of spells, but other methods look like Charms Rituals-LOVE Potions-Dolls and even Amulets If you are interested in becoming a love caster, be prepared for what’s to come. A genuine love caster knows that the art of love casting is no easy feat and shouldn’t be done casually. You should know that not only does it require you to be gifted spiritually, but you must be ready to serve others. Someone who is considered a real love caster has experience in all manner of spells, no matter the difficulty. Training yourself in attraction, commitment, and marriage spells is an excellent place to start. But this by no means will make you a professional. Practice your craft and expand your knowledge; understand that you will possess the ability to help others in time truly. Types of Love Spells What better way to start broadening your experiences with love spells than by learning more about them? These spells work like just about any other spell. Simply apply your intention, use a medium (sigils, mantras, candles, or charm bags), and top it off with establishing the belief that you will receive what you want. So what kind of spells are available and which ones suit your needs the best? Let’s take a look at the many options you have at your disposal. Attraction Spells

%+27788225528 love spells in Huntington Beach Psychic Readings, Attraction sp...

masabamasaba

Devoxx UK 2024 - Going serverless with Quarkus, GraalVM native images and AWS...

Bert Jan Schrijver

WSO2CON2024 - It's time to go Platformless

WSO2

In today's dynamic e-commerce landscape, the payment gateway emerges as a linchpin, ensuring smooth and secure transactions between buyers and sellers. In this discourse, we delve into the meticulous process of devising test cases tailored for scrutinizing payment gateways. Crafting precise test cases for payment gateways is a quintessential responsibility for testers operating within the service industry. This article meticulously explores pivotal scenarios integral to how to test payment gateways, coupled with essential guidelines for drafting effective test cases.

Payment Gateway Testing Simplified_ A Step-by-Step Guide for Beginners.pdf

kalichargn70th171

This presentation covers the following topics: What is logging? The purpose of logging: Debugging The purpose of logging: Security The purpose of logging: Stats & analytics Traditional logging Traditional logging: Advantages Traditional logging: Disadvantages The solution: Large-scale logging Large-scale logging: Core principles Large-scale logging: Solution types Large-scale logging: Cloud vs on-prem Large-scale logging: Operational complexity Large-scale logging: Security Large-scale logging: Costs Large-scale logging: On-prem comparison - Elasticsearch - Grafana Loki - VictoriaLogs On-prem comparison: Setup and operation On-prem comparison: Costs On-prem comparison: Full-text search support On-prem comparison: How to efficiently query 100TB of logs? On-prem comparison: Integration with CLI tools VictoriaLogs for large-scale logging VictoriaLogs demo instance - Ingestion rate: 3600 messages / minute - The number of log messages: 1.1 billion - Uncompressed log messages’ size: 1.5TB - Compressed log messages’ size: 23GB - Compression ratio: 47x - Memory usage: 150MB VictoriaLogs CLI integration demo - Which errors have occurred in all the apps during the last hour? - How many errors have occurred during the last hour? - Which apps generated the most of errors during the last hour? - The number of per-minute errors for the last 10 minutes - Status codes for the last hour - Non-200 status codes for the last week - Top client IPs for the last 4 weeks with 404 and 500 response status codes - Per-month stats for the given IP across all the logs Large-scale logging solution MUST provide excellent CLI integration VictoriaLogs: (temporary) drawbacks VictoriaLogs: Recap - Easy to setup and operate - The lowest RAM usage and disk space usage (up to 30x less than Elasticsearch and Grafana Loki) - Fast full-text search - Excellent integration with traditional command-line tools for log analysis - Accepts logs from popular log shippers (Filebeat, Fluentbit, Logstash, Vector, Promtail, Grafana Agent) - Open source and free to use!

Large-scale Logging Made Easy: Meetup at Deutsche Bank 2024

VictoriaMetrics

%in kempton park+277-882-255-28 abortion pills for sale in kempton park

masabamasaba

%in Midrand+277-882-255-28 abortion pills for sale in midrand

masabamasaba

WSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital Transformation

WSO2

MarTech Trend 2024 Book : Marketing Technology Trends (2024 Edition) How Data...

Jittipong Loespradit

%in Harare+277-882-255-28 abortion pills for sale in Harare

masabamasaba

%in Hazyview+277-882-255-28 abortion pills for sale in Hazyview

masabamasaba

Announcing Codolex 2.0 from GDK Software

Jim McKeeth

Investing in AI transformation today The modern business advantage: Uncovering deep insights with AI Organizations around the world have come to recognize AI as the transformative technology that enables them to gain real business advantage. AI’s ability to organize vast quantities of data allows those who implement it to uncover deep business insights, augment human expertise, drive operational efficiency, transform their products, and better serve their customers

Microsoft AI Transformation Partner Playbook.pdf

Willy Marroquin (WillyDevNET)

Abortion Pill Prices Tembisa [(+27832195400*)] 🏥 Women's Abortion Clinic in Tembisa ● Abortion Pills For Sale in Tembisa ● Tembisa 🏥🚑!! Abortion Clinic Near Me Cost, Price, Women's Clinic Near Me, Abortion Clinic Near, Abortion Doctors Near me, Abortion Services Near Me, Abortion Pills Over The Counter, Abortion Pill Doctors' Offices, Abortion Clinics, Abortion Places Near Me, Cheap Abortion Places Near Me, Medical Abortion & Surgical Abortion, approved cyctotec pills and womb cleaning pills too plus all the instructions needed This Discrete women’s Termination Clinic offers same day services that are safe and pain free, we use approved pills and we clean the womb so that no side effects are present. Our main goal is that of preventing unintended pregnancies and unwanted births every day to enable more women to have children by choice, not chance. We offer Terminations by Pill and The Morning After Pill.” Our Private VIP Abortion Service offers the ultimate in privacy, efficiency and discretion. we do safe and same day termination and we do also womb cleaning as well its done from 1 week up to 28 weeks. We do delivery of our services world wide SAFE ABORTION CLINICS/PILLS ON SALE WE DO DELIVERY OF PILLS ALSO Abortion clinic at very low costs, 100% Guaranteed and it’s safe, pain free and a same day service. It Is A 45 Minutes Procedure, we use tested abortion pills and we do womb cleaning as well. Alternatively the medical abortion pill and womb cleansing !!!

Abortion Pill Prices Tembisa [(+27832195400*)] 🏥 Women's Abortion Clinic in T...

Medical / Health Care (+971588192166) Mifepristone and Misoprostol tablets 200mg

WSO2CON 2024 - Cloud Native Middleware: Domain-Driven Design, Cell-Based Arch...

WSO2

WSO2Con2024 - Enabling Transactional System's Exponential Growth With Simplicity

WSO2

%in tembisa+277-882-255-28 abortion pills for sale in tembisa

masabamasaba

Direct Style Effect Systems -The Print[A] Example- A Comprehension Aid

Philip Schwarz

Microservices and Redis #redisconf Keynote

1. Microservices and Redis Chris Richardson Founder of Eventuate.io Founder of the original CloudFoundry.com Author of POJOs in Action @crichardson chris@chrisrichardson.net http://eventuate.io

2. @crichardson About Chris

3. @crichardson Why microservices?

4. @crichardson The monolithic architecture Tomcat Browser WAR SQL database HTML REST/JSON Client App Simple to …. Develop Test Deploy Scale Catalog Module Reviews Module Orders Module StoreFront UI Module

5. @crichardson But successful applications keep growing …. Eventually, agile development and deployment becomes impossible

6. @crichardson Microservice architecture = functional decomposition Browser Mobile Device Store Front UI API Gateway Catalog Service Review Service Order Service … Service Catalog Database Review Database Order Database … Database HTML REST REST

7. @crichardson Develop and deploy faster

8. @crichardson Scale more easily

9. @crichardson Pick the best technology

10. @crichardson Microservices are not a free lunch BUT for most large, complex applications are good choice

11. @crichardson Where does Redis ﬁt in?

12. Using Redis within a service Caching High performance messaging High performance database Catalog Service Catalog DB

13. @crichardson Using Redis for inter-service communication API Gateway Catalog Service Review Service … Service Pub/Sub Need Product Details X GET /product/X Need … Need … Need …Info Info Info

14. @crichardson Redis and the API Gateway API Gateway Caching Rate limiting Routing

15. @crichardson How to maintain data consistency?

16. @crichardson Database per service Catalog Service Review Service Order Service … Service Catalog Database Review Database Order Database … Database How to maintain data consistency without 2PC?

17. @crichardson Customer DB How to maintain data consistency without 2PC? Order DB Order Service placeOrder() Customer Service updateCreditLimit() Customer creditLimit ... has ordersbelongs toOrder total Invariant: sum(open order.total) <= customer.creditLimit ?

18. @crichardson Use event-driven, eventually consistent order processing Order Service Customer Service Order created Credit Reserved Credit Check Failed Place Order OR

19. @crichardson How to atomically update database and publish an event without 2PC? Order Service Order Database Message Broker insert Order publish OrderCreatedEvent dual write problem ?

20. @crichardson Use event sourcing Order Service Order Database Event Store insert Order Save OrderCreatedEvent X Persistence and notiﬁcation

21. @crichardson Event sourcing: persists events NOT current state Event table Entity type Event id Entity id Event data Order 902101 …OrderApproved Order 903101 …OrderShipped Event type Order 901101 …OrderCreated Order state total Replay

22. @crichardson How to implement queries?

23. @crichardson Find recent, valuable customers SELECT * FROM CUSTOMER c, ORDER o WHERE c.id = o.ID AND o.ORDER_TOTAL > 100000 AND o.STATE = 'SHIPPED' AND c.CREATION_DATE > ? Customer Service Order Service What if event sourcing is used? …. is no longer easy

24. @crichardson Command Query Responsibility Segregation (CQRS) Command side Commands Aggregate Event Store Events Query side Queries Materialized View Events POST PUT DELETE GET

25. @crichardson Food to Go example - on github.com http://bit.ly/redis-pia 94619:Monday [0700_2:1430, 1130_1:1430, ...] 94619:Tuesday [0700_2:1430, 1130_1:1430, ...] … … Restaurant View Updater Service Restaurant View Query Service ZRANGEBYSCORE Event Store Restaurant events Materialized view of restaurant locations and opening hours GET available restaurants ZADD ZREM Sorted sets

26. @crichardson Summary Organize into small, agile, autonomous teams responsible for one or more microservices Use an event-driven architecture, based on event sourcing and CQRS Use Redis throughout a microservices architecture

27. Thank you! @crichardson http://eventuate.io

Microservices and Redis #redisconf Keynote

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Destacado

Destacado (6)

Similar a Microservices and Redis #redisconf Keynote

Similar a Microservices and Redis #redisconf Keynote (20)

Más de Chris Richardson

Más de Chris Richardson (20)

Último

Último (20)

Microservices and Redis #redisconf Keynote