Destination Automation: Automating Processes in Modern Hipster Architectures

•

2 recomendaciones•1,013 vistas

Slides for my talk at #DestinationAutomation in July 2020. Code examples are here: https://github.com/berndruecker/ticket-booking-camunda-cloud

Tecnología

Automating Processes
in Modern
Hipster Architectures
@berndruecker

Example
Payment
Seat
ReservationBooking
Ticket
Generation

REST?
Payment
Seat
ReservationBooking
Ticket
Generation
REST
REST
REST
REST

Weaknesses: Latency creep
Payment
Seat
ReservationBooking
Ticket
Generation
REST
300 ms
1150 + x ms
600 ms
250 ms

Weaknesses: Availabiliy erosion
Payment
Seat
ReservationBooking
Ticket
Generation
REST
99 % uptime
99 % uptime
99 % uptime
96 % uptime

And what about consistency?
Payment
Seat
ReservationBooking
Ticket
Generation

What‘s hipster?
Event-Driven
Reactive
Distributed Systems
Microservices
Agile
Streaming
Cloud-Native
Eventual Consistency
Kubernetes
Serverless

Event Bus
Event-Driven Choreography
Payment
Seat
Reservation
Ticket
Generation
Ticket
booked
Seat
reserved
Payment
received
Ticket
generated

What we wanted
Photo by Lijian Zhang, available under Creative Commons SA 2.0 License and P..19 / CC BY-SA 4.0
@berndruecker

The danger is that it's very easy to make
nicely decoupled systems with event
notification, without realizing that you're
losing sight of that larger-scale flow, and
thus set yourself up for trouble in future
years.
https://martinfowler.com/articles/201701-event-driven.html
@berndruecker

How-to monitor
event-driven processes?
https://camunda.com/learn/webinars/
microservices-landscape-workflow-automation/

Orchestration
Payment
Seat
ReservationBooking
Ticket
Generation
This component orchestrates
the others
coordinates

Orchestration ≠ Synchronous Communication
Payment
Seat
ReservationBooking
Ticket
Generation
Kafka
AMQP
FaaS
REST

A workflow engine can help
Payment
Seat
ReservationBooking
Ticket
Generation
REST

A workflow engine can help
Payment
Seat
ReservationBooking
Ticket
Generation
REST
A workflow engine
Keeps persistent state
Can wait
Can retry
Can escalate
Can compensate
…

Berlin, Germany
mail@berndruecker.io
@berndruecker
Bernd Ruecker
Co-founder and
Chief Technologist of
Camunda

Architecture
Payment
Seat
Reservation
Ticket
Generation
REST
Booking
Java Spring Boot App
Camunda Cloud
Client
Camunda Cloud
Workflow Engine
AMQP
REST
Workflow engine
subscription
FakeServices
NodeJs App
https://github.com/berndruecker/ticket-booking-camunda-cloud

Camunda Cloud is based on Zeebe (OSS workflow engine)
http://zeebe.io/

Can your company
leverage your
hipster architecture?
Shutterstock
You need to
change business
processes and
customer
experience!

@berndruecker
happy
case
failure
case
Redesign your business process accordingly!
Or some interface
to poll for status
Sync in happy case
Async response

Summary
• Synchronous call chains have weknesses
• Event-driven choreography is not a magic cure
• Orchestration
• Helps to avoid chaos
• Can be handled within one service (decentral)
• Does not mean synchronous communication
• To leverage a great hipster architecture you need to adjust
business processes and customer experience

mail@berndruecker.io
@berndruecker
https://berndruecker.io
https://medium.com/berndruecker
https://github.com/berndruecker
https://www.infoq.com/articles/events-
workflow-automation
Contact:
Slides:
Blog:
Code:
https://www.infoworld.com/article/3254777/
application-development/
3-common-pitfalls-of-microservices-
integrationand-how-to-avoid-them.html
https://thenewstack.io/5-workflow-automation-
use-cases-you-might-not-have-considered/

Más contenido relacionado

La actualidad más candente

Workflow automation with BPMN. Lessons learned.

Bernd Ruecker

3 common pitfalls in microservice integration

Bernd Ruecker

2019 - Lost in transaction

Bernd Ruecker

Microservices with Camunda - Talk from Camunda Days 01/2018

Bernd Ruecker

JFS 2021 - The Process Automation Map

Bernd Ruecker

QCon NYC 2019 - Workflow automation reinvented

Bernd Ruecker

2019 DACH Roadshow - Workflow Automation in Microservices Architectures

Bernd Ruecker

Process Automation Forum April 2021 - Practical Process Automation

Bernd Ruecker

JAX 2019 - Workflow automation reinvented

Bernd Ruecker

DDD Europe 2019: Lost in transaction

Bernd Ruecker

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…

Webinar: Monitoring & Orchestrating Your Microservices Landscape using Workfl...

camunda services GmbH

Digitalization and Workflow Automation - Camunda Process Automation Forum

Bernd Ruecker

Lost in transaction - Strategies to deal with (in)consistency in distributed ...

Bernd Ruecker

Kafka Summit 2018: Monitoring and Orchestration of Your Microservices Landsca...

Bernd Ruecker

Kafka Summit 2021 - Apache Kafka meets workflow engines

Bernd Ruecker

JCon 2021 - Loosely or lousily coupled

Bernd Ruecker

GopherCon UK 2018 - Orchestration of microservices

Bernd Ruecker

Slides from my talk at QCon London on 5th of March 2019. More information can be found here: https://berndruecker.io/complex-event-flows-in-distributed-systems/ Abstract: Event-driven architectures enable nicely decoupled microservices and are fundamental for decentral data management. However, using peer-to-peer event chains to implement complex end-to-end logic crossing service boundaries can accidentally increase coupling. Extracting such business logic into dedicated services reduces coupling and allows to keep sight of larger-scale flows - without violating bounded contexts, harming service autonomy or introducing god services. Service boundaries get clearer and service APIs get smarter by focusing on their potentially long running nature. I will demonstrate how the new generation of lightweight and highly-scalable state machines ease the implementation of long running services. Based on my real-life experiences, I will share how to handle complex logic and flows which require proper reactions on failures, timeouts and compensating actions and provide guidance backed by code examples to illustrate alternative approaches.

Complex event flows in distributed systems (QCon London 2019)

Bernd Ruecker

Serverless London 2019 - Coordination of Serverless Functions

Bernd Ruecker

Presented by Bernd Rücker, Co-Founder of Camunda With microservices (or serverless functions) whole architectures are cut into smaller pieces that are ideally loosely coupled. In this talk I will discuss what this means for business processes that typically span more than one microservice. I will tackle questions like: 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? How can do this without introducing tight coupling or harming service autonomy? What does this mean for your architecture and the role of workflow automation technology within it?

CamundaCon 2018: The Role of Workflows in Microservices (Camunda)

camunda services GmbH

La actualidad más candente (20)

Workflow automation with BPMN. Lessons learned.

3 common pitfalls in microservice integration

2019 - Lost in transaction

Microservices with Camunda - Talk from Camunda Days 01/2018

JFS 2021 - The Process Automation Map

QCon NYC 2019 - Workflow automation reinvented

2019 DACH Roadshow - Workflow Automation in Microservices Architectures

Process Automation Forum April 2021 - Practical Process Automation

JAX 2019 - Workflow automation reinvented

DDD Europe 2019: Lost in transaction

Webinar: Monitoring & Orchestrating Your Microservices Landscape using Workfl...

Digitalization and Workflow Automation - Camunda Process Automation Forum

Lost in transaction - Strategies to deal with (in)consistency in distributed ...

Kafka Summit 2018: Monitoring and Orchestration of Your Microservices Landsca...

Kafka Summit 2021 - Apache Kafka meets workflow engines

JCon 2021 - Loosely or lousily coupled

GopherCon UK 2018 - Orchestration of microservices

Complex event flows in distributed systems (QCon London 2019)

Serverless London 2019 - Coordination of Serverless Functions

CamundaCon 2018: The Role of Workflows in Microservices (Camunda)

Similar a Destination Automation: Automating Processes in Modern Hipster Architectures

(Bernd Ruecker, Camunda) Kafka Summit SF 2018 A company’s business processes typically span more than one microservice. In an e-commerce company, for example, a customer order might involve microservices for payments, inventory, shipping and more. Implementing long-running, asynchronous and complex collaboration of 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 at least recognize stuck flows so that we can fix them? In this talk, I’ll demonstrate an approach based on real-life projects using the open source workflow engine zeebe.io to orchestrate microservices. Zeebe can connect to Kafka to coordinate workflows that span many microservices, providing end-to-end process visibility without violating the principles of loose coupling and service independence. Once an orchestration flow starts, Zeebe ensures that it is eventually carried out, retrying steps upon failure. In a Kafka architecture, Zeebe can easily produce events (or commands) and subscribe to events that will be correlated to workflows. Along the way, Zeebe facilitates monitoring and visibility into the progress and status of orchestration flows. Internally, Zeebe works as a distributed, event-driven and event-sourced system, making it not only very fast but horizontally scalable and fault tolerant—and able to handle the throughput required to operate alongside Kafka in a microservices architecture. Expect not only slides but also fun little live-hacking sessions and real-life stories.

The Big Picture: Monitoring and Orchestration of Your Microservices Landscape...

confluent

AWS Community Summit London 2019 - Lost in transaction

Bernd Ruecker

Bernd Rücker - Lost in transaction? Strategies to manage consistency in serve...

AWSCOMSUM

Kafka and Machine Learning in Banking and Insurance Industry

Kai Wähner

Goto meetup Stockholm - Let your microservices flow

Bernd Ruecker

Event mesh api meetup AsyncAPI Singapore

Phil Scanlon

Process automation technology progressed massively over the last years and can handle modern scalability and resiliency requirements. It is not the dinosaur some people think it is! Now there are super interesting combinations between Kafka and a workflow engine possible, such as starting or influencing process instances upon certain events in a stream, orchestrating microservices by writing commands as Kafka records, or using Kafka to collect information about decentralized process executions. In this talk, I will briefly walk you through these possibilities presenting real-life use cases and some sample code using open source tools.

Apache Kafka Meets Workflow Engines | Bernd Ruecker, Camunda

HostedbyConfluent

Reactive Summit 2020 - How state helps you to stay reactive

Bernd Ruecker

This session will begin with a short recap of how we created systems over the past 20 years, up to the current idea of building systems, using a Microservices architecture. What is a Microservices architecture and how does it differ from a Service-Oriented Architecture? Should you use traditional REST APIs to integrate services with each each other in a Microservices Architecture? Or is it better to use a more loosely-coupled protocol? Answers to these and many other questions are provided. The talk will show how a distributed log (event hub) can help to create a central, persistent history of events and what benefits we achieve from doing so. Apache Kafka is a perfect match for building such an asynchronous, loosely-coupled event-driven backbone. Events trigger processing logic, which can be implemented in a more traditional as well as in a stream processing fashion. The talk shows the difference between a request-driven and event-driven communication and answers when to use which. It highlights how a modern stream processing system can be used to hold state both internally as well as in a database and how this state can be used to further increase independence of other services, the primary goal of a Microservices architecture.

Building event-driven Microservices with Kafka Ecosystem

Guido Schmutz

This talk begins with a short recap of how we created systems over the past 20 years, up to the current idea of building systems, using a Microservices architecture. What is a Microservices architecture and how does it differ from a Service-Oriented Architecture? Should you use traditional REST APIs to integrate services with each eachother in a Microservices Architecture? Or is it better to use a more loosely-coupled protocol? Answers to these and many other questions are provided. The talk will show how a distributed log (event hub) can help to create a central, persistent history of events and what benefits we achieve from doing so. Apache Kafka is a perfect match for building such an asynchronous, loosely-coupled event-driven backbone. Events trigger processing logic, which can be implemented in a more traditional as well as in a stream processing fashion. The talk shows the difference between a request-driven and event-driven communication and answers when to use which. It highlights how a modern stream processing systems can be used to hold state both internally as well as in a database and how this state can be used to further increase independence of other services, the primary goal of a Microservices architecture.

Building event-driven (Micro)Services with Apache Kafka

Guido Schmutz

apidays LIVE JAKARTA - Event Driven APIs by Phil Scanlon

apidays

JAX 2017 talk: Orchestration of microservices

Bernd Ruecker

Today, in 2022, Apache Kafka is the central nervous system of many applications in various areas related to the automotive and manufacturing industry for processing analytical and transactional data in motion across edge, hybrid, and multi-cloud deployments. This presentation explores the automotive event streaming landscape, including connected vehicles, smart manufacturing, supply chain optimization, aftersales, mobility services, and innovative new business models. Afterwards, many real-world examples are shown from companies such as Audi, BMW, Porsche, Tesla, Uber, Grab, and FREENOW. More detail in the blog post: https://www.kai-waehner.de/blog/2022/01/12/apache-kafka-landscape-for-automotive-and-manufacturing/

Apache Kafka Landscape for Automotive and Manufacturing

Kai Wähner

Should you use traditional REST APIs to bind services together? Or is it better to use a richer, more loosely-coupled protocol? This talk will dive into how we piece services together in event driven systems, how we use a distributed log (event hub) to create a central, persistent history of events and what benefits we achieve from doing so. Apache Kafka is a perfect match for building such an asynchronous, loosely-coupled event-driven backbone. Events trigger processing logic, which can be implemented in a more traditional as well as in a stream processing fashion. The talk will show the difference between a request-driven and event-driven communication and show when to use which. It highlights how the modern stream processing systems can be used to hold state both internally as well as in a database and how this state can be used to further increase independence of other services, the primary goal of a Microservices architecture.

Building event-driven (Micro)Services with Apache Kafka Ecosystem

Guido Schmutz

Camunda Day Amsterdam 2019: Workflow Automation in Microservices Architecture...

camunda services GmbH

Build with Serverless Applications with azure functions By usama wahab Khan

Usama Wahab Khan Cloud, Data and AI

Should we use traditional REST APIs to bind services together? Or is it better to use a more loosely-coupled protocol? This talk will dive into how we piece services together in event driven systems, how we use a distributed log (event hub) to create a central, persistent history of events and what benefits we achieve from doing so. Apache Kafka is a perfect match for building an asynchronous, loosely-coupled event-driven backbone. Events trigger processing logic, which can be implemented in a traditional as well as in a stream processing fashion. The talk will show the difference between a request-driven and event-driven communication and show when to use which.

Building Event-Driven (Micro)Services with Apache Kafka

Guido Schmutz

Keep your venue packed with bookings!

Venue Arc

"Workflow engines and event streaming brokers offer very different solutions to the same requirement - an optimal implementation of microservices communication. At Wix, we have a good experience with event-driven architecture for our 2500 microservices using Apache Kafka. Apache Kafka provides: * Support for very high throughput * Fault tolerance * Very loose coupling * Huge connectors eco-system Temporal workflow orchestration has interesting features: * Support for long running tasks * Business flows visual tracking * Easy to follow imperative style programming In this talk we will learn about the tradeoffs between the two technologies and how to implement various use cases in each architecture, including those that need a little more work."

Workflow Engines & Event Streaming Brokers - Can They Work Together?

HostedbyConfluent

Workflow engines and event streaming brokers offer very different solutions to the same requirement - an optimal implementation of microservices communication. At Wix, we have a good experience with event-driven architecture for our 2500 microservices using Apache Kafka. Apache Kafka provides: * support for very high throughput * Fault tolerance * very loose coupling * Huge connectors eco-system Temporal workflow orchestration has interesting features: * Support for long running tasks * business flows visual tracking * Easy to follow imperative style programming In this talk we will learn about the tradeoffs between the two technologies and how to implement various use cases in each architecture, including those that need a little more work.

Workflow Engines & Event Streaming Brokers - Can they work together? [Current...

Natan Silnitsky

Similar a Destination Automation: Automating Processes in Modern Hipster Architectures (20)

The Big Picture: Monitoring and Orchestration of Your Microservices Landscape...

AWS Community Summit London 2019 - Lost in transaction

Bernd Rücker - Lost in transaction? Strategies to manage consistency in serve...

Kafka and Machine Learning in Banking and Insurance Industry

Goto meetup Stockholm - Let your microservices flow

Event mesh api meetup AsyncAPI Singapore

Apache Kafka Meets Workflow Engines | Bernd Ruecker, Camunda

Reactive Summit 2020 - How state helps you to stay reactive

Building event-driven Microservices with Kafka Ecosystem

Building event-driven (Micro)Services with Apache Kafka

apidays LIVE JAKARTA - Event Driven APIs by Phil Scanlon

JAX 2017 talk: Orchestration of microservices

Apache Kafka Landscape for Automotive and Manufacturing

Building event-driven (Micro)Services with Apache Kafka Ecosystem

Camunda Day Amsterdam 2019: Workflow Automation in Microservices Architecture...

Build with Serverless Applications with azure functions By usama wahab Khan

Building Event-Driven (Micro)Services with Apache Kafka

Keep your venue packed with bookings!

Workflow Engines & Event Streaming Brokers - Can They Work Together?

Workflow Engines & Event Streaming Brokers - Can they work together? [Current...

Más de Bernd Ruecker

QCon London: Mastering long-running processes in modern architectures

Bernd Ruecker

WeAreDevelopers Live 2024 - Mastering long-running processes in modern archit...

Bernd Ruecker

iSAQB Software Architecture Gathering 2023: How Process Orchestration Increas...

Bernd Ruecker

JCon Live 2023 - Lice coding some integration problems

Bernd Ruecker

JFall - Process Oriented Integration

Bernd Ruecker

CamundaCon NYC 2023 Keynote - Shifting into overdrive with process orchestration

Bernd Ruecker

JavaLand 2023 - Process Oriented Integration

Bernd Ruecker

CraftConf: Surviving the hyperautomation low code bubbl

Bernd Ruecker

Mastering Data for Higher Business Impact - at Commerzbank Innovation Summit

Bernd Ruecker

Camunda Chapter Hamburg - Surviving the hyperautomation low code bubble

Bernd Ruecker

Loosely or lousily coupled - Understanding communication patterns in microser...

Bernd Ruecker

CamundaCon 2022 Keynote: The Process Orchestration Journey

Bernd Ruecker

JAX 2022 - Loosely or lousily coupled

Bernd Ruecker

CamundaCon 2021 Keynote :From Human Workflow to High-Throughput Process Autom...

Bernd Ruecker

Micronaut Webinar 2021 - Process Automation Introduction

Bernd Ruecker

Automating Processes in Modern Architectures

Bernd Ruecker

GOTOpia 2020 - Balancing Choreography and Orchestration

Bernd Ruecker

Kafka Summit 2020: If an event is published to a topic and no one is around t...

Bernd Ruecker

Slides from my talk at QCon London on March 3rd 2020. Abstract: Integrating microservices or other components is hard, as it involves taming distributed systems. New API technologies are great, but can't magically solve all underlying challenges. This talk distills real-life experiences around typical architecture patterns. You will understand why you have to carefully think about boundaries and responsibilities of all your components. Further you will see why balancing orchestration and choreography is essential to avoid chaos. We also need to talk about idempotency, long-running and event-driven services. Don’t worry if you are new here, I will use easy to understand examples. In the end you will have gained a better feeling how to make your API smarter.

Moving beyond request reply - designing smarter APIs

Bernd Ruecker

Más de Bernd Ruecker (19)

QCon London: Mastering long-running processes in modern architectures

WeAreDevelopers Live 2024 - Mastering long-running processes in modern archit...

iSAQB Software Architecture Gathering 2023: How Process Orchestration Increas...

JCon Live 2023 - Lice coding some integration problems

JFall - Process Oriented Integration

CamundaCon NYC 2023 Keynote - Shifting into overdrive with process orchestration

JavaLand 2023 - Process Oriented Integration

CraftConf: Surviving the hyperautomation low code bubbl

Mastering Data for Higher Business Impact - at Commerzbank Innovation Summit

Camunda Chapter Hamburg - Surviving the hyperautomation low code bubble

Loosely or lousily coupled - Understanding communication patterns in microser...

CamundaCon 2022 Keynote: The Process Orchestration Journey

JAX 2022 - Loosely or lousily coupled

CamundaCon 2021 Keynote :From Human Workflow to High-Throughput Process Autom...

Micronaut Webinar 2021 - Process Automation Introduction

Automating Processes in Modern Architectures

GOTOpia 2020 - Balancing Choreography and Orchestration

Kafka Summit 2020: If an event is published to a topic and no one is around t...

Moving beyond request reply - designing smarter APIs

Último

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

MadyBayot

Join our latest Connector Corner webinar to discover how UiPath Integration Service revolutionizes API-centric automation in a 'Quote to Cash' process—and how that automation empowers businesses to accelerate revenue generation. A comprehensive demo will explore connecting systems, GenAI, and people, through powerful pre-built connectors designed to speed process cycle times. Speakers: James Dickson, Senior Software Engineer Charlie Greenberg, Host, Product Marketing Manager

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

DianaGray10

"I see eyes in my soup": How Delivery Hero implemented the safety system for ...

Zilliz

Created by Mozilla Research in 2012 and now part of Linux Foundation Europe, the Servo project is an experimental rendering engine written in Rust. It combines memory safety and concurrency to create an independent, modular, and embeddable rendering engine that adheres to web standards. Stewardship of Servo moved from Mozilla Research to the Linux Foundation in 2020, where its mission remains unchanged. After some slow years, in 2023 there has been renewed activity on the project, with a roadmap now focused on improving the engine’s CSS 2 conformance, exploring Android support, and making Servo a practical embeddable rendering engine. In this presentation, Rakhi Sharma reviews the status of the project, our recent developments in 2023, our collaboration with Tauri to make Servo an easy-to-use embeddable rendering engine, and our plans for the future to make Servo an alternative web rendering engine for the embedded devices industry. (c) Embedded Open Source Summit 2024 April 16-18, 2024 Seattle, Washington (US) https://events.linuxfoundation.org/embedded-open-source-summit/ https://ossna2024.sched.com/event/1aBNF/a-year-of-servo-reboot-where-are-we-now-rakhi-sharma-igalia

A Year of the Servo Reboot: Where Are We Now?

Igalia

ICT role in 21st century education and its challenges

rafiqahmad00786416

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Martijn de Jong

Manulife - Insurer Transformation Award 2024

The Digital Insurer

FWD Group - Insurer Innovation Award 2024

The Digital Insurer

Abhishek Deb(1), Mr Abdul Kalam(2) M. Des (UX) , School of Design, DIT University , Dehradun. This paper explores the future potential of AI-enabled smartphone processors, aiming to investigate the advancements, capabilities, and implications of integrating artificial intelligence (AI) into smartphone technology. The research study goals consist of evaluating the development of AI in mobile phone processors, analyzing the existing state as well as abilities of AI-enabled cpus determining future patterns as well as chances together with reviewing obstacles as well as factors to consider for more growth.

Exploring the Future Potential of AI-Enabled Smartphone Processors

debabhi2

Automating Google Workspace (GWS) & more with Apps Script

wesley chun

Strategies for Landing an Oracle DBA Job as a Fresher

Remote DBA Services

Scalable LLM APIs for AI and Generative AI Application Development Ettikan Karuppiah, Director/Technologist - NVIDIA Apidays Singapore 2024: Connecting Customers, Business and Technology (April 17 & 18, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays Singapore 2024 - Scalable LLM APIs for AI and Generative AI Applicati...

apidays

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Juan lago vázquez

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Edi Saputra

Following the popularity of "Cloud Revolution: Exploring the New Wave of Serverless Spatial Data," we're thrilled to announce this much-anticipated encore webinar. In this sequel, we'll dive deeper into the Cloud-Native realm by uncovering practical applications and FME support for these new formats, including COGs, COPC, FlatGeoBuf, GeoParquet, STAC, and ZARR. Building on the foundation laid by industry leaders Michelle Roby of Radiant Earth and Chris Holmes of Planet in the first webinar, this second part offers an in-depth look at the real-world application and behind-the-scenes dynamics of these cutting-edge formats. We will spotlight specific use-cases and workflows, showcasing their efficiency and relevance in practical scenarios. Discover the vast possibilities each format holds, highlighted through detailed discussions and demonstrations. Our expert speakers will dissect the key aspects and provide critical takeaways for effective use, ensuring attendees leave with a thorough understanding of how to apply these formats in their own projects. Elevate your understanding of how FME supports these cutting-edge technologies, enhancing your ability to manage, share, and analyze spatial data. Whether you're building on knowledge from our initial session or are new to the serverless spatial data landscape, this webinar is your gateway to mastering cloud-native formats in your workflows.

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Safe Software

GenAI Risks & Security Meetup 01052024.pdf

lior mazor

The value of a flexible API Management solution for Open Banking Steve Melan, Manager for IT Innovation and Architecture - State's and Saving's Bank of Luxembourg Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The value of a flexible API Management solution for O...

apidays

Whatsapp Number Escorts Call girls 8617370543 Available 24x7 Navi Mumbai Call Girls Service Offer Genuine VIP Model Escorts Call Girls in Your Budget. Navi Mumbai Call Girls Service Provide Real Call Girls Number. Make Your Sexual Pleasure Memorable with Our Navi Mumbai Call Girls at Affordable Price. Top VIP Escorts Call Girls, High Profile Independent Escorts Call Girls, Housewife Women Escorts Call Girl, College Girls Escorts Call Girls, Russian Escorts Call girls Service in Your Budget.

Navi Mumbai Call Girls 🥰 8617370543 Service Offer VIP Hot Model

Deepika Singh

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

Zilliz

How to Troubleshoot Apps for the Modern Connected Worker

ThousandEyes

Destination Automation: Automating Processes in Modern Hipster Architectures

1. Automating Processes in Modern Hipster Architectures @berndruecker

2. Example @berndruecker

3. Example Payment Seat ReservationBooking Ticket Generation

4. Example @berndruecker sync

5. REST? Payment Seat ReservationBooking Ticket Generation REST REST REST REST

6. Weaknesses: Latency creep Payment Seat ReservationBooking Ticket Generation REST 300 ms 1150 + x ms 600 ms 250 ms

7. Weaknesses: Availabiliy erosion Payment Seat ReservationBooking Ticket Generation REST 99 % uptime 99 % uptime 99 % uptime 96 % uptime

8. And what about consistency? Payment Seat ReservationBooking Ticket Generation

9. What‘s hipster? Event-Driven Reactive Distributed Systems Microservices Agile Streaming Cloud-Native Eventual Consistency Kubernetes Serverless

10. Event Bus Event-Driven Choreography Payment Seat Reservation Ticket Generation Ticket booked Seat reserved Payment received Ticket generated

11. Event Bus Event-Driven Choreography Payment Seat Reservation Ticket Generation Ticket booked Seat reserved Payment received Ticket generated This is super flexible and de-coupled

12. Event Bus Event-Driven Choreography Payment Seat Reservation Ticket Generation Ticket booked Seat reserved Payment received Ticket generated We now need to reserve seats before collecting payment!

13. What we wanted Photo by Lijian Zhang, available under Creative Commons SA 2.0 License and P..19 / CC BY-SA 4.0 @berndruecker

14. The danger is that it's very easy to make nicely decoupled systems with event notification, without realizing that you're losing sight of that larger-scale flow, and thus set yourself up for trouble in future years. https://martinfowler.com/articles/201701-event-driven.html @berndruecker

15. The danger is that it's very easy to make nicely decoupled systems with event notification, without realizing that you're losing sight of that larger-scale flow, and thus set yourself up for trouble in future years. https://martinfowler.com/articles/201701-event-driven.html @berndruecker

16. The danger is that it's very easy to make nicely decoupled systems with event notification, without realizing that you're losing sight of that larger-scale flow, and thus set yourself up for trouble in future years. https://martinfowler.com/articles/201701-event-driven.html @berndruecker

17. How-to monitor event-driven processes? https://camunda.com/learn/webinars/ microservices-landscape-workflow-automation/

18. Orchestration Payment Seat ReservationBooking Ticket Generation This component orchestrates the others coordinates

19. Orchestration ≠ Synchronous Communication Payment Seat ReservationBooking Ticket Generation Kafka AMQP FaaS REST

20. A workflow engine can help Payment Seat ReservationBooking Ticket Generation REST

21. A workflow engine can help Payment Seat ReservationBooking Ticket Generation REST A workflow engine Keeps persistent state Can wait Can retry Can escalate Can compensate …

22. Warning: Contains Opinion

23. Berlin, Germany mail@berndruecker.io @berndruecker Bernd Ruecker Co-founder and Chief Technologist of Camunda

24. Demo

25. Architecture Payment Seat Reservation Ticket Generation REST Booking Java Spring Boot App Camunda Cloud Client Camunda Cloud Workflow Engine AMQP REST Workflow engine subscription FakeServices NodeJs App https://github.com/berndruecker/ticket-booking-camunda-cloud

26. Camunda Cloud is based on Zeebe (OSS workflow engine) http://zeebe.io/

27. But… @berndruecker sync

28. Can your company leverage your hipster architecture? Shutterstock You need to change business processes and customer experience!

29. @berndruecker happy case failure case Redesign your business process accordingly! Or some interface to poll for status Sync in happy case Async response

30. Summary • Synchronous call chains have weknesses • Event-driven choreography is not a magic cure • Orchestration • Helps to avoid chaos • Can be handled within one service (decentral) • Does not mean synchronous communication • To leverage a great hipster architecture you need to adjust business processes and customer experience

31. Thank you! @berndruecker

32. mail@berndruecker.io @berndruecker https://berndruecker.io https://medium.com/berndruecker https://github.com/berndruecker https://www.infoq.com/articles/events- workflow-automation Contact: Slides: Blog: Code: https://www.infoworld.com/article/3254777/ application-development/ 3-common-pitfalls-of-microservices- integrationand-how-to-avoid-them.html https://thenewstack.io/5-workflow-automation- use-cases-you-might-not-have-considered/

Destination Automation: Automating Processes in Modern Hipster Architectures

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a Destination Automation: Automating Processes in Modern Hipster Architectures

Similar a Destination Automation: Automating Processes in Modern Hipster Architectures (20)

Más de Bernd Ruecker

Más de Bernd Ruecker (19)

Último

Último (20)

Destination Automation: Automating Processes in Modern Hipster Architectures