Wilmington, 19801, DE,
United States
Apache Software Foundation Technographics
Discover the latest software purchases and digital transformation initiatives being undertaken by Apache Software Foundation and its business and technology executives. Each quarter our research team identifies on-prem and cloud applications that are being used by the 10 Apache Software Foundation employees from the public (Press Releases, Customer References, Testimonials, Case Studies and Success Stories) and proprietary sources.
Apache Software Foundation has purchased the following applications: NodePing for Application Performance Management in 2022, Eclipse Jetty for Apps Development in 2007 and the related IT decision-makers and key stakeholders.
Our database provides customer insight and contextual information on which enterprise applications and software systems Apache Software Foundation is running and its propensity to invest more and deepen its relationship with NodePing , Eclipse Foundation or identify new suppliers as part of their overall Digital and IT transformation projects to stay competitive, fend off threats from disruptive forces, or comply with internal mandates to improve overall enterprise efficiency.
We have been analyzing Apache Software Foundation revenues, which have grown to $2.0 million in 2024, plus its IT budget and roadmap, cloud software purchases, aggregating massive amounts of data points that form the basis of our forecast assumptions for Apache Software Foundation intention to invest in emerging technologies such as AI, Machine Learning, IoT, Blockchain, Autonomous Database or in cloud-based ERP, HCM, CRM, EPM, Procurement or Treasury applications.
ITSM
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
| NodePing | Legacy | NodePing | Application Performance Management | ITSM | n/a | 2022 | 2022 |
In 2022, the Apache Software Foundation implemented NodePing as an Application Performance Management service to provide externally visible project and site status monitoring for the Whimsy project. The implementation is observable on the public Whimsy status page, which shows NodePing-originated status reporting. This positions NodePing as the infrastructure and status monitoring layer for the project.
NodePing is configured to provide uptime and availability checks, public status page feeds, and alerting for service incidents, reflecting common Application Performance Management capabilities such as synthetic checks and notification workflows. The deployment focuses on HTTP and endpoint monitoring and status publishing, supporting continuous visibility of site health. Configuration appears scoped to the Whimsy project and the project’s infrastructure and status functions rather than a broader enterprise rollout.
The integration with the Whimsy status page is the primary operational touchpoint, enabling public uptime reporting and real-time alerting for the project's infrastructure and status functions. Observed evidence is based on public status page signals and status reporting integration rather than a vendor case study, and outcomes explicitly include public uptime reporting and alerting for the project.
|
PaaS
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
| Eclipse Foundation | Legacy | Eclipse Jetty | Apps Development | PaaS | n/a | 2007 | 2007 |
In 2007, Apache Software Foundation embedded Eclipse Jetty to host Apache ActiveMQ's Web Console and REST endpoints for messaging administration and monitoring. This use of Eclipse Jetty is categorized as Apps Development and supports messaging and operations business functions for ActiveMQ.
Eclipse Jetty is deployed as an embedded HTTP servlet container within the ActiveMQ process, started by importing conf/jetty.xml that configures connectors, context handlers, and servlet mappings to expose the admin UI and web APIs. The ActiveMQ distribution explicitly imports conf/jetty.xml to provision the Jetty container and its servlet configuration at broker startup.
The architecture co-locates web hosting with the broker process rather than a separate web tier, so the Web Console and REST endpoints are served in process with ActiveMQ. Operational coverage centers on messaging administration, monitoring endpoints, and web based operations for deployments maintained by the Apache community in the United States.
Configuration and governance are handled through the conf/jetty.xml file distributed with ActiveMQ, enabling declarative control over servlets, security realms, and resource handlers used by the admin UI. Eclipse Jetty provides an in process web hosting model for ActiveMQ within Apps Development, aligning runtime hosting, configuration, and administrative tooling.
|
| First Name | Last Name | Title | Function | Department | Phone | |
|---|---|---|---|---|---|---|
| No data found | ||||||
| Date | Company | Status | Vendor | Product | Category | Market |
|---|---|---|---|---|---|---|
| No data found | ||||||