AMPS is a very robust system due to its amazing performance, flexibility, and reliability. 60East already provides client libraries for C/C++, C#, Java, and Python, and today we introduce the first version of our official JavaScript client that will power up both modern front end web applications and Node.js-backed back end applications.
Every system needs control, and AMPS is no exception. We already have a pretty powerful and flexible Admin module that provides various information about the AMPS instance and the host system, in several formats such as XML, JSON, CSV, and plain text. It is very convenient for applications, scripts, services... but what about humans? We, the people, prefer information processed and visualized. Among many other cool features that AMPS 5.2 introduced, this one is literally very easy to notice. Ladies and gentlemen, allow me to introduce the new admin interface: Galvanometer!
AMPS 5.2 is now available.
This release of AMPS includes new features designed to help manage extremely complex, high-volume data flows that require data transformation in the AMPS server — while maintaining the performance and ease of use that AMPS is known for. The release also includes a set of features designed to make AMPS easier to configure and administer, and a wide variety of other usability and performance improvements.
The Advanced Message Processing System (AMPS) from 60East Technologies is a state-of-the-art technology that powers up many of the Fortune 500 companies. Developers who tried AMPS love it and use it in their products.
In this post, we will revisit the topic of extending the AMPS client to provide a bookmark store for stateless clients. This post is in response to requests for a simple stateless store that does not provide all of the functionality of the local stores, but instead just makes it possible for an application with very simple needs to pick up a subscription after failover. The implementation that we will discuss here is fairly limited, but should provide a starting point for less restrictive implementations. Before we begin, I would like to encourage you to read No Filesystem? No Problem! Keeping State in AMPS in order to gain a deeper understanding of bookmark stores.
Here at 60East, we're dedicated to messaging. All messaging. All the time. Day in and day out.
AMPS 5.0 is now available.
This version of AMPS builds on the technology in previous releases to refine existing features and bring all new capability to AMPS.
The Advanced Message Processing System (AMPS) from 60East Technologies is used in production for thousands of enterprise messaging applications. These applications use AMPS because they have the most demanding throughput and latency requirements for publish/subscribe messaging. These applications also take advantage of the AMPS durable message storage, historical replay and audit, global replication and high availability, sophisticated aggregation and analytics, and more. The 5.0 release of AMPS adds durable message queues, built on the proven AMPS engine for the highest levels of reliability and performance.
I’ve been pondering for a while on how to showcase some replay functionality in our AMPS product in a way that’s general enough that everyone understands the concept, yet provides a solution metaphor that easily translates into other domains. Ideally, the data would be from some real-world system, where time-series, ordering, and content filtering could be useful (again, leveraging the features of the product I’m trying to explain.)
Why is it that the latest Bugatti Veyron doesn't have the fastest time at the Top Gear test track? How could a highly regulated or constrained 2004 Renault R24 Formula One outperform it? The Bugatti outperforms the F1 in many tests; but not on that prestigious Top Gear track due to the design trade-offs their designers made. We also don’t know if the driver of the Bugatti really was in tune with this vehicle. Martin Thompson provides an excellent metaphor from racing to software development in his blog Mechanical Sympathy.
“I may not have gone where I intended to go, but I think I have ended up where I needed to be.” ― Douglas Adams, The Long Dark Tea-Time of the Soul
In the Hitchhiker’s Guide to the Galaxy, Douglas Adams conveyed to us that the earth was actually a computer system designed to calculate the meaning of life. SPOILER ALERT: the answer was 42. Unfortunately, not all our answers come out as a concise short int format. Many of the simulation farms or grids that AMPS is deployed in produce vast amounts of data. This data is often an intermediate step in a workflow of calculations. In fact, we get asked about the movement of large data sets so often that we previously devoted an entire blog post to the topic. In this article, we are going to highlight how we can be flexible in our treatment of very large messages through the use of the new AMPS composite message types.
At 60East, we've been heads down in the lab, mixing up new ingredients to bring you the future of messaging today. We've just released AMPS 4.3.1.0.
This release focuses on extending the futuristic capabilities we introduced in AMPS 4.0, making AMPS even better!