veyepar: Distributed microservices in the real world

Author(s):	Imraan Parker
Location	Baobab
Date	oct Thu 11	Days Raw Files
Start	09:15	First Raw Start	08:51
Duration	01:00:00	Offset	0:23:02
End	10:15	Last Raw End	10:21
Chapters	00:00 0:01:31 0:04:57 0:34:57 0:46:53 0:57:00
Total cuts_time	57 min.

https://za.pycon.org/talks/2-distributed-microservices-in-the-real-world/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Distributed_microservices_in_the_real_world.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

This talk is intended for anyone interested in deploying microservices in their environment. It examines what is involved in developing, deploying and maintaining a distributed microservices architecture. Moving from a monolithic architecture to a services oriented architecture has many benefits and tradeoffs that need to be addressed.

One has to consider whether to go with an off the shelf solution or build your own. When does it make sense to do the latter? Tasks like monitoring and debugging is more difficult with the added complexity that is inherent with a distributed system.

This first part of the talk reviews what needs to be considered when deciding to build applications on a distributed microservices architecture. Topics that will be covered include:
<ul>
    <li>Why choose a microservices architecture, and when not to?</li>
    <li>Objectives of a distributed services architecture</li>
    <ul>
        <li>Service presence</li>
        <li>Heartbeating</li>
        <li>Logging</li>
        <li>Security</li>
        <li>Reliability</>
        <li>Performance and Scalability</li>
        <li>Monitoring</li>
        <li>Troubleshooting</li>
        <li>Message contracts</li>
    </ul>
</ul>

The second part of the talk delves into the micorservices framework built and used by CareerJunction. It is an in house framework written in Python 3 (3.5+) which uses asyncio for nonblocking I/O and ZeroMQ as a concurrency networking library.

In simple terms, the framework implements a reliable service-oriented request-reply dialog between a set of client applications, a set of brokers and a set of worker applications.

The features of the framework include those discussed in the first part of the talk and will be showcased by coding and deploying a service. Above and beyond that, the following topics will be covered:
<ul>
    <li>Conceptual architecture</li>
    <li>Architecture goals</li>
    <li>Coding a service</li>
        <ul>
            <li>Creating and running a service</li>
            <li>Message contract parameters</li>
            <li>Exposing services via HTTP</li>
            <li>Scheduled Jobs</li>
        </ul>
</ul>

The last part of the talk examines the lessons learnt over the past few years, what to avoid and the benefits it brought not only to the IT team, but to the business as a whole.
Topics that will be covered include:
<ul>
    <li>IT benefits</li>
    <li>Business benefits</li>
    <li>What to avoid?</li>
</ul>

Comment:

production notes