Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #25159

6

60East Technologies Blog

Company blog · crankuptheamps.com/blogsystemsprogramming

60East Technologies Blog is the company blog at crankuptheamps.com, writing about systems and programming. Since 2014, 3 different Hacker News readers have linked it 6 times. It is still writing: the last post was on 2025-04-02, and you can follow it by feed.

Visit the blog
6mentions?
3HN people?
2014–2020first – last linked?
Links on Hacker News per year · peak 2 in 2017

Too few sampled comments (4) to say how often HN recommends it.?

Why HN links it

Linked as the homepage of AMPS, a commercial messaging system. Commenters mention it as an alternative to Kafka, Pulsar, RabbitMQ and NATS. No comment discusses the writing.

Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Overview of AMPS, a high-performance publish and subscribe engine with advanced scalability features.

What Hacker News says?

  1. Just because it's widely used doesn't mean it's good (see PHP). It's slow with single-threaded topics that usually max out around 25k msgs/sec, fragile with dropped connections, stalled queues, corrupted data, terrible clustering that breaks often and doesn't support sharding, has a silly HIPE mode where you can choose to compile the Erlang code for more performance which turns startup time into minutes, etc. It's p…

    Comment linking /

    on “Apache Pulsar is an open-source distributed pub-sub messaging system”
  2. Submitted Achieving the highest levels of Message Queue performance as a story · 1 points

    HN discussion
  3. Have you tried AMPS: http://www.crankuptheamps.com/

    Comment linking /

    on “Is PostgreSQL good enough?”
  4. Submitted Break the Chains of Version Dependency as a story · 1 points

    HN discussion
  5. There are other options. RabbitMQ [1] is the usual although clustering has always been fragile. If you dont care about open-source then there are plenty of other options like AMPS [2] or Solace [3]. The latter has a free edition. 1. https://www.rabbitmq.com/ 2. http://www.crankuptheamps.com/ 3. https://solace.com/

    Comment linking /

    on “Waltz: A Distributed Write-Ahead Log”
  6. NATS (and NATS Streaming) is a good implementation of fast messaging with streaming/persistence built in Go without the usual Kafka issues: http://nats.io/ Also AMPS for the commercial software version: http://www.crankuptheamps.com/

    Comment linking /

    on “Jocko – Kafka implemented in Golang”

Search all of HN for crankuptheamps.com