3 ms·
One our our engineers in a few of his sprints rewrote major pieces of Apache Tomcat, which is used in our very high TPS APIs. He fixed a bunch of the way the me
by ldjkfkdsjnv 5y ago
One our our engineers in a few of his sprints rewrote major pieces of Apache Tomcat, which is used in our very high TPS APIs. He fixed a bunch of the way the memory loading works, and drastically improved latency and stability of over 100 teams APIs. This guy had deep understanding of dependency injection, how java works under the hood, etc. This kind of thing might not be a huge win for a startup, but at a large corporation, you need people that can push the bounds on already well tested and well known open source software
- nradov 5y agoWouldn't it be easier to just use a higher performance application server instead of rewriting Tomcat?
- kragen 5y agoI don't know the situation of the company, but very often the answer to "Wouldn't it be easier to just change platforms?" is just "no".
- david38 5y agoSo, say you have 500 machines serving something. This rewrite allows you to bring it down to 100. This code change saves you 400 instances x 24 hrs x 365 x aws cost per hour. And the next year, and the year after that, and maybe the one after that too. Throwing more metal at the problem is the favored solution when the issue is transient, the company doesn’t scale, or the company is shitty.
- nradov 5y agoI wasn't suggesting throwing more hardware at the problem. There are higher performance application servers available.