* A-A-P is portable over many systems. At least most Unix variants, MS-Windows and possibly the Macintosh. * A-A-P is open source, free software. Most of it is under the GNU GPL. Interfaces and libraries are more free. * A-A-P is not a monolitic program. It is made out of separate modules with clear interfaces. Most of the work is done by existing tools. * Since network connections are slow and unreliable - and when using a laptop - a local copy of a file is often required. A-A-P caches files, obtains a new version when available and cleans up files that have not been used recently. * The more alternatives there are, the more choices a developer has to make. Making all these choices slows down development. Therefore A-A-P provides a preferred set of modules. Many people will be satisfied with most of these modules, but will still be able to use a different module where they have a preference. * A-A-P is available in a command-line version and in a GUI version. The command-line version works on a console and over a telnet connection. The GUI version is easier to use, but requires a windowing system. * A-A-P maintains a set of preferences. These are global to all projects but local to the user or system. This specifies where specific tools, libraries, documentation files, etc. can be found. This greatly reduces the need to configure a package when building or installing it. * English is used in the original code. Provisions are made to add translations through the use of message files. * Reliability is considered more important than fancy features. A-A-P is a tool you can rely on.

* Take GC tuning off the table–Forever Zing doesn’t use obsolete GC technology – the Azul C4 collector can NEVER “stop the world” No need to re-architect your application – use the working Java, Scala, and third party code you already have No need for additional JVM add-ons or off-heap kludges – Zing just works Zing is fully Java SE compliant, it meets the standards and passes the tests for Java SE 8, 7 or 6 And your peak latencies and outliers get much closer to your average latency * Deliver consistently better latency–24 x 7 x 365 Deliver the same level of performance at the 99.9th percentile as at the 90th Meet the needs of trading systems, matching engines, customer portals, and other peak-latency-sensitive apps Zing’s ReadyNow! technology solves the Java warm-up problem. No more stalls at market open. In tuned low latency applications, see peak latencies in the 1-3 millisecond range (with average latencies in the microseconds) Move from multisecond (or worse) interactive pauses to a few milliseconds Zing also delivers consistent performance for Web-based workloads, messaging and analytics, and JVM-based data platforms. * Better capitalize on your existing infrastructure Zing will take advantage of memory in modern Intel hardware, as high as 2 terabytes per JVM process. Carry more user traffic on existing infrastructure, utilizing all available cores and sockets. Reduce deployment and management complexity — use fewer JVM instances to carry same load Extend the lifespan of older Java applications whose traffic has grown past original design limits Find – and fix – production performance issues with Zing Vision, an always-on, no-impact diagnostic tool include free with Zing. Plug any Zing-powered application directly into your existing JMX monitoring framework. Leverage Zing in on premise servers, on public clouds like Amazon, using virtualization products like KVM, and in containers like Docker Use regular Linux distros, spanning stable versions of Red Hat, SLES, Ubuntu, Oracle Linux, and Amazon Linux, plus latency tuned distros like Red Hat Enterprise MRG Realtime. * Rethink how your Developers use Java Pursue architectures and application designs not practical with existing Java platforms capped by GC stall pain. Consider what your application could accomplish with 8 GB heaps. Or 50 GB heaps. Or 2 TB heaps. All with no extra GC pause penalty. Keep important data on the heap without extra effort working on GC issues or off heap tricks