4 ms·
The reason a lot of people chose something out of Google book is not because they get confused about not being Google (which is actually a pretty insulting and
by jstummbillig 5y ago
The reason a lot of people chose something out of Google book is not because they get confused about not being Google (which is actually a pretty insulting and also idiotic assumption), but because they wanna benefit from Google putting a stamp of approval on certain tech and pouring resources into it. Tech changes fast, disappears quickly, there is a lot of it out there, most of it is readily available, and so we make use whatever signals we can gather to navigate this space.
Which doesn't mean that you can close your eyes and pick whatever tech for whichever use case (duh?) but Amazon or Google doing it differently in the past or a company not being as big as them is certainly not a great argument for not using parts of their stack.
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]
- alecbz 5y agoBut you do need to have _an_ argument for why using their tech is good. > benefit from Google putting a stamp of approval on certain tech and pouring resources into it On its own this is still not a great argument; Googling pouring resources into solving a problem does not help you unless you _also_ have that problem.
- staticassertion 5y agoChoosing technology that's battle tested at scale and under crazy load seems extremely reasonable. Just from a "I need this thing not to have a shitload of bugs" perspective. If you were choosing between two libraries, and one was used by 5 people and one was used by 5 million, it'd be hard to go with the one that is used by 5 people even if it is a better fit for the problem.
- alecbz 5y agoSure, but I think this is not the shape of situation people are generally facing when we say "you're not Google". E.g., often you see choices between NoSQL-esque solutions like BigTable, Dynamo, etc. and traditional relational DBs.
- deleted 5y ago[deleted]