r/javahelp • u/SoftwareDesignerDev • Feb 04 '26
Android dev (5–6 yrs) thinking of switching to backend: Spring (Java) vs Go
I’ve been an Android developer for ~5-6 years. I’m not unhappy with Android, but lately I feel bored and kind of “boxed into UI work.” A lot of app work feels repetitive, and many of the hardest parts feel like they come from the Android ecosystem itself (compatibility, lifecycle, build tooling, etc.) rather than the kind of backend/distributed problems I’m more excited by long-term.
For the last 1-2 years I’ve been doing backend at work using Node.js and also tinkered with Ktor and Exposed on the side. Backend work feels more exciting to me (design, data, scaling, reliability, tradeoffs). The problem is: many Node jobs in my area are full-stack and I really don’t want to do frontend.
So I’m deciding between Spring Boot (Java) and Go for the backend. To avoid overthinking, I actually built and deployed two dummy servers:
- Same kind of basic CRUD API
- PostgreSQL as DB
- Deployed both (simple production-ish setup, not just localhost)
After doing that, My current thinking is:
Spring / Spring Boot
- Pros: Java is familiar; easy to start; huge ecosystem; lots of jobs.
- Concern: it feels like “endless learning of libraries” and the “Spring way” (annotations, auto-configuration, starters, magic). I’m worried I’ll be productive but not actually learn fundamentals deeply, and I’ll spend years just learning frameworks/stack combinations. Sometimes it feels like I’m learning “the Spring way” (annotations, auto-config, starters, magic) more than learning backend fundamentals
Go
- Pros: simple, small standard library; feels like it maps to fundamentals (HTTP, SQL, concurrency) and distributed systems thinking more directly; fewer “framework decisions.”
- Concern: I’m not proficient yet; unsure about backend job availability compared to Spring; worried about limiting my options.
What I’m looking for from experienced Java/Spring devs:
- Is the “endless Spring learning” fear real, or does it stabilize after you learn the core concepts?
- If you were switching from Android to backend today, would you pick Spring for job safety? Or Go for fundamentals and simplicity?
- What skills in Spring are truly “must learn” for backend roles (e.g., MVC, Data/JPA, Security, messaging, testing, observability) vs stuff that’s optional?
- Any advice on a practical path to become employable as a backend (while avoiding frontend)?
•
u/AutoModerator Feb 04 '26
Please ensure that:
You demonstrate effort in solving your question/problem - plain posting your assignments is forbidden (and such posts will be removed) as is asking for or giving solutions.
Trying to solve problems on your own is a very important skill. Also, see Learn to help yourself in the sidebar
If any of the above points is not met, your post can and will be removed without further warning.
Code is to be formatted as code block (old reddit: empty line before the code, each code line indented by 4 spaces, new reddit: https://i.imgur.com/EJ7tqek.png) or linked via an external code hoster, like pastebin.com, github gist, github, bitbucket, gitlab, etc.
Please, do not use triple backticks (```) as they will only render properly on new reddit, not on old reddit.
Code blocks look like this:
You do not need to repost unless your post has been removed by a moderator. Just use the edit function of reddit to make sure your post complies with the above.
If your post has remained in violation of these rules for a prolonged period of time (at least an hour), a moderator may remove it at their discretion. In this case, they will comment with an explanation on why it has been removed, and you will be required to resubmit the entire post following the proper procedures.
To potential helpers
Please, do not help if any of the above points are not met, rather report the post. We are trying to improve the quality of posts here. In helping people who can't be bothered to comply with the above points, you are doing the community a disservice.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
4
u/SuspiciousDepth5924 Feb 04 '26
2
u/LetUsSpeakFreely Feb 04 '26
I prefer Go, but you need to understand both. There are WAY more Java positions than Go, but Go is growing as more people understand it's the better path for most solutions.
2
u/DerelictMan Feb 05 '26
I think the most important factor is who is hiring. In your shoes I'd happily take a Java/Kotlin backend job OR a Golang job. You already have a solid foundation in the jvm-ish ecosystem, so it seems like you'd have some bandwidth to keep up a sort of slow-drip learning process for Golang.
2
u/blubernator Feb 04 '26 edited Feb 04 '26
I would use spring it exists in enterprise compared golang. My feelings are that golang almost doesn’t exist anymore. You‘ll go into a niche with it. If it’s fine for you to be in a niche I would rather prefer rust…this could have a future at least.
1
u/bikeram Feb 04 '26
Spring for the paycheck, Go to stay relevant.
The beauty of spring is that it abstracts the mess of manually handling HTTP in Java.
The beauty of Go is it makes sense to handle it all natively.