Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. On average we deploy new code fifty times a day.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

SEPTEMBER 5, 2008

Youll learn how they pioneered the use of a lot of open source tools at new levels of scale, and even created quite a few more, that are essential scaling aids. Three of my favorite: memcached - an in-memory object caching system. Case Study: Continuous deployment makes releases n.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

JANUARY 4, 2009

This is true of most web application servers, caches like memcached, and all of the network infrastructure that connects them. For example, you might notice that caching gets a lot easier if you have good metadat about which queries are associated with the same entity. Case Study: Continuous deployment makes releases n.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JANUARY 12, 2009

The next time you needed to handle that page, you could take advantage of caching for excellent performance. There are also solutions to performance issues resulting from abstraction and runtime compilation (check out op-code caches such as APC). Case Study: Continuous deployment makes releases n.

PHP 166

PHP Software Review Ruby San Francisco 166