top of page


Share on:
Asset 14icon.png
Asset 39icon.png
Asset 12icon.png

Nir Orman, Innovation Lover, Technology Geek, Serial Hackathon Winner.
In her work, Nir builds complex software systems, from the initial architecture decisions to the smallest implementation details, bringing it all the way to the customers.
In her free time she enjoys satisfying her endless thirst for professional and personal growth, and is also a mentor for women in tech.
Currently Engineering Manager@ Wix, before that Full Stack Team Leader at D-ID, a startup developing Computer Vision Deep Learning algorithms.

Nir Orman

Software Engineer
Asset 12icon.png
Asset 1TWITTER.png
Asset 39icon.png
Asset 17icon.png
English, Hebrew
Asset 7TWITTER.png
Tel Aviv, Israel
Asset 7TWITTER.png
Can also give an online talk/webinar
Paid only. Contact speaker for pricing!


Distributed Workers System for Lifting Any Heavy Algorithm

Software Engineering, Backend

Asset 12SLIDES.png
Asset 21talk.png
Asset 11SLIDES.png

You’d think APIs are simple.
You send a request and get back a response, what’s so complicated about that?
But sometimes the response takes too long to compute.
Google recommends you aim for a response time lower than 200 milliseconds, everything over half a second is an issue.
For example If you developed a Deep Learning algorithm and you want to share it with the world, you need to develop an API exposing it. But you obviously can’t compute the algorithm for 10 minutes before returning a response from the API. No user will wait that long, and you most certainly should not use an expensive GPU that has a great compute power in order to serve the API requests.
In this talk we’ll explore tools for solving this problem and building a scalable system.
We will get to know Celery, which is an open-source, asynchronous, distributed task queue. It will save you blood, sweat and tears when trying to set up a distributed workers system to perform tasks for your API.

Asset 1icon.png

Distributed Workers System for Lifting Any Heavy Algorithm







Go to lecture page

bottom of page