Presentation name: A Beginner's Guide to Inter-Service Messaging
Speakers: Aurélien Bompard, Jeremy Cline
Description: Sending and receiving messages is a common task in software.
Fedora Infrastructure has many event-driven services, we'll discuss some of the problems we encountered and their solutions. Topics include:
- How to pick the right message protocol.
- How to design a "good message". How to recover when you inevitably
don't design a "good message" or when the meaning of the word "good" changes. - Networking: centralized or decentralized?
- How to deal with lost messages. Is it bad? Should you care?
Each topic contains plenty of concrete examples from Fedora Infrastructure.
At the end of this talk, the audience should be well-equipped to not repeat
the mistakes we made and instead go make new and interesting mistakes.
This talk does not require prior knowledge of any message protocols.
Modern, scalable and powerful
Productivity first and foremost
Loved by business, devs and IT
Build and orchestrate integration services, expose new or existing APIs, either cloud or on-premise, and use a wide range of connectors, data formats and protocols.
Zato facilitates intercommunication across applications and data sources spanning your organization's business or technical boundaries and beyond, enabling you to access, design, develop or discover new opportunities and processes.
NATS Server is a simple, high performance open source messaging system for cloud native applications, IoT messaging, and microservices architectures.
Jolokia is remote JMX with JSON over HTTP.
It is fast, simple, polyglot and has unique features. It's JMX on Capsaicin.
Jolokia is a JMX-HTTP bridge giving an alternative to JSR-160 connectors. It is an agent based approach with support for many platforms. In addition to basic JMX operations it enhances JMX remoting with unique features like bulk requests and fine grained security policies.
One of the most common questions I’m asked to cover when I discuss software architecture topics is the difference between the various application messaging protocols that exist today—issues like how and why the protocols came about, and which one should be used in a particular application.