Pinterest Architecture Update - 18M Visitors, 10x Growth, 12 Employees, 410 TB
1–10 of 88 posts
Re: Pinterest Architecture Update - 18M Visitors, 10x Growth, 12 Employees, 410 TB
#2They have a very Interesting Stack as seen on Quora[1]:
-Python + heavily-modified Django at the application layer
-Tornado and (very selectively) node.js as web-servers.
-Memcached and membase/redis for object and logical-caching
-RabbitMQ as a message queue.
-Nginx, HAproxy and Varnish for static-delivery and load-balancing.
-Persistent data storage using MySQL.
-MrJob on EMR for map-reduce.
[1] http://www.quora.com/Pinterest/What-technologies-were-used-t...
Re: Pinterest Architecture Update - 18M Visitors, 10x Growth, 12 Employees, 410 TB
#3They have a very Interesting Stack as seen on Quora[1]: -Python + heavily-modified Django at the application layer -Tornado and (very selectively) node.js as web-servers. -Memcached and membase/redis for object and logical-caching -RabbitMQ as a message queue. -Nginx, HAproxy and Varnish for static-delivery and load-balancing. -Persistent data storage using MySQL. -MrJob on EMR for map-reduce. [1] http://www.quora.co…
Pardon my ignorance: what is interesting about Pinterest stack?
I think by now most startups, YC or not, in Silicon Valley will pretty much have a similar setup:
1) Choose the main web-stack (Rails or Django)
2) Choose the API framework (node.js, or something else)
3) Memcached for caching (or some NoSQL)
4) A message queue (ZeroMQ, RabbitMQ, or something ...)
5) nginx, HAProxy, Varnish, (or similar technology)
6) Hadoop for map-reduce (only if you need to go that path...)
Re: Pinterest Architecture Update - 18M Visitors, 10x Growth, 12 Employees, 410 TB
#4It's cool that we're seeing companies reach 1 billion USD valuations with 12 employees.
Re: Pinterest Architecture Update - 18M Visitors, 10x Growth, 12 Employees, 410 TB
#5It's cool that we're seeing companies reach 1 billion USD valuations with 12 employees.
It will be even cooler when we see companies reach 1 billion USD net-income with 12 employees.
Re: Pinterest Architecture Update - 18M Visitors, 10x Growth, 12 Employees, 410 TB
#6They have a very Interesting Stack as seen on Quora[1]: -Python + heavily-modified Django at the application layer -Tornado and (very selectively) node.js as web-servers. -Memcached and membase/redis for object and logical-caching -RabbitMQ as a message queue. -Nginx, HAproxy and Varnish for static-delivery and load-balancing. -Persistent data storage using MySQL. -MrJob on EMR for map-reduce. [1] http://www.quora.co…
Pardon my ignorance: what is interesting about Pinterest stack? I think by now most startups, YC or not, in Silicon Valley will pretty much have a similar setup: 1) Choose the main web-stack (Rails or Django) 2) Choose the API framework (node.js, or something else) 3) Memcached for caching (or some NoSQL) 4) A message queue (ZeroMQ, RabbitMQ, or something ...) 5) nginx, HAProxy, Varnish, (or similar technology) 6) Ha…
Not trying to be a nit-pick, but wanted to mention that ZeroMQ is not a message queue in the sense that RabbitMQ (and Kestrel, Beanstalkd, SQS, etc) is. It's a socket library that you'd use to implement those technologies.
And while this is truly unimportant, my experience with bay area startup stacks is that Redis has very thoroughly supplanted Memcached for most use cases. Though most still have a memcached cluster or two.
That being said: 90% of software development in this world isn't done at tech companies and startups. So from that perspective, that stack is interesting.
Re: Pinterest Architecture Update - 18M Visitors, 10x Growth, 12 Employees, 410 TB
#7They have a very Interesting Stack as seen on Quora[1]: -Python + heavily-modified Django at the application layer -Tornado and (very selectively) node.js as web-servers. -Memcached and membase/redis for object and logical-caching -RabbitMQ as a message queue. -Nginx, HAproxy and Varnish for static-delivery and load-balancing. -Persistent data storage using MySQL. -MrJob on EMR for map-reduce. [1] http://www.quora.co…
Pardon my ignorance: what is interesting about Pinterest stack? I think by now most startups, YC or not, in Silicon Valley will pretty much have a similar setup: 1) Choose the main web-stack (Rails or Django) 2) Choose the API framework (node.js, or something else) 3) Memcached for caching (or some NoSQL) 4) A message queue (ZeroMQ, RabbitMQ, or something ...) 5) nginx, HAProxy, Varnish, (or similar technology) 6) Ha…
I agree. I think the interesting aspect is that they built a service that serves an impressive number of users on fairly common technologies.
There isn't anything very revolutionary about their stack by itself. FB didn't buy them for their technology... they could have replicated that on their own.
If they want to be talking about infrastructure, the story of using common tools at high volume is more interesting that just what tools...
Re: Pinterest Architecture Update - 18M Visitors, 10x Growth, 12 Employees, 410 TB
#8It's cool that we're seeing companies reach 1 billion USD valuations with 12 employees.
To be fair the employee number is as of last December, and they've grown quite a bit since then.
Re: Pinterest Architecture Update - 18M Visitors, 10x Growth, 12 Employees, 410 TB
#9It's cool that we're seeing companies reach 1 billion USD valuations with 12 employees.
To be fair the employee number is as of last December, and they've grown quite a bit since then.
Based off of their team page, Pinterest is up to 31 employees.
Re: Pinterest Architecture Update - 18M Visitors, 10x Growth, 12 Employees, 410 TB
#10Those kind of articles makes me feel so stupid. Even though those technologies are ready to go, making them work smoothly without any interruption always seems hard to me. I believe, there has to be lots of tips and trick. ( in other words you have to be experienced with all them or I am very lazy) I was wondering if any common receipt exists or if there is someone who can answer my couple of high scalability questions.