// tag

#scalability

5 posts
05
programming

Building Scalable Performant And Cheap Distributed Applications Part 1

With this post, I'd like to start a series of *DevOps*-related conversations about building distributed applications (read: common web-apps). Folks running enterprise application use different technologies and are hosted across a range of cloud providers, and yet are often faced with very similar problems.

2016.05.05
04
programming

Scaling Web Applications On Postgresql A Walkthrough Presentation

In this exciting and informative talk, presented at PgConf Silicon Valley 2015, Konstantin cut through the theory to deliver a clear set of practical solutions for scaling applications atop PostgreSQL, eventually supporting millions of active users, tens of thousands concurrently, and with the application stack that responds to requests with a 100ms average.

2015.11.27
03
programming

Twelve Step Program For Scaling Web Applications On PostgreSQL

In this exciting and informative talk, presented at PgConf Silicon Valley 2015, Konstantin cut through the theory to deliver a clear set of practical solutions for scaling applications atop PostgreSQL, eventually supporting millions of active users, tens of thousands concurrently, and with the application stack that responds to requests with a 100ms average. He will share how his team solved one of the biggest challenges they faced: effectively storing and retrieving over 3B rows of 'saves' (a Wanelo equivalent of Instagram's likes or Pinterest's pins), all in PostgreSQL, with highly concurrent random access.

2014.03.20
02
programming

The Case For Vertical Sharding

In this post I share the story of overcoming a massive scalability bottleneck from too many writes ino the Analytics database table used for Event collection, using Vertical Sharding.

2013.02.04
01
programming

The Big Switch How We Rebuilt Wanelo From Scratch And Lived To Tell About It

In this post we share the details of what we did and what we learned, in case someone out there ever finds themselves in a similar situation, weighing the risks of either working with a legacy stack or going full steam ahead with a rewrite.

2012.09.13