Return-Path: X-Original-To: apmail-helix-user-archive@minotaur.apache.org Delivered-To: apmail-helix-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 45C6318E3D for ; Sat, 5 Dec 2015 23:50:24 +0000 (UTC) Received: (qmail 3903 invoked by uid 500); 5 Dec 2015 23:50:18 -0000 Delivered-To: apmail-helix-user-archive@helix.apache.org Received: (qmail 3860 invoked by uid 500); 5 Dec 2015 23:50:18 -0000 Mailing-List: contact user-help@helix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@helix.apache.org Delivered-To: mailing list user@helix.apache.org Received: (qmail 3840 invoked by uid 99); 5 Dec 2015 23:50:17 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Dec 2015 23:50:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 27CF31809CB; Sat, 5 Dec 2015 23:50:17 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.88 X-Spam-Level: ** X-Spam-Status: No, score=2.88 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 6eKUp0eTdiEB; Sat, 5 Dec 2015 23:50:08 +0000 (UTC) Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com [209.85.213.182]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 740C542ADC; Sat, 5 Dec 2015 23:50:08 +0000 (UTC) Received: by igbxm8 with SMTP id xm8so60713412igb.1; Sat, 05 Dec 2015 15:50:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=DyWyZsuat9Fuhl0X2P8KRklHxrQnzj1Z5rbc86BhjTM=; b=CqgTSmYcASDBTGysWHsBKFuiek0AxXjKUKTEacaxaTynP16GigHL59j6teX4wl+C6y +yFJotgGWKdoiStNla2dyZAViFlPWgmDTu4mzBU1Pz2BSM543Q9W7Drg7mQyHjPX08y5 bj/lacJf+iUv65DePqGXQVw7aO/+Kda3f/OY7tiEdUF9awsfPwFA9/Y7LH+NjYGlqYv5 0MlYrGSHaaaqGhMZn7UjL53O9wWxwiIl8BSAY826M9g8OYdO5ssG0dneqvxGBGRQluTO 9t5a6XJkmj1De+klHpeB6WAt2C3vnKTUKUVLc4SgYLtb3pO7ckGptTRfbyKGwJZbckbc 1v4A== X-Received: by 10.50.8.72 with SMTP id p8mr9863796iga.67.1449359401982; Sat, 05 Dec 2015 15:50:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.35.136 with HTTP; Sat, 5 Dec 2015 15:49:42 -0800 (PST) From: Greg Brandt Date: Sat, 5 Dec 2015 15:49:42 -0800 Message-ID: Subject: dropwizard-helix To: "user@helix.apache.org" , "dev@helix.apache.org" Content-Type: multipart/alternative; boundary=089e01184c1a4ea0b805262f489f --089e01184c1a4ea0b805262f489f Content-Type: text/plain; charset=UTF-8 Hey, If you're not familiar with it, Dropwizard (http://www.dropwizard.io/) is a really good Java framework for building web applications. It has basically everything you'd need to build a web application - JDBI (or Hibernate), views, authentication, etc. and leverages solid existing components (Jetty, Jersey, Jackson, Metrics). One thing that it is lacking is the ability to easily deploy distributed applications, so I created a module that aims to make it very simple to use Helix to accomplish that: https://github.com/brandtg/dropwizard-helix Currently it only does really simple service discovery, but I think there are a lot of complementary features between the two frameworks that we could explore. For example, Dropwizard's task interface ( http://www.dropwizard.io/0.9.1/docs/manual/core.html#tasks) could leverage Helix's task framework to make running distributed tasks easy. My idea is to basically offer the Helix recipes as Dropwizard bundles, requiring no code from the user other than adding the bundle / config, then have an advanced mode where one can basically just provide state transition handler / factory class for things like master / slave. But the bundle would take care of all the details like computing instance name, connecting, etc. You can see it in use here: https://github.com/brandtg/dropwizard-helix/blob/master/src/test/java/com/github/brandtg/discovery/TestHelixServiceDiscoveryBundle.java -Greg --089e01184c1a4ea0b805262f489f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hey,

If you're not familiar with it= , Dropwizard (http://www.dropwizard.i= o/) is a really good Java framework for building web applications. It h= as basically everything you'd need to build a web application - JDBI (o= r Hibernate), views, authentication, etc. and leverages solid existing comp= onents (Jetty, Jersey, Jackson, Metrics).

One thin= g that it is lacking is the ability to easily deploy distributed applicatio= ns, so I created a module that aims to make it very simple to use Helix to = accomplish that:=C2=A0https://github.com/brandtg/dropwizard-helix

Currently it only does really simple service discovery, but I think there = are a lot of complementary features between the two frameworks that we coul= d explore. For example, Dropwizard's task interface (http://www.dropwizard.= io/0.9.1/docs/manual/core.html#tasks) could leverage Helix's task f= ramework to make running distributed tasks easy.

M= y idea is to basically offer the Helix recipes as Dropwizard bundles, requi= ring no code from the user other than adding the bundle / config, then have= an advanced mode where one can basically just provide state transition han= dler / factory class for things like master / slave. But the bundle would t= ake care of all the details like computing instance name, connecting, etc.<= /div>


-Gre= g
--089e01184c1a4ea0b805262f489f--