home.social

#enterprisejava — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #enterprisejava, aggregated by home.social.

  1. I use AI tools every day. They help. But I also feel the other side of it more now: more review, more supervision, more mental carry-over after the laptop is closed.

    This piece is about that cost for senior Java developers and enterprise teams.

    the-main-thread.com/p/ai-senio

    #Java #EnterpriseJava #SoftwareEngineering #AI #DeveloperProductivity

  2. I’ve been thinking a lot about where AI coding tools stop being “helpful” and start becoming part of the runtime risk model.

    This piece is about that line.

    For Java teams, the real issue is not bad generated code. It’s excessive agency: shell access, secrets, MCP tools, and autonomous actions without enough containment.

    the-main-thread.com/p/ai-codin

    #Java #Quarkus #DevSecOps #AICoding #SoftwareSecurity #EnterpriseJava

  3. I’ve been thinking a lot about where AI coding tools stop being “helpful” and start becoming part of the runtime risk model.

    This piece is about that line.

    For Java teams, the real issue is not bad generated code. It’s excessive agency: shell access, secrets, MCP tools, and autonomous actions without enough containment.

    the-main-thread.com/p/ai-codin

    #Java #Quarkus #DevSecOps #AICoding #SoftwareSecurity #EnterpriseJava

  4. I’ve been thinking a lot about where AI coding tools stop being “helpful” and start becoming part of the runtime risk model.

    This piece is about that line.

    For Java teams, the real issue is not bad generated code. It’s excessive agency: shell access, secrets, MCP tools, and autonomous actions without enough containment.

    the-main-thread.com/p/ai-codin

    #Java #Quarkus #DevSecOps #AICoding #SoftwareSecurity #EnterpriseJava

  5. I’ve been thinking a lot about where AI coding tools stop being “helpful” and start becoming part of the runtime risk model.

    This piece is about that line.

    For Java teams, the real issue is not bad generated code. It’s excessive agency: shell access, secrets, MCP tools, and autonomous actions without enough containment.

    the-main-thread.com/p/ai-codin

    #Java #Quarkus #DevSecOps #AICoding #SoftwareSecurity #EnterpriseJava

  6. I’ve been thinking a lot about where AI coding tools stop being “helpful” and start becoming part of the runtime risk model.

    This piece is about that line.

    For Java teams, the real issue is not bad generated code. It’s excessive agency: shell access, secrets, MCP tools, and autonomous actions without enough containment.

    the-main-thread.com/p/ai-codin

    #Java #Quarkus #DevSecOps #AICoding #SoftwareSecurity #EnterpriseJava

  7. ftware kann zum Beweismittel werden! #EnterpriseJava-Systeme stehen zunehmend im Fokus forensischer Analysen – Commit für Commit. Prof. Dr.-Ing. Stefan Wagenpfeil erklärt, wie man sich vorbereitet. Ist euer Entwicklungsprozess belastbar?

    Jetzt lesen: javapro.io/de/code-vor-gericht

  8. Not every company can jump to #JakartaEE 11 overnight. Chiara Civardi shows how to modernize safely — without breaking stable systems.
    What’s your biggest blocker in modernization?

    Read now: javapro.io/2025/12/03/as-java-

    #EnterpriseJava #SoftwareArchitecture @Payara_Fish #JAVAPRO

  9. Most teams think more context makes AI coding agents better.

    In enterprise Java, it often does the opposite.

    After working with Copilot, Claude, and lately IBM Bob + Bobshell, I learned one thing: your AGENTS.md is not documentation. It’s a control surface.

    Keep it small. Move conventions to skills. Separate repo rules from policy.

    Here’s the full breakdown:
    the-main-thread.com/p/optimize

    #Java #EnterpriseJava #AICoding #LLMs #SoftwareArchitecture

  10. Most teams don’t start from scratch.

    They have a working Quarkus app. Repositories. Services. REST endpoints. Production traffic.

    In our latest episode, Alex Soto shows how to use IBM Bob to add LangChain4j to an existing Quarkus application — step by step, no rewrite.

    It’s about controlled AI integration. Not hype.

    Full article:
    the-main-thread.com/p/from-sta

    #Java #Quarkus #LangChain4j #AIEngineering #EnterpriseJava #DevExperience

  11. Hibernate with Panache Next just landed in Quarkus main.

    One API.
    Blocking + reactive unified.
    Stateless sessions.
    Type-safe @Find queries validated at build time.

    This is a real shift in how we build persistence layers in Java.

    I built a full bookstore REST API to show:
    • Managed vs stateless sessions
    • Reactive repositories
    • What breaks under load

    Full hands-on deep dive:
    the-main-thread.com/p/quarkus-

    #Quarkus #Java #Hibernate #JakartaData #EnterpriseJava

  12. Hibernate with Panache Next just landed in Quarkus main.

    One API.
    Blocking + reactive unified.
    Stateless sessions.
    Type-safe @Find queries validated at build time.

    This is a real shift in how we build persistence layers in Java.

    I built a full bookstore REST API to show:
    • Managed vs stateless sessions
    • Reactive repositories
    • What breaks under load

    Full hands-on deep dive:
    the-main-thread.com/p/quarkus-

    #Quarkus #Java #Hibernate #JakartaData #EnterpriseJava

  13. Hibernate with Panache Next just landed in Quarkus main.

    One API.
    Blocking + reactive unified.
    Stateless sessions.
    Type-safe @Find queries validated at build time.

    This is a real shift in how we build persistence layers in Java.

    I built a full bookstore REST API to show:
    • Managed vs stateless sessions
    • Reactive repositories
    • What breaks under load

    Full hands-on deep dive:
    the-main-thread.com/p/quarkus-

    #Quarkus #Java #Hibernate #JakartaData #EnterpriseJava

  14. Hibernate with Panache Next just landed in Quarkus main.

    One API.
    Blocking + reactive unified.
    Stateless sessions.
    Type-safe @Find queries validated at build time.

    This is a real shift in how we build persistence layers in Java.

    I built a full bookstore REST API to show:
    • Managed vs stateless sessions
    • Reactive repositories
    • What breaks under load

    Full hands-on deep dive:
    the-main-thread.com/p/quarkus-

    #Quarkus #Java #Hibernate #JakartaData #EnterpriseJava

  15. Hibernate with Panache Next just landed in Quarkus main.

    One API.
    Blocking + reactive unified.
    Stateless sessions.
    Type-safe @Find queries validated at build time.

    This is a real shift in how we build persistence layers in Java.

    I built a full bookstore REST API to show:
    • Managed vs stateless sessions
    • Reactive repositories
    • What breaks under load

    Full hands-on deep dive:
    the-main-thread.com/p/quarkus-

    #Quarkus #Java #Hibernate #JakartaData #EnterpriseJava

  16. Software kann zum Beweismittel werden! #EnterpriseJava-Systeme stehen zunehmend im Fokus forensischer Analysen – Commit für Commit. Prof. Dr.-Ing. Stefan Wagenpfeil erklärt, wie man sich vorbereitet. Ist euer Entwicklungsprozess belastbar?

    Jetzt lesen: javapro.io/de/code-vor-gericht

  17. Org charts are boring.
    Until your company does another reorg.

    This article shows how to build an interactive org chart with Java, Quarkus, PostgreSQL recursive CTEs, and D3.js — designed for orgs that change constantly (yes, even yours).

    Hands-on. Full code. Real hierarchy queries.
    the-main-thread.com/p/interact

    #Java #Quarkus #PostgreSQL #SQL #WebDev #EnterpriseJava

  18. LangChain4j has crossed an important line:
    from “interesting library” → production Java AI infrastructure.

    I wrote a long-form guide with 50 LangChain4j interview questions, covering:
    • AI Services
    • RAG & embeddings
    • Tools & agents
    • Memory & context limits
    • Observability, cost, and security

    Written from a production Java perspective — not Python demos.

    the-main-thread.com/p/langchai

    #Java #LangChain4j #AIinJava #EnterpriseJava #RAG #LLM #SoftwareArchitecture #DevExperience

  19. Most persistence bugs are boring.

    Renamed fields. Broken query strings. Invalid sort orders.
    They compile. Tests pass. Production breaks later.

    Jakarta Data in Quarkus 3.31 moves these failures to compile time.

    This article explains why that matters, how Panache 2.0 fits in, and why the Hibernate annotation processor is the real story.

    the-main-thread.com/p/jakarta-

    #Java #Quarkus #JakartaData #Hibernate #EnterpriseJava

  20. Most persistence bugs are boring.

    Renamed fields. Broken query strings. Invalid sort orders.
    They compile. Tests pass. Production breaks later.

    Jakarta Data in Quarkus 3.31 moves these failures to compile time.

    This article explains why that matters, how Panache 2.0 fits in, and why the Hibernate annotation processor is the real story.

    the-main-thread.com/p/jakarta-

    #Java #Quarkus #JakartaData #Hibernate #EnterpriseJava

  21. Most persistence bugs are boring.

    Renamed fields. Broken query strings. Invalid sort orders.
    They compile. Tests pass. Production breaks later.

    Jakarta Data in Quarkus 3.31 moves these failures to compile time.

    This article explains why that matters, how Panache 2.0 fits in, and why the Hibernate annotation processor is the real story.

    the-main-thread.com/p/jakarta-

    #Java #Quarkus #JakartaData #Hibernate #EnterpriseJava

  22. Most persistence bugs are boring.

    Renamed fields. Broken query strings. Invalid sort orders.
    They compile. Tests pass. Production breaks later.

    Jakarta Data in Quarkus 3.31 moves these failures to compile time.

    This article explains why that matters, how Panache 2.0 fits in, and why the Hibernate annotation processor is the real story.

    the-main-thread.com/p/jakarta-

    #Java #Quarkus #JakartaData #Hibernate #EnterpriseJava

  23. Most persistence bugs are boring.

    Renamed fields. Broken query strings. Invalid sort orders.
    They compile. Tests pass. Production breaks later.

    Jakarta Data in Quarkus 3.31 moves these failures to compile time.

    This article explains why that matters, how Panache 2.0 fits in, and why the Hibernate annotation processor is the real story.

    the-main-thread.com/p/jakarta-

    #Java #Quarkus #JakartaData #Hibernate #EnterpriseJava

  24. Most toxicity filters fail because they treat language as text, not meaning.

    In this article I show how to build semantic toxicity detection with Quarkus Guardrails using a dedicated classifier model, not regex or vague embeddings.

    Multi-dimensional scoring. In-process ONNX. Production-grade Java.

    👉 the-main-thread.com/p/semantic

    #Java #Quarkus #AI #LLM #AISafety #EnterpriseJava

  25. Why do 48 hours sometimes equal 47?
    Because time in Java is not arithmetic — it’s policy.

    This deep dive shows how DST silently breaks billing logic, why Joda-Time modeled time correctly, and how to migrate legacy code safely to java.time using a real Quarkus example.

    the-main-thread.com/p/joda-tim

    #Java #JodaTime #JavaTime #DST #Quarkus #SoftwareArchitecture #EnterpriseJava

  26. mTLS looks simple until you realize what it doesn’t protect you from.

    A trusted client certificate is not the same thing as an allowed client.
    If your Java service stops at “the handshake worked,” you’re leaving a gap attackers can walk through.

    I wrote up a hands-on Quarkus implementation that shows:
    – where TLS ends
    – where security should begin
    – and how to enforce certificate rules before business logic runs

    the-main-thread.com/p/quarkus-

    #Java #Quarkus #Security #mTLS #EnterpriseJava

  27. Stuck between #JakartaEE 11, Spring, Quarkus — and legacy EE 8? Chiara Civardi outlines pragmatic modernization paths that avoid risky full rewrites.
    What path is your organization choosing?

    Read now: javapro.io/2025/12/03/as-java-

    #JAVAPRO #EnterpriseJava #Refactoring @Payara_Fish

  28. Most AI coding tools work best on small, isolated changes.
    That breaks down fast in real Java systems.

    I’ve been working with IBM Bob on long-lived codebases and wrote down what it actually does well: planning before coding, system-level analysis, and controlled modernization.

    Neutral, technical, and based on real use.

    the-main-thread.com/p/ibm-bob-

    #Java #EnterpriseJava #SoftwareArchitecture

  29. #Java EE 8 still powers most mission-critical apps — but vendor support is disappearing fast. Chiara Civardi explains what teams can realistically do next. What runtime are you still using in production?

    Read: javapro.io/2025/12/05/is-it-wo

    #JakartaEE #EnterpriseJava @Payara_Fish

  30. Only 2 days left! You were a #Speaker at #JCON2025, you will be speaking at #JCON2026 or other conferences, or you’ve always wanted to write about #Java? Then take your chance: #JAVAPRO is seeking articles for the new print edition.

    #CFP Deadline: Nov 28

    👉 Submit your proposals: docs.google.com/forms/d/e/1FAI

    #ServersideJava #CoreJava #GenAI #EnterpriseJava #Frameworks #APIs

  31. Only 2 days left! You were a #Speaker at #JCON2025, you will be speaking at #JCON2026 or other conferences, or you’ve always wanted to write about #Java? Then take your chance: #JAVAPRO is seeking articles for the new print edition.

    #CFP Deadline: Nov 28

    👉 Submit your proposals: docs.google.com/forms/d/e/1FAI

    #ServersideJava #CoreJava #GenAI #EnterpriseJava #Frameworks #APIs

  32. Only 2 days left! You were a #Speaker at #JCON2025, you will be speaking at #JCON2026 or other conferences, or you’ve always wanted to write about #Java? Then take your chance: #JAVAPRO is seeking articles for the new print edition.

    #CFP Deadline: Nov 28

    👉 Submit your proposals: docs.google.com/forms/d/e/1FAI

    #ServersideJava #CoreJava #GenAI #EnterpriseJava #Frameworks #APIs

  33. Only 2 days left! You were a #Speaker at #JCON2025, you will be speaking at #JCON2026 or other conferences, or you’ve always wanted to write about #Java? Then take your chance: #JAVAPRO is seeking articles for the new print edition.

    #CFP Deadline: Nov 28

    👉 Submit your proposals: docs.google.com/forms/d/e/1FAI

    #ServersideJava #CoreJava #GenAI #EnterpriseJava #Frameworks #APIs

  34. Only 2 days left! You were a #Speaker at #JCON2025, you will be speaking at #JCON2026 or other conferences, or you’ve always wanted to write about #Java? Then take your chance: #JAVAPRO is seeking articles for the new print edition.

    #CFP Deadline: Nov 28

    👉 Submit your proposals: docs.google.com/forms/d/e/1FAI

    #ServersideJava #CoreJava #GenAI #EnterpriseJava #Frameworks #APIs

  35. Polymorphic JSON meets Quarkus and Jakarta Data.

    A clean, standards-based way to store evolving object hierarchies directly in JSON columns — no schema pain, full type safety.

    Java records, Hibernate ORM, JAX-RS, and Quarkus Dev mode all in one place.

    👉 the-main-thread.com/p/quarkus-

    #Java #Quarkus #JakartaEE #Hibernate #JSON #EnterpriseJava

  36. Building a smarter #AI prompt server — in pure #Java with #Quarkus

    In this new guide, we connect GitHub’s awesome-copilot-prompts to Claude and other LLM clients using the Model Context Protocol (MCP).
    Persistent caching, clean architecture, and zero dependencies.

    the-main-thread.com/p/quarkus-

    #LangChain4j #ClaudeDesktop #OpenSource #DevTools #EnterpriseJava

  37. Building a smarter #AI prompt server — in pure #Java with #Quarkus

    In this new guide, we connect GitHub’s awesome-copilot-prompts to Claude and other LLM clients using the Model Context Protocol (MCP).
    Persistent caching, clean architecture, and zero dependencies.

    the-main-thread.com/p/quarkus-

    #LangChain4j #ClaudeDesktop #OpenSource #DevTools #EnterpriseJava

  38. Building a smarter #AI prompt server — in pure #Java with #Quarkus

    In this new guide, we connect GitHub’s awesome-copilot-prompts to Claude and other LLM clients using the Model Context Protocol (MCP).
    Persistent caching, clean architecture, and zero dependencies.

    the-main-thread.com/p/quarkus-

    #LangChain4j #ClaudeDesktop #OpenSource #DevTools #EnterpriseJava

  39. Building a smarter #AI prompt server — in pure #Java with #Quarkus

    In this new guide, we connect GitHub’s awesome-copilot-prompts to Claude and other LLM clients using the Model Context Protocol (MCP).
    Persistent caching, clean architecture, and zero dependencies.

    the-main-thread.com/p/quarkus-

    #LangChain4j #ClaudeDesktop #OpenSource #DevTools #EnterpriseJava

  40. Building a smarter #AI prompt server — in pure #Java with #Quarkus

    In this new guide, we connect GitHub’s awesome-copilot-prompts to Claude and other LLM clients using the Model Context Protocol (MCP).
    Persistent caching, clean architecture, and zero dependencies.

    the-main-thread.com/p/quarkus-

    #LangChain4j #ClaudeDesktop #OpenSource #DevTools #EnterpriseJava

  41. Ist Ihre alte #Java-App eine tickende Zeitbombe? Sicherheitslücken, veraltete Architektur, schwindendes Fachwissen – die Risiken wachsen. Chiara Civardi zeigt, wie man sicher modernisiert – ohne alles neu zu schreiben.

    Jetzt mehr erfahren: javapro.io/de/wiederbelebung-v
    #EnterpriseJava

  42. Ever wondered what saved #EnterpriseJava from fading into legacy? Spoiler: Not a framework—a power shift. It started at @EclipseFdn.
    Carmen Delgado, Thomas Froment & Tanja Obradovic chart the turning point.

    Follow the trail: javapro.io/2025/09/03/java-at-

    #CloudNative #JakartaEE #Microservices

  43. Think “just lift and shift” is a strategy? That’s how legacy becomes liability. @CivardiChiara maps out smart paths to modernizing #EnterpriseJava — without breaking what still works.

    A must-read for anyone maintaining the backbone: javapro.io/2025/06/26/revitali

    #JavaEE @EclipseFdn

  44. Modernizing legacy #Java isn’t about rewriting. It’s about choosing the right battle. Chiara Civardi delivers a no-BS guide to replatforming, refactoring & rebuilding — the smart way.

    Give your old code a real future: javapro.io/2025/06/26/revitali

    #JavaEE #EnterpriseJava @EclipseFdn