4 ms·
Things are not quite cut and dry operationally. Some places may have only a few hundred MB of data but they need really high availability and performance (proba
by devonkim 7y ago
Things are not quite cut and dry operationally. Some places may have only a few hundred MB of data but they need really high availability and performance (probably picked the wrong solution IMO but still...) which is better guaranteed hosting it yourself and perhaps even outside the cloud. Most places the availability of whatever a hosted solution provides is a better value than spending engineering hours to maintain these things. Devops / SRE folks are expensive compared to most other engineers that deliver features primarily.
My point is that a ton of companies (more for cultural reasons than business requirements IME) are so freaked out by any downtime in any way that they’re going to pay for an engineer to just maintain these things themselves.
- busterarm 7y agoThe only issue I have with this suggestion is that all of the situational awareness needed to _use_ Elasticsearch effectively is the same as is needed to _operate_ Elasticsearch effectively. If you're just spinning up something's defaults and throwing data in it, that bill is going to due eventually and it's probably going to be ugly.