A Year of MongoDB

Re:A Year of MongoDB by cobbzilla on Friday May 10, 2013 @02:28PM (#5687848)

You make a VERY big "if" in your first sentence, one that (admittedly anecdotally) I've very rarely seen hold true in tech companies. Much more often, the MVP becomes the product, and all those shortcuts and poor design decisions come back to kill your productivity when it becomes necessary to refactor foundational tech/designs that have metastasized throughout the codebase.

I am curious if this is other folks' experience as well, or do you actually throw out the MVP and start all over at some point? If so, at what point do you make the break?

[ Parent | on HN ]

Re:A Year of MongoDB by mrgreenfur on Friday May 10, 2013 @11:46PM (#5689647)

In real life, you are totally true. The initial test that succeeds becomes/continues to be the real product. I agree with the parent poster that Mongo is awesome for testing, if not awesome for scale. I think the point here is that tech co-founders/leads need to make it clear that this is a debt that will need to be paid if things take off.

[ Parent | on HN ]

Re:A Year of MongoDB by danbmil99 on Saturday May 11, 2013 @01:08AM (#5689760)

If NoSql's speed and flex gets you to MVP, and MVP gets you traction, then all the hell you may go through to rearchitect for SQL is probably worth it.

Premature scalability is as dumb as premature optimization and premature generality.

[ Parent | on HN ]

Re:A Year of MongoDB by daurnimator on Friday May 10, 2013 @03:09PM (#5688072)

MVP is used to get funding; which extends your runway so you have time to make your product correctly.

[ Parent | on HN ]