Install apache-geode with Homebrew

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• gfsh

Project history

Geode's codebase predates Apache incubation by more than a decade. ASF's top-level project announcement says it was originally developed by GemStone Systems in 2002, with GemFire as the commercial distribution. Pivotal later owned the technology and submitted the Geode code to the Apache Incubator in April 2015.

Geode graduated as an Apache top-level project in November 2016. The incubation record shows several milestone releases in 2016 before graduation, including 1.0.0-incubating milestones and the 1.0.0-incubating release.

Adoption history

Before its Apache life, the technology behind Geode was already used in finance; ASF's announcement describes GemFire as first widely adopted by the financial sector for Wall Street trading platforms. At graduation, ASF described the technology as used by over 600 enterprises for low-latency, always-on applications such as risk analysis, high-volume ecommerce, and transportation/logistics management.

That commercial-to-Apache path makes Geode unusual among Homebrew data packages: it is not a small developer utility that grew upward, but a mature enterprise distributed system made installable as an open source package with gfsh as the practical command-line entry point.

How it is used

The packaged executable is gfsh, Geode's shell for starting locators and servers, creating regions, querying data, deploying code, inspecting metrics, exporting config, and administering clusters. The docs also describe Java client/server APIs, OQL queries, WAN replication, Lucene integration, Pulse monitoring, and cluster configuration.

Geode configuration commonly involves gemfire.properties for member behavior and cache.xml for cache and region definitions. Apache's docs say security-related properties can be placed in gfsecurity.properties to restrict access to sensitive settings.

Why package nerds care

Geode is a package nerd's reminder that a single CLI can front a serious distributed system. A Homebrew install gives you gfsh, but behind that are locators, servers, regions, serialization formats, security properties, XML cache definitions, and a long enterprise compatibility tail.

The package is also historically interesting because its file names retain GemFire heritage: gemfire.properties and gfsecurity.properties remain the canonical configuration names even under the Apache Geode project.

Timeline

• 2002: Original codebase is developed by GemStone Systems.
• 2015: Pivotal submits Geode to the Apache Incubator.
• 2016: Apache Geode 1.0.0-incubating milestone releases appear.
• 2016: Apache Geode graduates as an Apache top-level project.

Related projects

• GemFire is the commercial predecessor/distribution history behind Geode.
• Apache Apex, Spring Data for Apache Geode, Lucene, JMX, and Java client/server applications are common neighboring technologies.

Sources

• https://geode.apache.org/docs/guide/20/reference/topics/gemfire_properties.html
• https://github.com/apache/geode
• https://incubator.apache.org/projects/geode.html
• https://news.apache.org/foundation/entry/the_apache_software_foundation_announces102