These are chat archives for jdubray/sam
@formido thanks for your firebase comments!
I don't think it's very easy to predict how hard it will be for a system to handle different scales, so I'm not going to spend a ton of time making bad guesses
for experiments, MVPs and POCs that's nearly always true.. but in other cases I plan ahead and define the constraints of the final product. For example I'll need plenty of storage, and that's pretty much expensive with Firebase (and google cloud in general), but I already found an hybrid approach to leverage both a firebase storage and an external storage at a lower cost
I'm also OK with running multiple DBs, use the best tool for the job
yes, that's the usual case in a micro-service architecture.. in the end I'll use a combination of document storage and RDBMS (postgres). On a side note, I'm not very fond of nosql, as I see it more like a trend among young devs. I'm pretty much convinced that no more than 20-30% of usages I see in the wild are valid, while the rest are more related to the "no(I'm too lazy to study)SQL" movement...