From: Joel Reymont <joelr1@gmail.com>
To: O'Caml Mailing List <caml-list@yquem.inria.fr>
Subject: huge low-latency ocaml cluster?
Date: Tue, 12 May 2009 16:30:16 +0100 [thread overview]
Message-ID: <90BE2851-C167-4B4C-AA0C-3BFA3AFA5658@gmail.com> (raw)
Does anyone have an API for Amazon EC2, S3 or SimpleDB?
I need to write an app to push content to hundreds of thousands
of users, connected to a bunch of servers. Think liveblogging.
You push a button and your post needs to be in front of eager
readers within a couple of seconds.
The client-facing interface is Flash sockets and HTTP.
I'm thinking of allocating up to 10k users per server so
clustering is a must. I haven't decided how to ago about it
but I'm wondering if it's time to resurrect Ensemble [1,2]!
Any advice or suggestions?
Thanks, Joel
[1] http://caml.inria.fr/pub/old_caml_site/caml-list/0315.html
[2] http://dsl.cs.technion.ac.il/projects/Ensemble
---
Mac hacker with a performance bent
http://linkedin.com/in/joelreymont
next reply other threads:[~2009-05-12 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 15:30 Joel Reymont [this message]
2010-03-26 4:01 ` [Caml-list] " William Le Ferrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=90BE2851-C167-4B4C-AA0C-3BFA3AFA5658@gmail.com \
--to=joelr1@gmail.com \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).