Distributed Systems
Presentations about Distributed Systems
No Microservice Is an Island
Debugging Microservices: How Google SREs Resolve Outages
Debugging Microservices: How Google SREs Resolve Outages
Chick-Fil-A: Milking the Most Out of 1000's of K8s Clusters
Chick-Fil-A: Milking the Most Out of 1000's of K8s Clusters
Forced Evolution: Shopify's Journey to Kubernetes
Complex Event Flows in Distributed Systems
Efficient Fault Tolerant Java with Aeron Clustering
Canopy: Scalable Distributed Tracing & Analysis @Facebook
Canopy: Scalable Distributed Tracing & Analysis @Facebook
Modeling the Real World With Elixir/OTP
Next Gen Networking Infrastructure With Rust
Digital Publishing for Scale: The Economist and Go
Large Scale Architectures Panel
Large Scale Architectures Panel
Large Scale Architectures Panel
Large Scale Architectures Panel
Large Scale Architectures Panel
Large Scale Architectures Panel
Large Scale Architectures Panel
Heretical Resilience: To Repair is Human
Help! I Accidentally Distributed My System!
Help! I Accidentally Distributed My System!
Platforms at Twilio: Unlocking Developer Effectiveness
Interviews
No Microservice Is an Island
You worked at Capital One first and then switched over to Square. So what were you working on at Capital One?
At Capital One, I was working on the first layer of services that our mobile app and website hit. Any new mobile or web request would first reach the service owned by my team. This service implemented security and customisation logic and then made a server request to the broader Capital one ecosystem. Capital One has a lot of microservices. QCon: And what do you work on now at Square?
Was the stack you worked on at Capital One JVM based or Node?
There were a lot of people at Capital One who worked on Java, but I was working on Node there. At Square I am working on a ruby on rails monolith and we are working towards a microservices based architecture.
See more interviews
