Remove Continuous Deployment Remove Engineer Remove Vertical Remove Webinar
article thumbnail

The curse of prevention

Startup Lessons Learned

Imagine you hear from an engineer that they are worried that a certain payment subsystem is unreliable, and will therefore double-charge some customers. If we’re practicing continuous deployment, we can be confident that we’ll be able to rush an emergency fix into production without risking introducing further problems.

article thumbnail

Lessons Learned: Sharding for startups

Startup Lessons Learned

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.

article thumbnail

Marching through quicksand

Startup Lessons Learned

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.