[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jetty-users] Vert.x-like functionality in Jetty?
- From: Simone Bordet <sbordet@xxxxxxxxxxx>
- Date: Thu, 24 May 2012 23:16:04 +0200
- Delivered-to: email@example.com
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=zVnG9GEdH1573xoM62dReAT3+sqiO+vHKJneLJA4ShE=; b=F/PdLef3oPplI9LNWcYBUnYgQI3T70PVSKgu2Eqcy0ZVHV/iEM4huLKJ3bHhpwm9We f51bRj1qnDL3pbBfZt04Cd4dl+XaJqhvaohE6AMS46SLn0lq1A0dY/5XSac1HEPcQppp Xgi/D0ah0k8CF7w7w3Xvu8+JaRKzQLr73WQxbkR4sowh2xYDAlDXKa8CL4OEjl6pru44 TwqclobPufXMW7IyKCP7EdgavvuwVmagGuY9XjzVPFPIX6R7ZkwmORMYPAoTlgAMr6bw yKpTiAJNggcR9OnWnfMNC1qQ1Ca79550Hih3J6Wj3xZkyBaGpT3DMN9SGOGy3s+V+jgb EA9A==
On Thu, May 24, 2012 at 8:59 PM, Otis Gospodnetic
> Are you saying CometD provides the same scalability and concurrency Vert.x
> claims to provide?
Look carefully at the Vert.x benchmark: they open 6 (six) connections
and pipeline on each 2000 requests.
How realistic is such traffic ?
I am sure Vert.x 1.0 is a fine framework and all that, but I'd like to
see a more realistic benchmark before expressing an opinion.
That is what we tried to achieve with the CometD benchmark, which
implements a chat application, with 1k, 5k 10k up to 200k connected
users to a single server and different message rates.
> If CometD provides (and has been providing for years) the high scalability
> and concurrency support, what's all Vert.x all about?
Ask them :)
To me, it's about diversity.
Why there exist more than one servlet container ?
> Is it the case that
> while CometD may provide the same stuff Vert.x does, CometD is not widely
> known or is at least not as popular? (if so, that can be critical for its
Not sure what Vert.x provides yet (have not looked in details), but
CometD provides authentication hooks, fine-grained access control,
message acknowledgment and guaranteed server-to-client message
delivery on short network failures, a fully extensible framework,
transport independence and fallback, automatic reconnections, and I
can continue for a while.
I heard about Vert.x one month or less ago, actually, so I personally
do not classify it as "popular" just because it had a spike in tweets.
Evaluate both frameworks and choose the one that fits your case better.
You have not said what is it in Vert.x that appeals you. It's just the
benchmark result ?
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.ÂÂ Victoria Livschitz