Micro-services provide some benefits, but at what cost?

*
Accepted Session
Short Form
Advanced
Scheduled: Wednesday, June 22, 2016 from 10:00 – 10:45am in B302/303

Excerpt

Several years ago, there was an architectural paradigm shift toward "micro-services" and away from the "monolithic" application stack. A micro-service architecture comes with scalability and replaceability, among others, but is it worth the time and effort to build it? Is it worth debugging API calls gone wrong? If you're thinking about making this move, have already started, or have already deployed to production, this is an ideal venue to see what others are doing with micro-services.

Description

At Kavi Corporation, we have implemented and deployed a robust micro-service architecture on top of RabbitMQ from the ground up. This presented a plethora of challenges as well as some unforeseen treats.

In this presentation, we discuss the challenges we ran into implementing this architecture and how we dealt with them. We’ll also discuss the perceived long-term costs and benefits of the new architecture and how the new architecture changed how we think about and implement new functionality.

It is expected that participants are already familiar with the concept of a micro-service, REST, HTTP, and at least have heard of AMQP.

The slides for this presentation are available: http://www.domkowski.net/micro_services_benefits_costs/

Tags

soa, rabbitmq, amqp, flow, rest, async, micro, api, json-schema, pika, kombu, 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.

    Sessions

      • Title: Micro-services provide some benefits, but at what cost?
      • Track: Theory
      • Room: B302/303
      • Time: 10:0010:45am
      • Excerpt:

        Several years ago, there was an architectural paradigm shift toward “micro-services” and away from the “monolithic” application stack. A micro-service architecture comes with scalability and replaceability, among others, but is it worth the time and effort to build it? Is it worth debugging API calls gone wrong? If you’re thinking about making this move, have already started, or have already deployed to production, this is an ideal venue to see what others are doing with micro-services.

      • Speakers: Serge Domkowski

Leave a private comment to organizers about this proposal