Startup Lessons Learned
JULY 29, 2009
Outside the world of hypothetical examples, its more important to make continual progress than to build the ultimate design. For example, at a previous virtual world company , we spent years developing an architecture to cope with millions of simultaneous users. That’s what Just-in-time Scalability is all about. One last thought.
Startup Lessons Learned
NOVEMBER 29, 2008
and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. For the past couple of years Ive used a question that I once was asked in an interview, in which you have the candidate produce an algorithm for drawing a circle on a pixel grid. I remember answering "What security model?"
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
NOVEMBER 13, 2008
Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
JANUARY 4, 2009
Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. More common is to use a one-way hashing algorithm to map the data to be accessed to one of the shards that store it. Support multiple sharding schemes. Easy to understand.
Startup Lessons Learned
JANUARY 30, 2009
Build a world-class technology platform, with patent-pending algorithms and the ability to scale to millions of simultaneous users. Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Even a great architecture becomes inflexible.
Expert insights. Personalized for you.
168 
Let's personalize your content