apidays Paris 2024 - Governance of Event-Driven Distributed Systems, Omid Eidivandi, Groupe La Centrale

Dec 27, 2024Download as PPTX, PDF0 likes79 views

Governance of Event-Driven Distributed Systems Omid Eidivandi, Solution Architect at Groupe La Centrale apidays Paris 2024 - The Future API Stack for Mass Innovation December 3 - 5, 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/

Governance in Distributed
Event-Driven Systems

Distributed Systems are
Hard
Design Vigilantly

Distributed Microservices
Api
Broker
Api
Broker
Api
Broker
Api
Broker
Api
Broker
Api
Broker
Api
Broker
Api
Broker
Api
Broker
Api
Broker
Api
Broker
Api
Broker

Unintentional Complexities
● State Inconsistency
● Coordinations Difficulties
● Lack of Observability
● Quality Bottlenecks
● Lack of Autonomy

Lack of defined context
External
Gateway
External
Pub/Sub
Inteface
External
Queue
External
Stream
Inteface
Inteface External
Gateway
External
Pub/Sub
Inteface
External
Queue
External
Stream
Inteface
Inteface

Chang
es
Catalo
g
Contr
act
Structure & shape

Standards Paths
Tools
Low = Standard
Education
= Golden paths
Services = Tooling

follow up identifier
time
subject
source
data contenttype
id
type
Omid
confidential
2024/03/11
international
sender
Cloudevents
Spec
data
letter
Routing
Process

Community
standards
Cloudevents
Asyncapi
Arazzo
OpenApi
XRegistry

Request-Reply
Producer
Requester
Receiver
Process

Categories
SDK
O
b
s
e
r
v
a
b
i
l
i
t
y
Testing
Blueprints
A
u
t
o
m
a
t
i
o
n Development
Collaboration
Quality Analysis
Experim
entation

APIs have become ubiquitous as a way of exposing the capabilities of the enterprise both internally and externally. However, are APIs alone enough? There is a strong resurgence in interest in asynchronous communication and event driven architecture. Applications want to receive events immediately so they can respond in real time, and furthermore they also want the benefit of being decoupled from the availability and performance characteristics of the systems providing that data. However, whilst the way that APIs are socialized, exposed, versioned etc. is well matured in the form of API management technology. We are now on the cusp of seeing first class support for event endpoint management to provide the same sophistication for discovering, exposing and consuming events.

apidays LIVE Paris 2021 - Event driven design and serverless by Omid Eidivand...apidays

Should we manage events like APIs? | Alan Chatt and Kim Clark, IBMHostedbyConfluent

APIs have become ubiquitous as a way of exposing the capabilities of the enterprise both internally and externally. However, are APIs alone enough? There is a strong resurgence in interest in asynchronous communication and event driven architecture. Applications want to receive events immediately so they can respond in real time, and furthermore they also want the benefit of being decoupled from the availability and performance characteristics of the systems providing that data. However, whilst the way that APIs are socialised, exposed, versioned etc. is well matured in the form of API management technology. We are now on the cusp of seeing first class support for event endpoint management to provide the same sophistication for discovering, exposing and consuming events.

WSO2Con Asia 2014 - Building the API-Centric EnterpriseWSO2

WSO2 helps businesses become API-centric by providing tools and infrastructure to support the entire API lifecycle from creation to management to hosting. The platform supports developing RESTful and SOAP APIs and hosting them scalably. It also offers an API management solution, tools for creating and testing APIs, and capabilities for collecting data from user interactions and performing analytics. WSO2 aims to make user interactions with apps and APIs as smooth as possible through features like single sign-on, app marketplaces, and support for hybrid cloud deployments.

API Gateways are going through an identity crisisChristian Posta

API Gateways provide functionality like rate limiting, authentication, request routing, reporting, and more. If you've been following the rise in service-mesh technologies, you'll notice there is a lot of overlap with API Gateways when solving some of the challenges of microservices. If service mesh can solve these same problems, you may wonder whether you really need a dedicated API Gateway solution? The reality is there is some nuance in the problems solved at the edge (API Gateway) compared to service-to-service communication (service mesh) within a cluster. But with the evolution of cluster-deployment patterns, these nuances are becoming less important. What's more important is that the API Gateway is evolving to live at a layer above service mesh and not directly overlapping with it. In other words, API Gateways are evolving to solve application-level concerns like aggregation, transformation, and deeper context and content-based routing as well as fitting into a more self-service, GitOps style workflow. In this talk we put aside the "API Gateway" infrastructure as we know it today and go back to first principles with the "API Gateway pattern" and revisit the real problems we're trying to solve. Then we'll discuss pros and cons of alternative ways to implement the API Gateway pattern and finally look at open source projects like Envoy, Kubernetes, and GraphQL to see how the "API Gateway pattern" actually becomes the API for our applications while coexisting nicely with a service mesh (if you adopt a service mesh).

Securing, Governing, and Protecting Your Office 365 InvestmentsChris Bortlik

How to Build, Manage, and Promote APIsWSO2

The document discusses WSO2's API Management Platform, which provides tools for publishing, documenting, securing, analyzing usage of, and monetizing APIs. It highlights key features like API publishing, documentation, analytics, security via OAuth, and a roadmap including additional collaboration and monetization features. The platform is based on WSO2's middleware and aims to provide a minimum viable product in its first release with additional capabilities over time based on user requirements.

API, Integration, and SOA ConvergenceKasun Indrasiri

This document provides an overview of APIs, API management, integration, and API security. It discusses why organizations adopt APIs to accelerate mobile app development, foster reuse, and allow external developers to innovate. The document outlines components of API management like the API gateway and developer portal. It also discusses how SOA, ESB, and APIs can converge in the API facade pattern to provide simple interfaces to complex systems. The presentation demonstrates this pattern using WSO2 API Manager and ESB and discusses API security techniques like OAuth for identity delegation.

Building an API Centric SOA WSO2

This document discusses how the WSO2 platform can help businesses build an API-centric service-oriented architecture (SOA). It describes WSO2 tools for creating, hosting, managing, and monitoring APIs. It outlines how the platform supports API development, collaboration with developers, capturing usage data, ensuring smooth user interactions, and scalable deployment including in hybrid clouds. The overall message is that WSO2 provides a full-stack solution to help businesses transition to an API-centric connected digital model.

Public v1 real world example of azure functions serverless conf london 2016 Yochay Kiriaty

Yochay Kiriaty gave a presentation on serverless computing using Microsoft Azure services. He began by defining serverless and its benefits like event-driven scaling, sub-second billing, and abstraction of servers. He then demonstrated several serverless patterns using Azure Functions for tasks like processing data from Blob storage, responding to API requests, and replicating logs between data centers. Throughout the presentation, he emphasized best practices for building serverless applications including designing functions to do single tasks, finish quickly, be stateless and idempotent.

Portal as UI of SOAAndrew Petro

Shine a Light with Prism (the Composite Application Guidance for WPF and Silv...Dave Bost

Prism is a library that provides guidance and tools for building composite client applications in WPF and Silverlight. It supports separating an application into modules and composing them at runtime. Prism provides features like module discovery, region-based UI composition, and an event aggregator for loose coupling. The library includes documentation, code samples, and a reference implementation to help developers build these types of applications while targeting both desktop and RIA scenarios.

Design and Develop Serverless Applications as Set-PiecesSheenBrisals

The emergence of microservices made us rethink how we built business applications. It led us to the migration of complex monolith applications to countless microservices. The cloud adoption and the suitability of the container services helped to revolutionize microservices. Amidst this adoration for microservices came serverless, the next evolution of the cloud. Serverless brought deeper granularity with its technology offering. It tested our thinking, shifted our minds, and questioned us the way we’ve been building microservices. The agility of event-driven computing and the granularity of serverless allows us to break traditional microservices into multiple pieces. In this talk, we will see how cloud and serverless help us build those pieces in isolation to achieve acceleration in our modern application development process.

Permit to Cloud, Landing with confidence in AzureMike Benkovich

Convergence of Integration and Application DevelopmentKim Clark

The document discusses the convergence of integration and application development. It notes that in the past, integrations and applications were developed separately by different teams. However, nowadays application developers regularly perform integration tasks like defining and exposing APIs when building applications. Integration capabilities have become part of the standard toolkit for application developers. The document argues this trend is resulting in a new generation of powerful applications that are integration-enabled.

MuleSoft Surat Meetup#39 - Pragmatic API Led ConnectivityJitendra Bafna

This document provides an overview of a MuleSoft meetup on API-led connectivity. It includes introductions of the organizers and agenda. The agenda discusses designing RESTful reusable APIs, how API-led fits into architecture, and an example use case. It also covers when system APIs may be useful, such as to address security issues, improve error handling, reduce complexity, and improve third party APIs. The document emphasizes that core or business APIs are the essential layer and other layers like system or process APIs are optimizations that need only be built if necessary.

apidays Hong Kong - Event API Products: Maximizing the Value of Your Event-Dr...apidays

apidays Hong Kong 2022 - API-First Digital Transformation & Platform Economy August 24 & 25, 2022 Event API Products: Maximizing the Value of Your Event-Driven Architecture Giri Venkatesan, Developer Advocate at Solace ------------ 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/ Deep dive into the API industry with our reports: https://www.apidays.global/industry-reports/ Subscribe to our global newsletter: https://apidays.typeform.com/to/i1MPEW

Internet of Things and Edge Compute at Chick-fil-ABrian Chambers

OUGN 2018 - Chatbot and the need to integrateJon Petter Hjulstad

The document discusses chatbots and the need to integrate them. It provides an overview of chatbot types and maturity levels. It also discusses various ways chatbots can be integrated, including through backend systems, channels, and intelligence providing systems. The document notes that chatbots need APIs to external systems to function properly and should have limited scope. It shares Oracle's offerings for chatbot platforms, tools, and services to enable integrations.

SVCC Microservices: Decomposing Applications for Testability and Deployability Chris Richardson

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

Agile integration architecture in relation to APIs and messagingKim Clark

This document discusses agile integration architecture from three perspectives: application integration, APIs, and messaging. It outlines how traditional centralized integration approaches are moving to more decentralized models with fine-grained deployments, application autonomy, and cloud-native implementations. APIs are shifting from system-centric to consumer-centric exposure, while messaging is evolving from self-managed to platform-managed infrastructure. Microservices require both asynchronous communications via events and synchronous APIs to fully decouple components. Agile integration architecture enables independent, scalable, and resilient digital applications and services.

[WSO2Con EU 2017] Microservice Architecture (MSA) and Integration MicroservicesWSO2

Sharepoint 2013 applied architecture from the field (v2)Tihomir Ignatov

The document provides an overview of SharePoint 2013 architecture from a consultant's perspective. It discusses the role of the IT architect and considerations for SharePoint infrastructure decisions and application development. Key points covered include: - The IT architect's responsibilities in requirements engineering, design, and solution governance. - Factors for SharePoint infrastructure like servers, capacity planning, and skills. - Options for developing SharePoint apps, whether cloud-hosted, on-premises, or a hybrid. - Recommended SharePoint topologies based on availability, scalability and workload.

Detecting Malicious Cloud Account Behavior: A Look at the New Native Platform...Priyanka Aash

Until recently, major public cloud providers have offered relatively basic toolsets for identifying suspicious activity occurring inside customer accounts that may indicate a compromise. Some organizations have invested significant resources to build their own tools or have leveraged industry vendor offerings to provide this visibility. The reality is, that barrier has meant that a large number of organizations haven't dedicated those resources to this problem and therefore operate without sufficient detection and response capabilities that monitor their cloud accounts for compromise. Amazon Web Services, Google Cloud Platform, and Microsoft Azure have recently launched a new set of native platform threat and anomalous behavior detection services to help their customers better identify and respond to certain issues and activities occurring inside their cloud accounts. From detecting crypto-currency mining to identifying bot-infected systems to alerting on suspicious cloud credential usage to triggering on cloud-specific methods of data exfiltration, these new services aim to make these kinds of detections much easier and simpler to centrally manage. But what new and unique insights do they offer? What configuration is required to achieve the full benefits of these detections? What types of activities are not yet covered? What attack methods and techniques can avoid detection by these systems and still be successful? What practical guidelines can be followed to make the best use of these services in an organization? Follow along as we attempt to answer these questions using practical demonstrations that highlight the real threats facing cloud account owners and how the new threat detection capabilities perform in reducing the risks of operating workloads in the public cloud.

Apidays Paris 2023 - API Security Challenges for Cloud-native Software Archit...apidays

Apidays Paris 2023 - Software and APIs for Smart, Sustainable and Sovereign Societies December 6, 7 & 8, 2023 API Security Challenges for Cloud-native Software Architects Pierre Versali, Cloud-native Software Architect | Principal Consultant at Devoteam ------ 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 Paris 2024 - AI-Enhanced API Documentation Bridging Knowledge Gaps an...apidays

AI-Enhanced API Documentation : Bridging Knowledge Gaps and Elevating Developer Experience Saheed Abiola Lasisi, Executive Director, Principal API Architect , JPMorgan Payments at JP Morgan Chase & Co. apidays Paris 2024 - The Future API Stack for Mass Innovation December 3 - 5, 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 Paris 2024 - AI Adoption - Engaging Minds, Developing Skills, Deliver...apidays

AI Adoption : Engaging Minds, Developing Skills, Delivering Results Yannick Tremblais, AI/IT Innovation Manager at Groupe Rocher apidays Paris 2024 - The Future API Stack for Mass Innovation December 3 - 5, 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/

More Related Content

Similar to apidays Paris 2024 - Governance of Event-Driven Distributed Systems, Omid Eidivandi, Groupe La Centrale (20)