|
|
|
|
|
|
by ericd
1656 days ago
|
|
|
The capital costs are very easy to make back. For us, the payback period was <1 year, and our machines provided unbeatable performance with very good transparency into issues, which made it relatively easy to track down issues. Dedicated machines are really, really powerful now, and you can do with a few what it used to take racks. I feel like the perception of “it’s too hard” or “it’s actually more expensive” is subtly encouraged and reinforced by the myriad companies that stand to benefit - all those hosted services, the cloud providers, etc. And they make it easy for individual employees to appear more productive, but in exchange for costing their companies much more in the long run, and introducing a lot of inter-service latency and complexity. Misaligned incentives. The major exception for us is S3, scaling storage seems like it would suck terribly. |
|
|
Not just companies. Web developers love the complexity of their stack. Some monolith written in native performant language and put on a decent hardware can cover needs of the most reasonable size business. This simple fact makes them very uncomfy when presented. Many of them would not be even aware that such things are possible. They'd rather be spoon fed by the likes of the Amazon telling them how to develop their wares. The fact that the more inefficient their software is the more money said Amazon will make is ignored. They'd invent all kinds of largely BS arguments to avoid going a simpler route. One can just read numerous articles on HN describing "our stack". On a client site they have this React atrocity. Sure this thing works well for orgs the size of FB. But they're not FB and never will be.