Armeria Newsletter vol. 5

We have some announcements to share with you.

• 📢 Discontinuation of virtual office hours:
  • We will transform the existing virtual hours to another form such as quarterly webinar. But we haven't decided how often we hold the webinar or what to cover. Please stay tuned.
• 🙌 Armeria adopters page and limited goods package:
  • You can now show off how well your service takes advantage of Armeria!
  • Don't forget to request the limited goods packages.

• 🚛 Moving to Discord:
  • We decided to move to Discord to preserve all past messages.
  • But no rush! We'll run the both Slack and Discord for a while. Please join our Discord server whenever you're ready.
• 🌟 We're now 4K family members!
  • It's amazing to see the steady growth of stars. Thank y'all!

• ✨ We've released several new versions since our last newsletter with a bunch of new exciting features! Here are the highlights between 1.17.1 and 1.23.1.

  • Resilience4j circuit breaker support

  • Improvements in gRPC support

    • Asynchronous ServerInterceptor + Kotlin Coroutine support
    • Improved annotations support
    • Improvements in gRPC HTTP/JSON transcoding

  • Spring Boot 3 support (and dropping Spring Boot 1)

  • Improvements in DocService

    • Markdown and Mermaid support for DocService

    • Autocompletion support for gRPC and Thrift

• 🎓 Try out this guided tutorial for gRPC Service! This super friendly and simple tutorial will guide you to make a blog service just like the previous tutorial for REST services. But this time, you'll try step by step guide including:
  • Implement Armeria gRPC service and client
  • Exception handling
  • Invoke gRPC service via DocService
• 🔋 Here are some cool open source projects powered by Armeria:
  • Thorium Framework
    • A Scala 3 microservice framework leveraging on Armeria
  • Apache SkyWalking
    • An application performance monitor tool for distributed systems built on top of Armeria
  • Scavenger
    • A runtime dead code analysis tool on top of Armeria

• 🤔 Your opinion means a lot to us. Please let us know what you think about these proposals:
  • #4314 Provide an easier way to get a ClientRequestContext
  • #4569 Consider RFC 7807 Problem Details for HTTP APIs as the default response format in REST APIs
  • #4738 Consider a way to make OAuth2AuthorizationGrant dynamic when update the grant information needed

• 🔰 Want to contribute but not sure where to start from? Try this issue:
  • #4797 Contain which file doesn't exist in the response so that user get more clues to distinguish if the file service isn't bound at all or only the file doesn't exist