home.social

#openliberty — Public Fediverse posts

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

  1. MicroProfile is not about annotations.
    It’s about contracts.

    In this hands-on guide, I build a book-catalog microservice with:
    • MicroProfile Config
    • Health (live + ready)
    • Fault Tolerance (timeout, retry, circuit breaker)
    • JWT security

    All on Open Liberty.
    No vendor APIs in business code.

    Production behavior included. Not just “it works locally.”

    the-main-thread.com/p/micropro

    #Java #MicroProfile #OpenLiberty #CloudNative #JakartaEE

  2. Marcus Hellberg just delivered “Full-stack web apps, 100% Java” at #JCON USA @ #IBMTechXchange. A crisp live-coding tour of #OpenLiberty+ #Vaadin Flow—from persistence and external services to a good-looking UI—all in #Java!
    Bonus: it’s his birthday today 🎂 If you’re onsite, catch him in the hallway track and wish him well!

    #JCONUSA2025

  3. Fed up with #JavaScript bugs? Take the red pill and build full-stack web apps with just #Java! 🕶️

    At #JCONUSA25, Marcus Hellberg will live-code apps using #OpenLiberty + #Vaadin Flow.
    100% Java, no agents, no glitches. Follow the white rabbit.

    usa.jcon.one/register

    #JCON #IBM #TechXchange

  4. Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: bit.ly/4cEppIA

    This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.

    This analysis guides Java developers on when and how to use virtual threads in their applications.

    #JDK21 #VirtualThreads #OpenLiberty

  5. There has been some interesting discussion on 11 and servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.

  6. On the / server front, my preference now tends to be for either or . may be ok too, but I have actually seen the folks kind of unselling it a bit. Payara has really moved much more strongly to an model. I've seen some features pulled from Payara Community Edition in the last couple years (gives me bad vibes).