Welcome to Atmosphere: The Event Driven Framework supporting WebSocket and HTTP
The Atmosphere Framework contains client and server side components for building Asynchronous Web Applications. Atmosphere transparently supports WebSockets, Server Sent Events (SSE), Long-Polling, HTTP Streaming (Forever frame) and JSONP.
The Atmosphere Framework can be used with
The Atmosphere Framework works on all Servlet based servers, Spring Boot and frameworks like Netty, Play! Framework and Vert.x. We support a variety of extensions like Apache Kafka, Hazelcast, RabbitMQ, Redis and many more.
Atmosphere's Java/Scala/Android Client is called wAsync.
Main development branch is atmosphere-2.7.x Only pull request for that branch will be accepted.
Commercial Support is available via Async-IO.org
To use Atmosphere, add the following dependency:
Support for Jakarta EE (
jakarta.*) is available with Atmosphere 3.0.0
<dependency> <groupId>org.atmosphere</groupId> <artifactId>atmosphere-runtime</artifactId> <version>3.0.2</version> </dependency>
atmosphere-module can be: runtime (main module), jersey, spring, kafka, guice, redis, hazelcast, jms, rabbitmq, jgroups etc. Our official releases are available from Maven Central download.
Get started using this step by step tutorial.
Easiest way to learn Atmosphere is by trying a sample.
The Atmosphere Framework ships with many examples describing how to implement WebSockets, Server-Sent Events, Long-Polling, HTTP Streaming and JSONP client applications. Take a look at this page to pick the best sample to start with.
Jump directly inside the code: WebSockets, Server-Sent Events (SSE), Long-Polling, JSONP and HTTP Streaming!
Atmosphere and JDK Versions
Atmosphere 2.5.x requires JDK 8 or 11. Atmosphere 2.4.x requires JDK 1.7 or newer
3.0.x releases: 3.0.1 [3.0.0](Jakarta Support)
http://async-io.org for commercial support)End Of Life Versions (go to
@Copyright 2008-2022 Async-IO.org