RESTful Micro-service communication over AMQP

*
Proposal
Short Form
Intermediate

Excerpt

In the last several years, the web application has evolved from “monolith” to collection of APIs. In this presentation, we discuss the advantages, the difficulties, and some of the technologies involved in getting APIs to talk with each other successfully.

Description

In the last several years, the web application has evolved from “monolith” to collection of APIs. In this presentation, we discuss the advantages, the difficulties, and some of the technologies involved in getting APIs to talk with each other successfully.

For the past two years, Kavi Corporation has been aggressively building a new architecture using micro-services communicating asynchronously with each other over RabbitMQ. It is my intention to discuss the difficulties we ran into, how we resolved them, and benefits we achieved as a result with a focus on one-way and two-way inter-service communication.

Tags

soa, rabbitmq, amqp, flow, rest, async, micro, api, json-schema, pika, gevent, python

Speaking experience

This would be my first speaking engagement where participation was “really” voluntary. My previous experiences have been either internal to my employment or technical training aimed at individuals who were getting paid to learn what I was teaching. I am hoping that the topic being fresh for debate will help keep the discussion lively but also promise not to get upset if someone chooses to leave. At least, not while they are still in the room.

Speaker

  • Profile pic

    Serge Domkowski

    Kavi Corporation

    Biography

    I’ve been involved in making web software for about 22 years. I design and write code, talk about code (much to the delight of my wife), play with my son, ride my bicycle, root for the Timbers, drink beer, and once in a while sleep.