CQRS without event sourcing

An introduction to CQRS (without Event Sourcing) made at MS experiences days in Paris (and translated in english)

The Pareto
Principle
80-20
Root cause
0%0%
80%
reading
20%
writing

…only one central
component to deal
with a wide range
of constraints.
With…

Do you have those constraints in mind
while designing your architectures?
A question
(for you)

How to optimize an app that has to scale
for massive read accesses?
So…

CQRS splits the 80s and the 20s
20 % of time
80 % of time

C
Q
R
S
Behind the acronym
( powered by Greg YOUNG - @gregyoung )

Command
Query
Responsibility
Segregation
Behind the acronym

Classical
transactional
databases
RDBMS
(ACID)
« ready-to-eat
data », Caches,
non-normalized
models,
(no SQL)
CQRS illustrated

Command
TRIGGERS AN ACTION
Modify the state of the system
>> Don’t return data ! <<
Imperative Verb
Ex: BookARoom
Query
ASKS FOR AN INFORMATION
Read-only!
Get back data
Imperative Verb
Ex: GetAvailableRooms
Event
ALREADY HAPPENED
(Immutable)
Past-tense
Ex: RoomBooked

Open Source Implementation available on GitHub
2 main parts:
CoreClr (Runtime execution) (C++)
CoreFx (including classes, collections, file systems, xml, etc.) (C#)
ASP.NET Core 1.0 framework relies on it
Classic deployment or
Container deployment (Linux or Windows)
.NET Core
// Licensed to the .NET Foundation under one or more agreements.

…a top-level architecture pattern
Use it for components under stress
Do not generalize its usage for all the components of your platform!
CQRS is not…

CQRS Event Sourcing
but
CQRS != Event Sourcing

Well-separated read and write concerns
CQRS is mostly
Queries
Caches, Ready-
to-eat data
(no SQL)
Commands
Transactionnal
ACID

Merci aussi à Rui CARVALHO, Mendel MONTEIRO-BECKERMAN,
Olivier COANET et Clément BOUDEREAU ainsi que Greg YOUNG
pour leurs feedbacks et idées pour ce talk.

Wanna play the lab @home?
Follow the white rabbit here:
https://github.com/tpierrain/CQRS/blob/master/LabInstructions.
md

@microsoftfrance @Technet_France @msdev_fr
@tpierrain @brunoboucard @tjaskula @EricVernie

What's hot

AWS Summit Seoul 2023 | 실시간 CDC 데이터 처리! Modern Transactional Data Lake 구축하기

AWS Cloud 환경으로 DB Migration 전략 수립하기

BESPIN GLOBAL

Tracxn - Database Technology Startup Landscape

Tracxn

The document provides an overview of the database technology sector, including key metrics and subsectors. It summarizes funding trends, notable companies, and recent news. The sector has seen $3.9B in funding for 1424 companies. Top subsectors are NoSQL, relational databases, and in-memory databases. Major public companies include Oracle, MongoDB, and Progress, while unicorns include Snowflake and Yellowbrick Data.

쿠버네티스를 이용한 기능 브랜치별 테스트 서버 만들기 (GitOps CI/CD)

충섭 김

Microservices Testing Strategies JUnit Cucumber Mockito Pact

Araf Karsh Hamid

Microservices for Application Modernisation

Ajay Kumar Uppal

Elastic-Engineering

Araf Karsh Hamid

Agile, User Stories, Domain Driven Design

Araf Karsh Hamid

Google cloud-platform-official-icons-and-sample-diagrams

Dhamotharan Paramasivam

This document provides guidance and assets for creating Google Cloud Platform (GCP) architectural diagrams. It includes examples of diagram elements like user cards, product cards, zones, and expanded product cards. Specifications are given for formatting zones, titles, and other elements. Icons for GCP products, services, and Material Design are also referenced. The goal is to help users accurately diagram GCP architectures in a consistent visual style.

Terraform modules restructured

Ami Mahloof

AWS 기반 대규모 트래픽 견디기 - 장준엽 (구로디지털 모임) :: AWS Community Day 2017

AWSKRUG - AWS한국사용자모임

AWS Summit Seoul 2015 - 국내 사례로 본 클라우드 운영 최적화 (이주완-메가존)

Monoliths and Microservices

Bozhidar Bozhanov

Saturn 2018: Managing data consistency in a microservice architecture using S...

A revised and extended version that I gave at Saturn 2018. 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.

[AWS Dev Day] 앱 현대화 | 코드 기반 인프라(IaC)를 활용한 현대 애플리케이션 개발 가속화, 우리도 할 수 있어요 - 김필중...

현대의 애플리케이션 개발은 비지니스 요구사항을 빠르게 수용하여 구현한 뒤, 피드백을 통해 개선하는 과정을 지속적으로 반복해야 합니다. 본 세션에서는 AWS가 제공하는 코드 기반 인프라(Infrastructure as Code) 관련 도구를 활용하여 현대의 애플리케이션 개발을 위한 더 나은 환경을 어떻게 구성하며, 어떤 이점이 있는지 소개합니다. 기업에서 적용한 실제 사례를 통해 보다 더 직접적인 활용법을 확인할 수 있습니다. 기업에서 적용한 실제 사례를 통해 보다 더 직접적인 활용법은 물론, 조직에 필요한 변화 부터 환경 구성, 개발 진행, 변화 수용에 대해서 알 수 있습니다.

Developing event-driven microservices with event sourcing and CQRS (svcc, sv...

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 Segregation (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.

Microservices Architectures on Amazon Web Services

Amazon Web Services

TechEvent Infrastructure as Code on Azure

Trivadis

This document provides an overview of Infrastructure as Code (IaC) on Azure using ARM templates and Terraform. It discusses the benefits of IaC for consistency, version control, and faster deployments. ARM templates are the native Microsoft solution for Azure resources defined in JSON, while Terraform uses a declarative language and manages dependencies automatically. Both tools were compared, with ARM templates having better integration with Azure services and security features, while Terraform excels with its plan preview and dependency management. Advanced IaC concepts like environments and centralized repositories were also covered.

DevOps on AWS

Amazon Web Services

This document provides an overview of DevOps on AWS and the AWS developer tools for continuous delivery including CodeCommit, CodeDeploy, CodePipeline, and Elastic Beanstalk. It discusses how these tools help implement a microservices architecture and continuous delivery approach to software development. Specifically, it describes how CodeCommit provides version control, CodeDeploy enables easy and reliable deployments, CodePipeline allows connecting tools for accelerated release processes, and Elastic Beanstalk provides a simple way to deploy applications.

Internal Architecture of Amazon Aurora (Level 400) - 발표자: 정달영, APAC RDS Speci...

ccAmazon Aurora 데이터베이스는 클라우드용으로 구축된 관계형 데이터베이스입니다. Aurora는 상용 데이터베이스의 성능과 가용성, 그리고 오픈소스 데이터베이스의 단순성과 비용 효율성을 모두 제공합니다. 이 세션은 Aurora의 고급 사용자들을 위한 세션으로써 Aurora의 내부 구조와 성능 최적화에 대해 알아봅니다.

What's hot (20)

AWS Summit Seoul 2023 | 실시간 CDC 데이터 처리! Modern Transactional Data Lake 구축하기

AWS Cloud 환경으로 DB Migration 전략 수립하기

Tracxn - Database Technology Startup Landscape

쿠버네티스를 이용한 기능 브랜치별 테스트 서버 만들기 (GitOps CI/CD)

Microservices Testing Strategies JUnit Cucumber Mockito Pact

Microservices for Application Modernisation

Elastic-Engineering

Agile, User Stories, Domain Driven Design

Google cloud-platform-official-icons-and-sample-diagrams

Terraform modules restructured

AWS 기반 대규모 트래픽 견디기 - 장준엽 (구로디지털 모임) :: AWS Community Day 2017

AWS Summit Seoul 2015 - 국내 사례로 본 클라우드 운영 최적화 (이주완-메가존)

Monoliths and Microservices

Saturn 2018: Managing data consistency in a microservice architecture using S...

[AWS Dev Day] 앱 현대화 | 코드 기반 인프라(IaC)를 활용한 현대 애플리케이션 개발 가속화, 우리도 할 수 있어요 - 김필중...

Developing event-driven microservices with event sourcing and CQRS (svcc, sv...

Microservices Architectures on Amazon Web Services

TechEvent Infrastructure as Code on Azure

DevOps on AWS

Internal Architecture of Amazon Aurora (Level 400) - 발표자: 정달영, APAC RDS Speci...

Viewers also liked

The art of Software Design

Software Design ... a nice expression, uh? But what does it mean to "design a software"? What are the prerequisites? What are the pitfalls to avoid? As Software Designers we would like to highlight on what makes us build simple, useful and above all effective software. And of course, we will talk about Domain-Driven Design in that journey ;-) Talk made at http://domain-driven-design.eu/the-art-of-design/

CQRS на практике. В поиске точки масштабирования и новых метафор

Alexander Byndyu

Ddd reboot (english version)

Culture craft humantalks

Avez-vous déjà eu l'impression de vous être assoupis dans votre carrière, de faire moins de veille qu'à d'autres périodes ? A l'inverse, vous êtes-vous déjà demandé comment sortir du ronron ambiant et "réveiller" vos collègues qui vous semblaient manquer de curiosité et de passion sur un projet ? Cette courte session vise à vous présenter toutes les formules et astuces qui ont permis à très peu de gens chez nous de réveiller une grosse organisation qui s'endormait sur ses lauriers. Si on a réussi ici -sandwichs à la main- pourquoi pas vous ? Attention: effet contagieux ;-)

Faible latence haut debit Devoxx FR 2014

Comment concevoir des systèmes capables d’encaisser des dizaines de milliers d’updates par seconde sans s’engorger, ni dépasser la milli seconde de traitement ? Comment écrire du code scalable qui reste lisible –mais garanti 100% sans deadlock ? Que recouvre le reactive manifesto et les termes : conflation, sequencer, immutable state ? Après vous avoir présenté les besoins et contraintes du trading électronique, nous répondrons à toutes ces questions dans une session qui s'annonce...technique.

Decouvrir CQRS (sans Event sourcing) par la pratique

Async await...oh wait!

The document discusses async-await in C# and how it works under the hood. It begins with questions about what happens when await is used. It then explains that async-await is used to compose asynchronous code using task continuations generated by the compiler. It discusses how await marks a continuation and depends on the context to determine threading. Windows I/O is used as an example of asynchronous operations without threads. The document concludes with recommendations to avoid deadlocks by not blocking on async code and to only use async-void for event handlers.

TDD is dead?!? Let's do an autospy (ncrafts.io)

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

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.

Windows Containers and Docker: Why You Should Care

Elton Stoneman

Decouvrir son sujet grace à l'event storming

Ulili Emerson Martins Nhaga

.NET Inside - Microservices, .NET Core e Serverless

Coder sans peur du changement avec la meme pas mal hexagonal architecture

Découvrez en pratique l'architecture hexagonale, indispensable pour vos applications complexes ! Ce style d'architecture permet d'adapter votre code à tout changement de technologie sans souffrir. Si vous aimez changer de frameworks ou de librairies, tester correctement ou appliquer le Domain-Driven Design, alors vous avez besoin d'architecture hexagonale ! Avec des exemples en code Java, et au travers d’un kata d’architecture auquel vous pourrez participer, nous vous montrerons les pièges à éviter et comment mettre en œuvre ce pattern sans trop galérer, et ce dès votre retour au bureau !

The Velvet Revolution: Modernizing Traditional ASP.NET Apps with Docker

Elton Stoneman

.Net Microservices with Event Sourcing, CQRS, Docker and... Windows Server 20...

Javier García Magna

Faible latence, haut debit PerfUG (Septembre 2014)

vidéo disponible : http://tv.octo.com/videos/les-secrets-de-la-finance-pour-avoir-des-systemes-reactifs/ Comment concevoir des systèmes capables d’encaisser des dizaines de milliers d’updates par seconde sans s’engorger, ni dépasser la milli seconde de traitement ? Comment écrire du code scalable qui reste lisible –mais garanti 100% sans deadlock ? Que recouvre le reactive manifesto ? et les termes : conflation, sequencer, immutable state ? Après vous avoir présenté les besoins et contraintes du trading électronique, nous répondrons à toutes ces questions dans une session … résolument réactive. Note: il s'agit de la présentation que nous avions faîte à DEVOXX France en Avril 2014, mais revue et corrigée pour notre session au PerfUG de Septembre (avec une nouvelle charte graphique donc)

Sortir de notre zone de confort

The document discusses the need for developers to move outside their comfort zone and connect more with business needs. It notes that developers often get stuck creating generic CRUD applications instead of domain-specific solutions because of data modeling over domain modeling, laziness, and isolation from business partners. The document argues that to have more impact, developers should make more effort to understand business problems, accompany partners to help explain technology's benefits, and focus on delivering business value rather than just technical skills. Developers are encouraged to be curious, think outside the box, and work to bridge the gap between development and business concerns.

Docker and Windows: The State of the Union

Elton Stoneman

Solving distributed data management problems in a microservice architecture (...

The document discusses challenges of maintaining data consistency and performing queries in a microservices architecture. It recommends using sagas and compensating transactions to maintain consistency across services with private databases. For queries, it recommends API composition when possible, but for more complex queries, using the Command Query Responsibility Segregation (CQRS) pattern with separate read models optimized for different query types. The talk also covers event sourcing to provide reliable saga execution.

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

This document discusses building and deploying microservices using event sourcing, CQRS and Docker. It covers an overview of event sourcing and how it solves data consistency issues in microservice architectures. CQRS is used to implement materialized views for queries. Spring Boot is recommended for building microservices and Docker is used to package the microservices. A continuous integration pipeline is used to build, test, publish Docker images and deploy updates.

Viewers also liked (20)

The art of Software Design

CQRS на практике. В поиске точки масштабирования и новых метафор

Ddd reboot (english version)

Culture craft humantalks

Faible latence haut debit Devoxx FR 2014

Decouvrir CQRS (sans Event sourcing) par la pratique

Async await...oh wait!

TDD is dead?!? Let's do an autospy (ncrafts.io)

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

Windows Containers and Docker: Why You Should Care

Decouvrir son sujet grace à l'event storming

.NET Inside - Microservices, .NET Core e Serverless

Coder sans peur du changement avec la meme pas mal hexagonal architecture

The Velvet Revolution: Modernizing Traditional ASP.NET Apps with Docker

.Net Microservices with Event Sourcing, CQRS, Docker and... Windows Server 20...

Faible latence, haut debit PerfUG (Septembre 2014)

Sortir de notre zone de confort

Docker and Windows: The State of the Union

Solving distributed data management problems in a microservice architecture (...

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

Similar to CQRS without event sourcing

CQRS & Queue unlimited

Tim Mahy

This document provides an introduction to CQRS (Command Query Responsibility Segregation) patterns and QueueUnlimited concepts and implementation. It discusses why CQRS is needed to separate queries from commands in distributed systems. QueueUnlimited is an open source project that uses SQL Server Service Broker to implement an asynchronous queue-based data store for CQRS. It allows publishing and subscribing to commands and queries across services. The document demonstrates how QueueUnlimited works and provides advantages and disadvantages of the CQRS pattern.

Software Architecture Conference - Monitoring Microservices - A Challenge

Adrian Cockcroft

The document discusses the challenges of monitoring microservices architectures. It notes that microservices are deployed much more frequently than traditional applications, sometimes in seconds or milliseconds. This rapid deployment rate requires monitoring tools that can measure and report metrics at an equally fast pace. It also explains that microservices architectures involve large numbers of loosely coupled services distributed across multiple regions, zones, and instances. Monitoring tools must be able to handle the scale and complexity of these distributed systems. Other challenges discussed include visualizing request flows, understanding common failure scenarios, and testing monitoring systems at a large scale. The document advocates for using simulations to model microservices architectures and stress test monitoring tools to help address these challenges.

Stuff About CQRS

thinkddd

This document discusses Command Query Responsibility Segregation (CQRS). It begins by explaining that CQRS splits commands and queries into separate paths at an architectural level. This aligns with how people think about tasks (commands) and requesting information (queries) differently. The document then discusses how CQRS provides an eventually consistent architecture based on CAP theorem, similar to BASE. It explains that CQRS reads data from a separate read model than where commands write to the domain model. In summary, CQRS separates commands from queries in a way that matches how people think, and provides an eventually consistent architecture.

Awesome Tools to Level Up Your Spring Cloud Architecture - Spring I/O 2017

Andreas Evers

CQRS: A More Effective Way of Writing the Same Applications

CodeFest

The document discusses CQRS (Command Query Responsibility Segregation), an architectural pattern that separates read and write operations into different models. It aims to address complexity that arises from having a single model handle all aspects of a business domain. CQRS keeps write and read operations separated using different data models and stacks, which can simplify design and improve scalability. The document outlines different flavors of CQRS implementations from basic to more advanced using events and event sourcing.

Semplificare l'observability per progetti Serverless

Luciano Mammino

Hai mai pensato che le tue lambda functions possano fallire senza che tu te ne accorga? Se la risposta é "SI" probabilmente é perché ti sei giá "bruciato" giocando con il cloud, dove errori e fallimenti sono sempre dietro l'angolo. Purtroppo non possiamo prevenire tutti i fallimenti, pero' possiamo essere notificati quando qualcosa va storto cosí da poter reagire tempestivamente. Ma come fare a configurare il nostro ambiente AWS per raggiungere un buon livello di "Observability"? Se hai giá provato ad utilizzare CloudWatch saprai giá quanto possa essere complesso. In questo talk, esploreremo il tema dell'observability per applicazioni Serverless su AWS. Discuteremo problemi e best practices. Infine vi proporró un tool che permette di automatizzare la configurazione di CloudWatch per l'80% delle esigenze in pochi minuti!

Glue con2011 future_of_net_systems

James Urquhart

RA - Empower your Connected Enterprise with FactoryTalk.pptx

Ajay Gangakhedkar

The document discusses FactoryTalk InnovationSuite, an IIoT platform powered by PTC that provides data analytics, edge computing, AI, and augmented reality capabilities for empowering the connected enterprise. It presents an overview of the FactoryTalk InnovationSuite and its key components including the ThingWorx IIoT platform, fit for purpose applications, and data analytics tools. The platform allows for mobile/desktop access, orchestration of data sources from traditional and edge systems, and engages users through manufacturing apps, augmented reality, and scalable analytics.

Better Architecture without Architects.pdf

Geert van der Cruijsen

This document discusses how architecture roles are changing in DevOps organizations. It argues that traditional architect roles are no longer needed and that architecture is now a continuous process done by the whole team, not a separate role. It provides examples of how organizations can structure teams and share architectural knowledge to be more agile through techniques like architecture decision records and modeling.

Cloud Computing for Business - The Road to IT-as-a-Service

James Urquhart

This document discusses the transition from infrastructure-centric IT operations to service-centric operations driven by cloud computing. It explains that cloud computing asks IT to deliver computing resources as a set of services rather than managing individual servers, networks, and storage. This new model of service operations is comprised of application operations, service operations, and infrastructure operations. Application operations focus on consuming services through tools like multi-cloud management. Service operations identify and deliver key services with supporting capabilities. Infrastructure operations provide the common foundation through APIs and automation.

A Pragmatic Union: Security and SRE

James Wickett

Our Brave Modular Future

Orchestrate

agile microservices @scaibo

Ciro Donato Caiazzo

The document discusses agile microservices and their advantages over monolithic architectures. It describes how to decompose a monolithic real estate management application into independent microservices for properties, facilities, and engineering. Microservices allow for improved independence, speed of development, automation, and use of different technologies. Inter-service communication can occur over REST, HTTP, or AMQP, while an API gateway pattern hides service complexity from clients. Cloud computing platforms like Docker and Convox can deploy and manage containerized microservices. The Internet of Things connects physical devices to these services over protocols like MQTT and WebSocket.

DC Spark Users Group March 15 2016 - Spark and Netflix Recommendations

Chris Fregly

This document discusses various techniques for providing recommendations, including non-personalized and personalized recommendations. Non-personalized recommendations include using highest rated actors, top K aggregations, social graphs, or PageRank on likes/dislikes to address the cold start problem for new users. Personalized recommendations techniques discussed include user-to-user clustering based on similarity of viewing patterns or ratings. The document also covers feature engineering techniques such as normalization, dimensionality reduction, and one-hot encoding for modeling recommendations.

The Next Generation of Microservices

Phil Calçado

The document discusses the evolution of microservices architectures over time as techniques for handling issues like failures and timeouts were developed. It describes how early approaches involved adding timeouts and circuit breakers to code. Later, approaches involved sharing state between services and client-side service discovery. Today, sidecars and service meshes have moved reliability patterns lower in the stack, standardizing protocols and allowing services to abstract away operational concerns. However, meshes also introduce new tradeoffs around portability and development cycles.

Building Data Intensity with AWS MSK & Lenses.io

Lenses.io

This document discusses building data intensity through a DataOps approach. It emphasizes focusing on what matters through streaming data flows, self-service data visibility and governance, and skills. Data platforms need to provide visibility, access to data, integration capabilities, transformation capabilities, and deployment/scaling while being API-driven and allowing for governance, security and multi-tenancy. Technology should enable focus on data intensity. The remainder discusses Lenses.io's product for real-time applications and data operations and its use with AWS MSK for a customer, Vortexa, which tracks oil and gas flows.

From Pandas to Koalas: Reducing Time-To-Insight for Virgin Hyperloop's Data

Databricks

TAXTRON Profile_PDF

TAXTRON TECHNOLOGIES

Taxtron Technologies is an ISO 9001:2008 certified company that provides industrial and technological training. They have expertise in areas like IT hardware, networking, MATLAB, embedded systems, LabVIEW, industrial automation, and software development. Their goal is to reduce the gap between industry needs and what educational institutions teach. They train students to become industry-ready and also develop projects for industries and academic institutions.

“Performance” - Dallas Oracle Users Group 2019-01-29 presentation

Cary Millsap

In this session, Cary Millsap begins with a little bit of the theory behind why reducing call count is the most important goal of optimizing performance. Then he works through two examples where understanding the call count reduction idea is key to making progress. The first worked example is an intermittent performance problem that was frustratingly difficult to reproduce. The second worked example is a performance problem caused by an inefficiently-written application that overtaxes the system’s CPU.

Spark Summit East NYC Meetup 02-16-2016

Chris Fregly

This document summarizes a presentation on recommendations and machine learning using Apache Spark. It discusses scaling techniques like parallelism and composability. It also covers similarity measures, recommendation algorithms, and common approximations used like sampling. Common algorithms and data structures are explained, like similarity graphs and PageRank. Finally, it provides an overview of Netflix's recommendations system and data pipeline.

Similar to CQRS without event sourcing (20)

CQRS & Queue unlimited

Software Architecture Conference - Monitoring Microservices - A Challenge

Stuff About CQRS

Awesome Tools to Level Up Your Spring Cloud Architecture - Spring I/O 2017

CQRS: A More Effective Way of Writing the Same Applications

Semplificare l'observability per progetti Serverless

Glue con2011 future_of_net_systems

RA - Empower your Connected Enterprise with FactoryTalk.pptx

Better Architecture without Architects.pdf

Cloud Computing for Business - The Road to IT-as-a-Service

A Pragmatic Union: Security and SRE

Our Brave Modular Future

agile microservices @scaibo

DC Spark Users Group March 15 2016 - Spark and Netflix Recommendations

The Next Generation of Microservices

Building Data Intensity with AWS MSK & Lenses.io

From Pandas to Koalas: Reducing Time-To-Insight for Virgin Hyperloop's Data

TAXTRON Profile_PDF

“Performance” - Dallas Oracle Users Group 2019-01-29 presentation

Spark Summit East NYC Meetup 02-16-2016

More from Thomas Pierrain

The scale-up, the autonomy and the nuclear submarine

The document discusses the challenges of scaling up an organization while maintaining autonomy at various levels. It advocates giving teams and individuals responsibility and autonomy rather than micromanaging them. It also notes that while autonomy is important, it is not universally desired by all and balancing autonomy with coordination is delicate. The document concludes by stating the goal of leaving an organization with more autonomous people than when one started.

La scale-up, l'autonomie et le sous-marin nucléaire

La plupart des organisations efficaces ont en commun d’avoir des équipes autonomes. L’autonomie est aussi un moteur individuel puissant : qui n’aime pas se sentir libre de définir sa vie, ses horaires, sa façon de travailler ? Lorsqu’on travaille dans une scale-up en plein essor et qui grossit de manière exponentielle, l’autonomie n’est plus une option, c’est un carburant indispensable. Mais est-ce pour autant facile à mettre en oeuvre ? C’est de cette quête d’autonomie dont nous aimerions vous parler à travers nos histoires, nos réussites et nos erreurs. Nous parlerons de full-remote, de release management, de démarche SRE, de conflits d’équipes et de Domain Driven Design. On parlera aussi d’auto-organisation, d’APIs de split de monolithe, mais également de sous-marins nucléaires et de contract tests. Au final, pleins de trucs et astuces pour arriver à mettre en place une Culture de l’autonomie qui tienne la route sur le long terme.

De l'autre côté du miroir

This document discusses the importance of context in software development. It notes that without understanding the context, software can become too rigid or technical. It also discusses the need to represent the same real-world instrument, such as a futures contract, differently based on the context of trading, financial, or market systems. The document advocates for frequent communication between developers and customers to ensure the software properly accounts for necessary contexts.

eXtreme

This document discusses the principles and practices of extreme programming (XP). It presents the 13 core practices of XP including simple design, pair programming, collective ownership, and test-driven development. It emphasizes that XP relies on close collaboration between team members and embracing change. XP aims to remove barriers between team members and create a safe, supportive environment for software development.

Write Antifragile & Domain-Driven tests with ”Outside-in diamond” ◆ TDD

TDD is a game changer. It changed my dev life for good, no doubt. Having made almost all possible errors while practicing it over the years (more than 15 years of TDD practice), I have now ended up since many years with a style that provides me and my teams lots of efficiency and happiness. A style that Bruno Boucard and myself have called the “outside-in diamond” TDD. Something that help us to easily write both domain-driven, but also "Antifragile" tests. A session made at DDD Africa

Beyond Hexagonal architecture

The document discusses moving beyond a traditional hexagonal architecture to a more functional architecture. It outlines some benefits of a functional core such as business code without side effects and the ability to separate decisions from actions. The document compares features of hexagonal versus functional architecture and notes they should not be directly compared as they relate to different programming paradigms. It also questions whether the term "beyond hexagonal" accurately reflects incorporating functional concepts. Overall, the document explores options for mixing hexagonal architecture and functional programming principles.

The 9 rules of debugging

Hexagonal architecture vs Functional core / Imperative shell

The document discusses the differences between hexagonal architecture and functional architecture for software design. Hexagonal architecture separates infrastructure from business logic but allows business code with side effects, while functional architecture requires business code be free of side effects. Both approaches separate infrastructure from business concerns and support testability, but functional architecture more strictly avoids technical leaks into the domain and is better suited for functional programming languages. The document raises questions about how to handle sequential I/O operations in a functional style.

Une nuit dans l'hexagone

Equiper sa voie

Au-delà de la passion, faire du logiciel pour moi c’est aider les autres à résoudre leurs problèmes. Comment aider les autres si on n’est pas déjà clair soi-même avec sa posture, son métier, ses envies, ses ambitions ou bien ses craintes ? C’est la question que je me suis posé à plusieurs reprises durant ma carrière. Et c’est de cela - et des quelques aides trouvées en route - dont je voudrais vous parler. Keynote d'ouverture de la conférence d'Alpes Craft 2019 (le 13 juin 2019)

As time goes by (episode 2)

When building an Event Sourcing system, can we change the past? Can we also forecast “events” in the future? If we want to provide various projections/visions of things that hapenned over the time, what are the consequences and trade-offs on our code? All these questions will be answered during this talk. But moreover, I'll tell you our learning story about Bi-temporal Event Sourcing. Yet another illustration of the power of modeling, sketches and concrete examples when we need to understand each others.

Et si on parlait Éthique ?

Coder, c'est de plus en plus façonner le monde. Redéfinir ses contours et certaines interactions que nous pouvons avoir (ou pas) entre nous. Si certains métiers se sont déjà interrogés par le passé sur leur rôle et leur impact sur la société, il me semble que ces questions d'éthique ne nous traversent pas encore suffisamment dans la sphère des faiseuses et faiseurs de logiciels. Et si on se posait quelques minutes pour faire le tour de certaines d'entre elles ?

L'Agilité a grande échelle : conserver l'esprit, pas la lettre

Legacy club (english version)

Unmaintainable code, repetitive bugs, time-consuming corrections, depressed teams ... No wonder most of us prefer to start projects from scratch (a.k.a. Greenfield) rather than a Legacy code base (Brownfield). For sure, situations where control has been lost are annoying, even more: exhausting. But what if we were wrong? What if -fully equipped with some refactoring techniques and communication skills- we were able to reverse things and get back control over such situations? During a session with real live-coding inside, come and discover the tips and tricks from people who prefer to regain control rather than undergo. From people who prefers the hidden opportunities of the legacy to the blank pages of the Greenfield projects. You too, realize it could be fun and join the Legacy Club!

Culture Craft Devoxx 2015