Reactive Systems - Managing Back Pressure

Hi All,

end of last year was kind of crazy. Too much to do and not enough time :).

Wanna get back into scheduling one of these every 2 month.

For the first one I want to try something new.

First I want to find a way to manage the "back pressure" more/better ... and no: I am not talking about the back pressure in a reactive system. I am talking about the pressure for time in the evening, Attending a meetup competes with a lot of other priorities (family, friends, sport, being on the phone to the US, ..., attending meetups :)).

Means ... this time around we are going to run the meetup at lunch time and ... we will run it as a series of lighting talks (four 15 min (max) talks with no Q&A (the Q&A will happen afterwards with the pizza and the beer (if you want one :)).

noon-1pm: Lighting Talks
1pm-2pm: Pizza, Beer, ..., Q&A

Let me know, what you think about the idea, the timing and the format.

We have 50 seats. First come, first served.

Talks are below.

Regards ... Roland (roland@gonitro.com)

---

“Streaming data to S3 with Akka-Streams" - Mikhail Girkin – Software Engineer, Gilt Groupe

Gilt has recently re-done one of their services. The main task was to upload couple of hundreds megabyte JSON file, containing the single collection, to S3. To avoid constructing of that thing in memory and then serialize it to JSON, which would require a lot of memory, we decided to stream the data in chunks, using Akka-Streams and S3 multipart upload API.

Mikhail Girkin is a Software Engineer with Gilt. He works in the Core Services Team, which owns a lot of back-end services in the very heart of Gilt - Users, Inventory, Search, etc.

---

“Unsuck the Future of Options – The Nitro Way” – Donal & Roland – Software Engineers, Nitro

To be reactive we want to perform our operation asynchronously (using Futures). As we all know in distributed systems things can go wrong. In this talk we want to show what Nitro is doing (on top of the Scalaz capabilities) to make this suck less.

Donal and Roland are passionate about writing good code and building scalable systems.

---

“Orchestration in Distributed Systems” – Paul Kelly – Software Engineer, Zalando

Complexities around orchestration in distributed systems and the problems we faced in designing our new customer data platform in Zalando. We had to give the facade of a synchronous system at the same time having everything async in the backend.

Paul Kelly, Co-Founder of the Dublin Software Craftsmanhip meetup. Passionate about everything that is distributed and reactive.