Discord & Slack — Real-Time Java

Real-time chat is where you go for a fast sanity check (“is this the right way to do X in Spring Boot 3.4?”) or to observe practitioners at work. Neither replaces reading docs, but both compress the time from stuck-at-11-PM to unstuck.

Discord Servers

Invite links rot. Always verify the invite at the linked project’s official homepage or GitHub README before joining. The homepages below are stable.

Server

Homepage / how to find invite

Members (approx 2026)

Focus

Verdict

Java (official-ish community)

discord.java.com (redirects to Discord) or from adventofcode / discord.gg listings

60k+

General Java, JEP discussion, help channel

PRIMARY. Multiple help channels tiered by skill. Real JDK contributors occasionally answer.

Spring Community Discord

Announced on spring.io blog; join link maintained on spring.io/community

15k+

Spring, Spring Boot, Spring Cloud

JOIN when starting Spring (M7). Josh Long and other Spring team members drop in.

The Programmer’s Hangout

theprogrammershangout.com

100k+

Multi-language

SITUATIONAL. Java channel active but general community is broad.

JavaBrains (Koushik Kothagal)

Linked from java-brains.io or the JavaBrains YouTube “About” section

5-10k

Beginner-intermediate

SITUATIONAL for M1-M3.

r/java Discord

Linked in r/java sidebar (verify current invite)

Smaller

r/java overflow

OPTIONAL. Redundant with the main Java Discord for you.

Kotlin Slack (Kotlinlang)

slack.kotlinlang.org

60k+

Kotlin, but Java-Kotlin interop active

SITUATIONAL if considering Kotlin. Not for pure Java help.

How to actually use Discord

  • Join, mute the server (right-click → notification settings → Nothing).

  • Use #help channels only when stuck for >30 min after checking docs.

  • Format code blocks with triple backticks + java. People will ignore unformatted questions.

  • State: what you tried, error message, minimal repro. “How do I use RestTemplate” gets ignored; “I get X error when calling Y with headers Z on Spring Boot 3.4, tried W” gets answered.

  • Do not DM. Ask in the channel.

Slack

Slack is dying as a public community platform (paid tiers hide history) but two Java communities remain worth joining.

Workspace

How to join

Focus

Verdict

Foojay Slack

foojay.io — click “Slack” in the site header for the invite

JDK / OpenJDK developer conversation

JOIN. This is where OpenJDK devs and DevRel folks (Simon Ritter, Geertjan Wielenga) hang out. Signal-to-noise is high.

Spring Slack

Deprecated in favor of Spring Discord as of 2023. Don’t bother.

SKIP.

DevRel Collective

devrelcollective.fun

Developer advocacy community

SKIP unless considering a DevRel career move.

Foojay Slack — the underrated one

Foojay (“Friends of OpenJDK”) is a technical community founded by Azul + Bellsoft + community. Its Slack has channels by JDK vendor (Temurin, Corretto, Zulu), by topic (#virtual-threads, #gc, #tools), and low ceremony. Ask “which JDK should I use on Apple Silicon” and get a straight answer from someone at the vendor.

The India-Specific Note

  • Bangalore JUG Slack existed pre-COVID; largely dormant now. WhatsApp / Telegram groups have replaced it. Ask at your first Bangalore JUG meetup (see 06_conferences_and_meetups.md).

  • Chennai / Hyderabad JUG groups primarily coordinate via Meetup.com and LinkedIn events, not Slack.

  • Zoho internal Slack (if you’re at Zoho) has Java-specific channels — check with your L&D or Backend platform team.

Etiquette Rules That Apply Everywhere

  1. Lurk for 3 days before asking. Learn the norms first.

  2. Read pinned messages. They usually contain FAQ + rules.

  3. Post minimal reproducible example. Not screenshots of IDE.

  4. Thank people who help. Karma compounds.

  5. Never ping @everyone or DMs on cold outreach. Instant ban material.

Rule for This Plan

Join the Java Discord in Month 1. Join Foojay Slack in Month 5 (when you start caring about JVM internals). Join the Spring Discord in Month 7. Do not join everything at once — you will only end up muting them all and forgetting they exist.

Return to README.md · Next: 03_youtube_and_video.md