Talk at QCon London. Based on an article in InfoWorld (https://www.infoworld.com/article/3254777/application-development/3-common-pitfalls-of-microservices-integrationand-how-to-avoid-them.html).
Source code available: https://github.com/flowing/flowing-retail/tree/master/payment-rest
Recording available: https://youtu.be/O2-NHptllKQ
Java User Group Maas-Rhine February 2018: 7 sins of workflowBernd Ruecker
Ā
Slides from my talk at Eureg JUG Aachen in February 2018. You can find the recoding here: https://youtu.be/hS-4hjeFjt0. Code is available: http://github.com/flowing/flowing-retail and https://github.com/flowing/flowing-retail/tree/master/payment-rest.
Jfokus 2018: Lost in transaction - Strategies to deal with (in-)consistency ...Bernd Ruecker
Ā
Slides from my talk at Jfokus 2018 about how to avoid getting lost in transaction. Code is here: https://github.com/flowing/flowing-retail and https://github.com/flowing/flowing-retail/tree/master/payment-rest.
O'Reilly SA NYC 2018: Complex event flows in distributed systemsBernd Ruecker
Ā
Slides from my talk at O'Reilly Software Architecture Conference in New York City on 28th of February 2018. Code from the demo is available: http://github.com/flowing/flowing-retail
Java User Group Erfurt 2018: Zeebe.io - Event-driven Microservice OrchestrationBernd Ruecker
Ā
Slides from my talk at JUG Erfurt on 22nd or march 2018.
Sample code available: https://github.com/flowing/flowing-retail/tree/zeebe
Recording in German available: https://youtu.be/lZIe02um5eI
Webinar "Communication Between Loosely Coupled Microservices"Bernd Ruecker
Ā
Slides from the Camunda webinar "Communication Between Loosely Coupled Microservices" in February 2021. Recording can be found online: https://page.camunda.com/wb-communication-between-microservices
Java User Group Maas-Rhine February 2018: 7 sins of workflowBernd Ruecker
Ā
Slides from my talk at Eureg JUG Aachen in February 2018. You can find the recoding here: https://youtu.be/hS-4hjeFjt0. Code is available: http://github.com/flowing/flowing-retail and https://github.com/flowing/flowing-retail/tree/master/payment-rest.
Jfokus 2018: Lost in transaction - Strategies to deal with (in-)consistency ...Bernd Ruecker
Ā
Slides from my talk at Jfokus 2018 about how to avoid getting lost in transaction. Code is here: https://github.com/flowing/flowing-retail and https://github.com/flowing/flowing-retail/tree/master/payment-rest.
O'Reilly SA NYC 2018: Complex event flows in distributed systemsBernd Ruecker
Ā
Slides from my talk at O'Reilly Software Architecture Conference in New York City on 28th of February 2018. Code from the demo is available: http://github.com/flowing/flowing-retail
Java User Group Erfurt 2018: Zeebe.io - Event-driven Microservice OrchestrationBernd Ruecker
Ā
Slides from my talk at JUG Erfurt on 22nd or march 2018.
Sample code available: https://github.com/flowing/flowing-retail/tree/zeebe
Recording in German available: https://youtu.be/lZIe02um5eI
Webinar "Communication Between Loosely Coupled Microservices"Bernd Ruecker
Ā
Slides from the Camunda webinar "Communication Between Loosely Coupled Microservices" in February 2021. Recording can be found online: https://page.camunda.com/wb-communication-between-microservices
Talk given at DDDx London on 27th of April about how to implement long running processes in Domain Driven Design properly. Describes patterns like Process Manager and Saga.
Webinar: Monitoring & Orchestrating Your Microservices Landscape using Workfl...camunda services GmbH
Ā
A companyās core business processes nearly always span more than one microservice. In an e-commerce company, for example, a ācustomer orderā might involve different services for payments, inventory, shipping and more. But how do these services play together to fulfill the customerās desire?
Implementing long-running, asynchronous, and complex collaborations between distributed microservices is challenging. How can we ensure visibility of cross-microservice flows and provide status and error monitoring? How do we guarantee that overall flows always complete, even if single services fail? Or how do we recognize stuck flows so that we can fix them?
In this webinar, Bernd will explain how workflow automation supports the orchestration of microservices, to make sure business processes are always carried out - even in case of failure -
providing monitoring and visibility into the overall progress and status.
He will reveal how to do all of this without introducing monolithic workflows that clash with microservices principles. You will also learn how to balance orchestration (using a workflow engine) with choreography (using events). Still believe that choreography is more loosely coupled and thus the modern way to go? You definitely need to listen inā¦
JUG Amsterdam - Orchestration of microservicesBernd Ruecker
Ā
Slides from the talk at JUG Amsterdam I held at 25th of September 2017. The live hacking code is available on GitHub: https://github.com/flowing/flowing-retail.
Serverless Days 2019 - Lost in transactionBernd Ruecker
Ā
Slides from my talk at Serverless Days Hamburg 2019 about how to avoid getting lost in transaction, how to coordinate multiple functions and how Sagas might help.
Source code is here: https://github.com/berndruecker/trip-booking-saga-serverless
November 2017: Collaboration of (micro-)servicesBernd Ruecker
Ā
Slides from a talk held at WJAX Munic on 9th of November (and some other meetups later in November) about how to tackle collaboration of microservices.
Most of the talk was live coding, the respective code is here: https://github.com/flowing/flowing-retail.
Slides from a talk held at WJAX Munic on 9th of November (and some other meetups later in November) about how to tackle collaboration of microservices.
Most of the talk was live coding, the respective code is here: https://github.com/flowing/flowing-retail.
Bernd Ruecker - 3 Common Pitfalls in Microservice Integration - Codemotion Be...Codemotion
Ā
Integrating microservices and distributed systems is hard. In this talk I will present three challenges we observed in real-life projects and how to avoid them. 1. Communication is complex. With everything being distributed failures are normal so you need sophisticated failure handling. 2. Asynchronicity requires you to handle timeouts. This is not only about milliseconds--systems get much more resilient when you can wait for minutes or hours. 3. Distributed transactions cannot simply be delegated to protocols like XA. I will not only use slides but demonstrate concrete source code examples.
Bernd Ruecker - 3 Common Pitfalls in Microservice Integration - Codemotion Be...Codemotion
Ā
Integrating microservices and distributed systems is hard. In this talk I will present three challenges we observed in real-life projects and how to avoid them. 1. Communication is complex. With everything being distributed failures are normal so you need sophisticated failure handling. 2. Asynchronicity requires you to handle timeouts. This is not only about milliseconds--systems get much more resilient when you can wait for minutes or hours. 3. Distributed transactions cannot simply be delegated to protocols like XA. I will not only use slides but demonstrate concrete source code examples.
Talk given at DDDx London on 27th of April about how to implement long running processes in Domain Driven Design properly. Describes patterns like Process Manager and Saga.
Webinar: Monitoring & Orchestrating Your Microservices Landscape using Workfl...camunda services GmbH
Ā
A companyās core business processes nearly always span more than one microservice. In an e-commerce company, for example, a ācustomer orderā might involve different services for payments, inventory, shipping and more. But how do these services play together to fulfill the customerās desire?
Implementing long-running, asynchronous, and complex collaborations between distributed microservices is challenging. How can we ensure visibility of cross-microservice flows and provide status and error monitoring? How do we guarantee that overall flows always complete, even if single services fail? Or how do we recognize stuck flows so that we can fix them?
In this webinar, Bernd will explain how workflow automation supports the orchestration of microservices, to make sure business processes are always carried out - even in case of failure -
providing monitoring and visibility into the overall progress and status.
He will reveal how to do all of this without introducing monolithic workflows that clash with microservices principles. You will also learn how to balance orchestration (using a workflow engine) with choreography (using events). Still believe that choreography is more loosely coupled and thus the modern way to go? You definitely need to listen inā¦
JUG Amsterdam - Orchestration of microservicesBernd Ruecker
Ā
Slides from the talk at JUG Amsterdam I held at 25th of September 2017. The live hacking code is available on GitHub: https://github.com/flowing/flowing-retail.
Serverless Days 2019 - Lost in transactionBernd Ruecker
Ā
Slides from my talk at Serverless Days Hamburg 2019 about how to avoid getting lost in transaction, how to coordinate multiple functions and how Sagas might help.
Source code is here: https://github.com/berndruecker/trip-booking-saga-serverless
November 2017: Collaboration of (micro-)servicesBernd Ruecker
Ā
Slides from a talk held at WJAX Munic on 9th of November (and some other meetups later in November) about how to tackle collaboration of microservices.
Most of the talk was live coding, the respective code is here: https://github.com/flowing/flowing-retail.
Slides from a talk held at WJAX Munic on 9th of November (and some other meetups later in November) about how to tackle collaboration of microservices.
Most of the talk was live coding, the respective code is here: https://github.com/flowing/flowing-retail.
Bernd Ruecker - 3 Common Pitfalls in Microservice Integration - Codemotion Be...Codemotion
Ā
Integrating microservices and distributed systems is hard. In this talk I will present three challenges we observed in real-life projects and how to avoid them. 1. Communication is complex. With everything being distributed failures are normal so you need sophisticated failure handling. 2. Asynchronicity requires you to handle timeouts. This is not only about milliseconds--systems get much more resilient when you can wait for minutes or hours. 3. Distributed transactions cannot simply be delegated to protocols like XA. I will not only use slides but demonstrate concrete source code examples.
Bernd Ruecker - 3 Common Pitfalls in Microservice Integration - Codemotion Be...Codemotion
Ā
Integrating microservices and distributed systems is hard. In this talk I will present three challenges we observed in real-life projects and how to avoid them. 1. Communication is complex. With everything being distributed failures are normal so you need sophisticated failure handling. 2. Asynchronicity requires you to handle timeouts. This is not only about milliseconds--systems get much more resilient when you can wait for minutes or hours. 3. Distributed transactions cannot simply be delegated to protocols like XA. I will not only use slides but demonstrate concrete source code examples.
WeAreDevelopers Live 2024 - Mastering long-running processes in modern archit...Bernd Ruecker
Ā
Slides from my talk at WeAreDevelopers Live on the Java Day about long-running processes. Code can be found here: https://github.com/berndruecker/customer-onboarding-camunda-8-springboot
CraftConf: Surviving the hyperautomation low code bubblBernd Ruecker
Ā
Slides from my talk at CraftConf Budapest in May 2023 about how developers can embrace and shape low code applications in their organizations to help the business automate more
Slides from my talk "Microservices Architectures" at JAX Mainz on 3rd of May 2022 (https://jax.de/software-architecture/understanding-communication-patterns-in-microservices-architectures/)
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Ā
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
Ā
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Ā
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Ā
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
DevOps and Testing slides at DASA ConnectKari Kakkonen
Ā
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
Ā
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Ā
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overviewā
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Ā
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Ā
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Ā
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Ā
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
24. We are having some technical
difficulties and cannot present you
your boarding pass right away.
But we do actively retry ourselves, so
lean back, relax and we will send it
on time.
37. We are processing your payment.
Do not leave this page.
And for god sake ā do not reload!
It is a business
problem
anyway!
38. We are processing your payment.
Do not leave this page.
And for god sake ā do not reload!
It is a business
problem
anyway!
We are currently processing your request.
Donāt worry, it will happen safely ā
even if you loose connection.
Feel free to reload this page any time!
51. generateBoardingPass
HTTP 200 OK
HTTP 202 ACCEPTED
Check-in
A synchronous response is possible in the
happy case, otherwise it is switched to
asynchronous processing.
52. āThe customer wants a synchronous responseā
Check-in
Barcode
Generator
Web-UI
Me
Output
Mgmt
āEh ā no!ā
53. Synchronous communication
is the crystal meth of
distributed programming
Todd Montgomery and Martin Thompson
in āHow did we end up hereā at GOTO Chicago 2015
61. Who has no problems
operating a message bus?
Dead messages | No context | Inaccesible payload | Hard to redeliver |
Home-grown message hospitals | ā¦
70. has to implement
Timeout, Retry,
Compensation
has to offer
Compensation
has to implement
Idempotency
Client Service Provider
71. has to implement
Timeout, Retry,
Compensation
has to offer
Compensation
has to implement
Idempotency
Client Service ProviderDonāt forget
about state
72. Before mapping processes
explicitly with BPMN, the truth was
buried in the code and nobody
knew what was going on.
Jimmy Floyd, 24 Hour Fitnesse
ā
73. Event-driven example also available
InventoryPaymentOrder ShippingCheckout Monitor
https://github.com/flowing/flowing-retail/
Human
Tasks
H2 H2
77. # Be aware of complexity of distributed systems
# Know strategies and tools to handle it
e.g. Circuit breaker (Hystrix)
Workflow engine for stateful retry, waiting, timeout
and compensation (Camunda)