11–20 of 38 posts
"MongoDB is how we store things" Is mongodb really a good solution for storing things? IIRC one concern about coinbase (YC) is that they used mongodb for storing financial information.
That's a hell lot of things to change, break, go down, lose your data, start charging ridiculous prices, be discontinued, etc... I'm all for SaaS and not re-inventing wheels, but I'd be nervous if I had to rely on so many external dependencies.
I was hoping for a slightly higher-level look at what problems not to solve. It seems that Collections.me solves a solved problem - convenient online storage. It iterates a bit on it, but you seem to be building something that is largely a pile of already-solved problems, both in its implementation and use cases. Just my opinion, of course, and that is how many services advance, but I thought I'd voice it in light of…
The OP doesn't really talk about "solved problems", it talks about the companies core competencies.
That's a lot more 3rd party services than most use - do you find major differences in reliability?
That's a hell lot of things to change, break, go down, lose your data, start charging ridiculous prices, be discontinued, etc... I'm all for SaaS and not re-inventing wheels, but I'd be nervous if I had to rely on so many external dependencies.
Presumably when any of those things happen, that's when you bring it in-house.
Earlier quoted context omitted.
Presumably when any of those things happen, that's when you bring it in-house.
I don't think that's a viable solution. Some of these are quite complicated and replicating them in-house is not something you just up and do in a short time. That tactic might expose you to significant downtime.
most of these services wouldn't be around if they had taken that advice ;)
I've spent almost a year on it and don't think I'm going to take their advice if it's all the same to them.