Install openmama with Homebrew

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• atomicbookbuilder
• atomicbookticker
• auctionticker
• bookpublisher
• bookticker
• bookviewer
• comboticker
• currencyticker
• fundamentallisten
• mamaftmemberc
• mamaftmembercpp
• mamainboxc
• mamainboxcpp
• mamaio
• mamaiocpp
• mamalistenc
• mamalistencachedc
• mamalistencachedcpp
• mamalistencpp
• mamamultisubscriberc
• mamaproxyc
• mamaproxycpp
• mamapublisherc
• mamapublishercpp
• mamasubscriberc
• mamasubscribercpp
• mamasymbollistsubscriberc
• mamasymbollistsubscribercpp
• mamdalisten
• multipartticker
• multisecurityticker
• newsticker

Project history

The project emerged from technology developed by NYSE Technologies and earlier Wombat Financial Software work, then moved into a vendor-neutral open-source setting. The Linux Foundation described OpenMAMA in 2012 as a Linux Foundation Labs project whose first year completed the open-sourcing of the stack, including OpenMAMDA and language support for C, C++, Java, and .NET.

OpenMAMA later moved under FINOS governance. The FINOS GitHub repository states that OpenMAMA was accepted as a FINOS project in October 2020 and that the project charter was approved by the FINOS Governing Board on 2020-10-21.

Adoption history

The 2012 Linux Foundation milestone announcement named participants including Bank of America Merrill Lynch, IBM, EMC, Exegy, Fixnetix, J.P. Morgan, and NYSE Technologies. It also listed bridges for Qpid AMQP, Avis, Bloomberg Open API, Data Fabric Multi Verb, Exegy, LBM, Rai, and IBM WebSphere Front Office work, showing that adoption centered on bridgeability rather than a single broker.

The OpenMAMA FAQ frames the project as a way for financial-services firms, market-data vendors, and technology firms to reduce middleware lock-in and standardize event-driven market-data applications across multiple transports and payloads.

How it is used

Developers use OpenMAMA by writing market-data publishers and subscribers against one API, then loading an appropriate bridge for the deployment's middleware. The quick-start documentation demonstrates a subscriber that connects to an OpenMAMA-compatible data source configured through mama.properties.

The API adds market-data features that generic messaging stacks lack, including subscription management, entitlements or permissioning, and data-quality handling. OpenMAMDA builds on top of MAMA with higher-level market-data types for trades, quotes, order books, program trading, and tick-capture systems.

Why package nerds care

For package nerds, OpenMAMA is a rare open-source artifact from institutional market-data infrastructure. Its formula exposes a stack that is less about a single daemon and more about ABI, bridge plugins, examples, and language bindings meant to let high-volume financial systems change transports without changing application code.

Timeline

• 2011: OpenMAMA was announced under Linux Foundation Labs, according to the Linux Foundation's 2012 one-year milestone announcement.
• 2012-11-28: the Linux Foundation announced that the OpenMAMA software stack was completely open source and listed multiple middleware bridges and industry participants.
• 2020-10-21: the FINOS Governing Board approved the OpenMAMA project charter.

Related projects

• OpenMAMDA is the market-data framework layered on MAMA. Related bridge targets and ecosystems include Qpid AMQP, Avis, Bloomberg Open API, 29West LBM, Tibco Rendezvous, and other market-data middleware products.

Sources

• https://danielpocock.com/en/openmama-packaging-free-software-for-free-markets/
• https://github.com/finos/OpenMAMA
• https://openmama.finos.org/faq.html
• https://openmama.finos.org/quickstart.html
• https://openmama.finos.org/reference/mama/cs/classWombat_1_1Mama.html
• https://www.linuxfoundation.org/press/press-release/financial-services-industry-advances-high-performance-messaging-with-openmama-project