Startup Lessons Learned

OCTOBER 5, 2009

In other words, a principled way to combine agility with stability. Imagine you hear from an engineer that they are worried that a certain payment subsystem is unreliable, and will therefore double-charge some customers. To a lot of smart engineers, that sounds crazy. Many problems are catastrophic only if allowed to fester.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

AUGUST 24, 2009

I have a question though- do you think that most content metrics (the ebook example you mentioned) should be developed by the "author" to target their specific data, or do you think there are opportunities for a new business vertical that give these tools directly to the creator. Case Study: Continuous deployment makes releases n.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JANUARY 4, 2009

For example, Friendster was famously vertically partitioned at one time in its growth curve. I normally recommend you just store this directory on your master database, but you could use a standalone vertical shard (or even a key-based partition!) This type of vertical partitioning sharding scheme wont work in most cases.

San Francisco 151

San Francisco Architecture Startup Database 151