4 ms·

Looks like a pretty cool product, especially for those who want to add on small real-time features to their application but don't want to have to deal with even

Looks like a pretty cool product, especially for those who want to add on small real-time features to their application but don't want to have to deal with evented servers/browser support/etc. I started looking into doing something very similar about a year ago based on having those exact needs actually (the project was eventually scrapped). - The cost is listed as per million messages - what happens if I deliver 900,000 messages, what am I charged (if anything)? - Care to share any details about your infrastructure? - Have you thought about writing (and open-sourcing) a simple demo app, such as a chat room, to give people an idea of how everything works together?

cgbystrom 16y ago
Thanks for your feedback! 1. Right now we offer up to one million messages for free. After that, we charge per each initiated million messages delivered. Meaning, if you send 900 000 you will be charged for 1 MM. Much how Amazon bills hours on EC2. 2. Well, sure. Our endpoint server (where all browsers connect) is written in Java. We're using the Netty framework, which we are incredibly happy with. Highly recommend it for doing high-performance networking in Java. Also, using the JVM instead of, say node.js, makes it very easy to utilize all our CPUs. The user-facing website is implemented in our own framework called Planet. Developed in-house using Python with focus on real-time web sites. Both Beacon and Planet share the same underlying push technology and we have some major customers using it. You can read more about it at http://www.esn.me http://www.esn.me The REST API is also implemented in Python and coordinates the message sending among our end-point servers. It's quite simple actually, just 200 lines of code. 3. Sounds like a good idea. It's just a few lines of code that's needed to integrate it. But yeah, a simple chat app hosted on GitHub would be helpful for newcomers. -- Carl

cgbystrom 16y ago

Thanks for your feedback! 1. Right now we offer up to one million messages for free. After that, we charge per each initiated million messages delivered. Meaning, if you send 900 000 you will be charged for 1 MM. Much how Amazon bills hours on EC2. 2. Well, sure. Our endpoint server (where all browsers connect) is written in Java. We're using the Netty framework, which we are incredibly happy with. Highly recommend it for doing high-performance networking in Java. Also, using the JVM instead of, say node.js, makes it very easy to utilize all our CPUs. The user-facing website is implemented in our own framework called Planet. Developed in-house using Python with focus on real-time web sites. Both Beacon and Planet share the same underlying push technology and we have some major customers using it. You can read more about it at http://www.esn.me http://www.esn.me The REST API is also implemented in Python and coordinates the message sending among our end-point servers. It's quite simple actually, just 200 lines of code. 3. Sounds like a good idea. It's just a few lines of code that's needed to integrate it. But yeah, a simple chat app hosted on GitHub would be helpful for newcomers. -- Carl