Welcome to AskMeJava Discussions!

[rokon12]

Exciting News for My Network 🚀

I've been fortunate to receive many questions and engage in valuable discussions across different channels. Your curiosity and eagerness to learn have inspired me to create something special.

I'm pleased to announce the launch of a new GitHub repository dedicated to your questions related to software engineering, Java, architecture, and industry trends. This repository will be a one-stop solution for all your queries, ensuring that no question goes unanswered.

Here's how it works:
1️⃣ Post your questions in the comments section bellow.
2️⃣ I'll do my best to respond, either directly in the repo or through an in-depth article on my blog.

By centralizing these interactions, I hope to create a valuable resource that's not only beneficial to you but also accessible to anyone interested in our shared passions.

Your questions don't have to be confined to a narrow field. Whether it's something specific about Java or a more general inquiry about software development, architecture, or industry trends, I'm here to engage with you.

Your thoughts, questions, and feedback are the driving force behind this initiative, and I can't wait to see where this collaborative effort takes us.

Happy coding, and let's keep the conversation going! 🎉

#softwareengineering #java #knowledgeSharing #communityBuilding

[ArunJohnJ]

In the age where we can just spin up some machines and scale horizonantly a application, the following question might be sily, but still couldn't understand the full need of why we would still want to continue with concurrent programming using threads?

[rokon12]

The amount of resources you have, if you could do more with that, why would you waste it? Shouldn't we best use of resources?

The primary limitation of the native threads is that they are heavy, and you don't have enough of them. In I/O-driven applications, they sit there doing nothing. To carve out the problem, many alternatives have been built, e.g. reactive being one of them. But reactive programming is just not easy; you also have to sacrifice many wonderful things that Java gives you for free.

Many other languages have already solved the issue, e.g. go having goroutine. Async/await one of them. Java came up with virtual threads.

Thanks for the question; I am now thinking about an article answering your question with more details.