Re:What software engineers can learn from the rapid collapse...
by irjustin on Thursday April 07, 2022 @10:59PM
(#30952878)
Exactly, the cost of turning on additional servers is measured in ~US$100's/mth vs an engineer's time ~US$10k-25k/mth.
If you can make the problem go away by spending more in servers always do it.
For startups, the life and death is product market fit and you only get there by iterating on the business as many times as possible, not making something more efficient.
Put engineers on business iterations.
Re:What software engineers can learn from the rapid collapse...
by dgb23 on Friday April 08, 2022 @04:03AM
(#30954501)
Using more machines also introduce complexity.
Re:What software engineers can learn from the rapid collapse...
by tomp on Thursday April 07, 2022 @07:02PM
(#30951358)
Even before using more servers, one should consider using (one) bigger server (and another as backup).
Massive servers are laughably cheap these days. E.g. 16 cores, 128GB RAM is €112 from Hetzner.
Re:What software engineers can learn from the rapid collapse...
by mwcampbell on Thursday April 07, 2022 @07:05PM
(#30951392)
Damn, wish those dedicated servers were available in Hetzner's US data center. As far as I'm aware, the closest thing to a competitor in the US is OVH, and the server you get for that price is about a quarter of the capacity. That's plenty for my little company, but still...
Re:What software engineers can learn from the rapid collapse...
by hardwaresofton on Thursday April 07, 2022 @07:54PM
(#30951735)
Same here -- I'm eagerly awaiting them having a dedicated server offering
In the meantime have you looked at leaseweb?
https://www.leaseweb.com/dedicated-servers#US
I'm planning on running nimbus web services[0] there and there are a few other smaller providers I have earmarked depending on how brave you are:
https://www.defendhosting.com/usa-unmanaged-servers/
https://cc.delimiter.com/cart/dedicated-servers/
[0]: https://nimbusws.com
Re:What software engineers can learn from the rapid collapse...
by SkyPuncher on Friday April 08, 2022 @05:11PM
(#30962577)
In our case, we're running on top of a PaaS (think Heroku). Vertical vs Horizontal scaling is essentially the same complexity for the scale we're currently at.
Basically, to move development velocity faster we "load everything". Seems like a really bad idea on the surface. In practice, we only ran into an issue with a single customer that was literally 1000x as large as the other customers. It took about two weeks by 1 engineer to rework a select few calls that were egregiously slow and we were back at it.
----
In other words, even with some arguably inefficient technical decisions, I've rarely if ever seen performance issues at early stage startups.