I'm a software engineer passionate about algorithms, backend technologies, distributed systems, cloud native and performance, although I am no stranger to frontend.
It's true that managing memory out of the "standards" that the JVM provides, brings other concerns and problems to think about, however off-heap is not a replacement of the heap memory for all cases and should be something to evaluate carefully depending on the case.
As I mentioned in the post it could be a good try when we are dealing with a lot of data stored in memory, or even when that data exceeds the physical memory and using disk is an option.
Finally, there are many options for addressing design problems and I just wanted to show one that I found interesting IMHO.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Darius, thanks for reading and commenting.
It's true that managing memory out of the "standards" that the JVM provides, brings other concerns and problems to think about, however off-heap is not a replacement of the heap memory for all cases and should be something to evaluate carefully depending on the case.
As I mentioned in the post it could be a good try when we are dealing with a lot of data stored in memory, or even when that data exceeds the physical memory and using disk is an option.
Finally, there are many options for addressing design problems and I just wanted to show one that I found interesting IMHO.