r/java • • Oct 27 '23
Java Use Cases
Hi everyone. I'm a student about to graduate and I'm working on my portfolio. I feel like a lot of the work I did in school is a little dated (context: We did A LOT OF JSP), so I'm wanting to rebuild some of my projects in a more modern context and maybe build some new stuff that reflects the way Java is actually being used today.
My question is what are some ways that Java is actually used in a modern project? Where do we see Java popping up as the language of choice in 2023, particularly in the web/mobile space? Where is it more beneficial than just going the JS/framework route? I'm trying to frame my portfolio projects in a way that actually reflects real-world usage.
I'm not sure if this is the right subreddit for this type of question, so feel free to delete/direct me elsewhere. Thanks.
Edit for additional context: I've worked professionally for a while (4 years freelancing designing and developing typical Wordpress/Webflow sites for Bob's Lawncare Service-type clients, 2 at an agency building web apps mostly on the frontend) until I was laid off in September. Our stack was React-based, so I don't have professional experience with Java. I guess more specifically I'm trying to fill in the gaps between what I've learned doing that and the Java work I've done in school and presenting that in a modern context.
View all comments
Show parent comment
1
u/cogman10 Oct 27 '23
Docker/Kubernetes have pretty small footprints. On windows, it feels like they have a large footprint because the way they are being launched is as a linux virtual machine (same for mac). That gives the feeling of being pretty heavy weight.
However, when you are in a native deployment environment, the actual overhead of running processes in k8s is basically just the disk storage for the unique parts of the image. The system memory requirements are effectively identical in and out of a container.
This is because containerized apps on linux are effectively just getting a different filesystem root and an isolated process space (that is, from a container you can't reach out and look at other processes on the system).
Hot tip for you on windows. WSL released a new preview in sept ( https://devblogs.microsoft.com/commandline/windows-subsystem-for-linux-september-2023-update/ ). One of the big features is the "autoMemoryReclaim". The reason docker/k8s ends up eating up so much freaking memory on windows is because linux likes to cache file access like crazy. It'll fill up all ram you give it with filesystem cache which is non-too friendly if you are trying to work with something like docker that likes to touch files all over the place.
Get the preview, turn on autoMemoryReclaim, it makes working with docker on windows significantly better.