WildFly Swarm

WildFly Swarm
Name	WildFly Swarm
Developer	Red Hat
Released	2015
Latest release	2018 (as part of Thorntail transition)
Programming language	Java
Operating system	Cross-platform
Platform	Java Virtual Machine
License	Apache License 2.0

WildFly Swarm WildFly Swarm was a Java microservices framework designed to create self-contained, executable Java archives by packaging selected subsystems from the WildFly application server. It targeted cloud-native deployment on platforms such as Kubernetes, OpenShift, and Docker while offering developers an approach to build services with familiar Java SE, Jakarta EE, and MicroProfile APIs. The project was initiated and maintained by contributors at Red Hat, with community involvement from organizations and projects in the Eclipse Foundation ecosystem and the broader Open Source Initiative community.

Overview

WildFly Swarm provided a modular runtime that allowed applications to assemble only the server components they required, enabling smaller artifact sizes and faster startup times compared with full-profile application servers like GlassFish, JBoss EAP, and WebSphere Application Server. It exposed a programming model compatible with frameworks and libraries such as Spring Framework, Hibernate ORM, Apache Camel, RESTEasy, and Vert.x, while integrating with build tools including Apache Maven, Gradle, and CI/CD systems like Jenkins and Travis CI. The project emphasized container readiness for orchestration platforms such as Docker Swarm, Kubernetes, and OpenShift Origin.

History and Development

The initiative began within Red Hat engineering groups as an effort to reconcile the monolithic JBoss AS heritage with emerging microservices patterns championed by companies like Netflix and communities around Cloud Native Computing Foundation. Early milestones paralleled developments in MicroProfile and the evolution of Jakarta EE from Java EE, reflecting contributions from industry participants including IBM, Oracle Corporation, Payara, and community members from Eclipse MicroProfile. Over time, the project influenced and intersected with efforts such as Thorntail (the successor distribution), and its roadmap aligned with containerization trends driven by Google and the rise of Amazon Web Services and Microsoft Azure. Maintenance transitioned as corporate priorities shifted, and the codebase and concepts informed subsequent middleware products and community forks.

Architecture and Components

WildFly Swarm's architecture centered on modular "fractions" that encapsulated subsystem functionality derived from WildFly. Fractions represented components like networking, security, persistence, and web services, integrating technologies such as Undertow, Elytron, Keycloak, Infinispan, and Narayana transaction manager. The runtime packaged with a lightweight JUnit-friendly launcher and leveraged bytecode tooling from projects like ASM and JBoss Modules. Persistence stacks combined Hibernate ORM with HikariCP or JBoss JDBC drivers for databases including PostgreSQL, MySQL, Oracle Database, and MariaDB. Observability features enabled integration with Prometheus, Grafana, ELK Stack, and tracing systems inspired by Zipkin and OpenTracing.

Usage and Deployment

Developers built Swarm-based services using Maven or Gradle to assemble uber-jars that embedded only required fractions, which simplified deployment to Docker containers and orchestration with Kubernetes or OpenShift Container Platform. Typical deployment workflows incorporated CI pipelines in GitLab CI, CircleCI, or Jenkins X, with container registries such as Docker Hub and Quay.io. Runtime configuration could be provided via environment variables consistent with 12-factor app principles and secrets management integrated with HashiCorp Vault or cloud provider services including AWS Secrets Manager and Azure Key Vault. For scaling and service discovery, teams used Consul, Eureka, or Kubernetes service objects alongside load balancers like HAProxy and NGINX.

Tooling and Integration

Tooling around Swarm included IDE support via Eclipse IDE, IntelliJ IDEA, and NetBeans, and build plugins for Maven Plugin and Gradle Plugin ecosystems. Integration with testing frameworks such as Arquillian, Mockito, and Testcontainers facilitated integration and system testing against ephemeral containers. Developers used configuration management from Ansible or Terraform when provisioning infrastructure on cloud platforms like AWS, Google Cloud Platform, and Microsoft Azure. Monitoring integrations leveraged New Relic, Datadog, and AppDynamics alongside open-source solutions to provide metrics, logs, and distributed tracing.

Comparisons and Alternatives

WildFly Swarm competed with and related to frameworks and runtimes addressing microservices and Java deployment such as Spring Boot, Quarkus, Micronaut, Dropwizard, and Payara Micro. Compared with Spring Boot and Quarkus, Swarm emphasized reusing application server subsystems from WildFly and JBoss heritage, whereas alternatives focused on custom runtimes or ahead-of-time compilation. Organizations evaluated trade-offs versus full servers like GlassFish and WebSphere Liberty and versus lightweight JVM runtimes favored by cloud-native projects in the Cloud Native Computing Foundation landscape.

Reception and Legacy

While adoption among some enterprise teams was positive due to alignment with existing Red Hat ecosystems and JBoss EAP knowledge, the project faced competition from rising frameworks such as Spring Boot and Quarkus and changing priorities within Red Hat and the open-source community. The architectural concepts—modular fractions, executable jars, and container-first design—influenced successors including Thorntail and contributed to discussions in Eclipse MicroProfile working groups. The legacy persists in middleware strategies at firms adopting hybrid cloud patterns and in toolchains integrating Kubernetes and JVM-based microservices.

Category:Java (programming language) frameworks Category:Red Hat projects