Hacker News Reader

Comment by abadger9 | Hacker News Reader

Having worked in the JVM ecosystem building low latency systems for over a decade, I always aspire to have the minute knowledge Aleksey has. I wish there was a book/MOOC for more senior engineers, but i've found myself content and happy with the Anatomy Quark series.

View on HN

I share the feeling that I wish there were more resources out there. I've collected a motley set at https://justinblank.com/notebooks/jvmarchitecture.html, but I haven't found anything systematic.

this is the one that got me started in low latency java a decade ago - http://blog.vanillajava.blog/ - I've spoken with Peter a couple of times, he's a phenomenal technologist

Vanilla Java is a great resource. The work that Chronicle does got me into low latency Java as well (not doing java now though).

Some other great resources I used:

* http://psy-lob-saw.blogspot.com/ - Not updated since 2018, but still great stuff in there

* https://richardstartin.github.io/ - A few posts per year. Richard does a lot of interesting things.

https://shipilev.net/jvm-anatomy-park yields 404. Maybe that should link to the TFA now?

Thanks, will update later. https://shipilev.net/jvm/anatomy-quarks/ is the address.

Why is Java used in low latency systems? Isn't C++ a better choice there?

It works 24/7, I guess. Reliability is the key -- it stays running.

It's got a vast array of third-party libraries available. It performs pretty well even in a low-latency environment.

Developers can spend time solving actual business problems, rather than waiting to compile, fooling around with memory allocation, templating problems & inefficient STL data structures, or badly handrolling data structures.

There is a little extra work to stay within a latency envelope, but there are definitely productivity boosts from just forgetting all the old C legacy and being able to work at a higher level of thinking.

Even better, use the JVM but try Kotlin as a language.

C++ is actually an esoteric language, not unlike Haskell or Prolog. It is just a widely used one, for historical reasons.

Meanwhile, you may just get things done in Java without giving much thought.

When there are orders of magnitude more people working with C++ compare to Haskell or Prolog, I would hesitate to call it "esoteric." The problem with C++ is everyone uses their own little dialect, ranging from little more than C with classes / nicer syntax, to every new "modern" feature under the sun.

Reply on news.ycombinator.com