Distributed architecture concepts I learned while building a large payments system


52 bookmarks. First posted by aebraddy april 2018.


Distributed architecture concepts I learned while building a large payments system
from twitter
may 2018 by pfleidi
I joined Uber two years ago as a mobile software engineer with some backend experience. I ended up building the payments functionality in the app - and rewriting the app on the way. Afterwards, I ended up moving into engineering management, heading up the team itself. via Pocket
IFTTT  Pocket 
april 2018 by tkhwang
I joined Uber two years ago as a mobile software engineer with some backend experience. I ended up building the payments functionality in the app - and rewriting the app on the way. Afterwards, I ended up moving into engineering management, heading up the team itself.
ifttt  tfav  twitter  getpocket 
april 2018 by linkt
via Pocket - Distributed architecture concepts I learned while building a large payments system - Added April 18, 2018 at 03:46AM
april 2018 by mikele
I joined Uber two years ago as a mobile software engineer with some backend experience. I ended up building the payments functionality in the app - and…
from instapaper
april 2018 by chrispoole
I joined Uber two years ago as a mobile software engineer with some backend experience. I ended up building the payments functionality in the app - and rewriting the app on the way. Afterwards, I ended up moving into engineering management, heading up the team itself.
IFTTT  Pocket 
april 2018 by deepblue
A share-worthy list of challenges you may face if you develop distributed systems
DistributedSystems  from twitter_favs
april 2018 by tjweir
Nice write-up of some of the issues in distributed systems with a lot of relevant links:
from twitter
april 2018 by codesilverback
I joined Uber two years ago as a mobile software engineer with some backend experience. I ended up building the payments functionality in the app - and…
from instapaper
april 2018 by elnaril
The usual vocabulary of describing programming practices - things like variables, interfaces, calling methods - all assume single machine systems. When talking about distributed systems, we need to use a different set of approach. A common way of describing these systems is following the actor model, where we think about the code in terms of communication. This model is popular, as it matches the mental model that we would think of, for example, when describing how people communicate in an organization. Another, also popular way of describing distributed systems is CSP - communicating sequential processes.

The actor model is based on actors sending messages to each other and reacting to them. Each actor can do a limited set of things - create other actors, send messages to others or decide what to do with the next message. With a few simple rules, complex, distributed systems can be described well, which can also repair themselves, after an actor crashes. For a short overview, I recommend the article The actor model in 10 minutes by Brian Storti. Many languages have implemented actor libraries or frameworks. For example, at Uber, we use the Akka toolkit for some of our systems.
messaging  scalability  erlang  scala  reactive 
april 2018 by janpeuker