Introduction to AMPS
Welcome to the Advanced Message Processing System (AMPS) from 60East Technologies! AMPS is designed to help you quickly and easily develop and deploy data-intensive applications, with demanding requirements, for low latency and high performance. AMPS takes a nontraditional approach to messaging, storage, and analytics that is designed from the ground up for streaming data and highly-parallelized multicore systems.
AMPS isn't a traditional database or messaging product. This guide presents a brief introduction to help you understand the capabilities of AMPS and how AMPS operates.
AMPS is widely used for applications such as:
Tradeplant operations (including backtesting and historical analysis)
Risk calculations
Elastic worker farms
View servers
Message flow integration and "shock absorbers"
AMPS combines a set of capabilities that cut across traditional boundaries between applications that work with data.
AMPS is built around a fast messaging engine that supports both publish and subscribe (fan-out) and queued (competitive consumption) message delivery with full content filtering.
AMPS also provides an integrated database that applications can use as a current value cache, key/value document store, and fully queryable database -- or all of these at once. With this database, AMPS includes a built-in aggregation and analytics engine for near-real time analysis of streaming data, including aggregation across multiple topics or message formats.
Integrated message logging provides the ability to record and replay streams of messages with full fidelity.
AMPS is designed from the ground up for enterprise deployment at scale. AMPS provides an extensive set of high-availability features, including integrated replication and automatic failover and recovery for applications. Detailed monitoring and statistics are included from a RESTful interface for ease of data collection and integration with enterprise monitoring and management systems.
Authentication and entitlement capability applies to every operation in AMPS, for fine-grained control over permissions to meet enterprise policy and regulatory requirements. Access to data can be controlled at a topic level, at a message level (content-based security), or at the level of individual fields within a message (limiting the fields a given user has access to view).
60East developed AMPS to serve the needs of some of the most demanding data-intensive applications on the planet. The feature set and capabilities have been engineered for the highest levels of performance, designed for ease of use, and proven in production applications worldwide.
Getting to Know AMPS
AMPS is designed to be a developer friendly product. 60East recommends reading about AMPS with a running instance of AMPS and your development environment of choice available. Although 60East makes every effort to clearly describe how AMPS works, there is no substitute for seeing exactly how a running instance behaves (not to mention the advantages of being able to try out ideas or do quick prototyping while you read).
The table below lists the main parts of the AMPS documentation:
Overview of AMPS functionality.
This is a good place to start if you are new to AMPS or if you are familiar with older versions of AMPS.
Detailed description of AMPS functionality, including guidance and best practices.
If you have detailed questions about how AMPS works, refer to the AMPS User Guide.
Guide to AMPS configuration.
This guide shows the configuration file syntax and accepted values. The guide also includes useful examples of configuring commonly-used options.
Guide to the RESTful monitoring interface and the AMPS statistics database.
Use this guide when creating a monitoring strategy or when collecting statistics about an instance.
Description of the commands sent from an AMPS client to the AMPS server and responses from the server.
Client Language Developer Guides
Guide to using a client library to work with AMPS.
This guide uses the spark command line utility for basic examples for simplicity, although a production installation would use an application to perform these functions.
Last updated