If you attended the meet up last month you probably saw me present an asynchronous HTTP library we've been working on at mDialog, called Smoke. At the end of the presentation, you may also have seen me promise to release it in June.
While the examples included are pretty simplistic, we're successfully using Smoke to power several fast, complex HTTP service components of our video streaming platform.
Please, take a look. I'd love to hear what you think. If it looks interesting to you, please note we're hiring: http://www.mdialog.com/careers.html#4
Also, is there any interest in another meetup? I know some of the other mDialog developers would love the chance to talk a little but about what they've been working on.
On Fri, Jun 8, 2012 at 11:19 AM, Chris Dinn <cd...@mdialog.com> wrote:
> Everyone:
> If you attended the meet up last month you probably saw me present an
> asynchronous HTTP library we've been working on at mDialog, called Smoke.
> At the end of the presentation, you may also have seen me promise to
> release it in June.
> While the examples included are pretty simplistic, we're successfully
> using Smoke to power several fast, complex HTTP service components of our
> video streaming platform.
> Please, take a look. I'd love to hear what you think. If it looks
> interesting to you, please note we're hiring:
> http://www.mdialog.com/careers.html#4
> Also, is there any interest in another meetup? I know some of the other
> mDialog developers would love the chance to talk a little but about what
> they've been working on.
On Fri, Jun 8, 2012 at 11:44 AM, Tom Switzer <thomas.swit...@gmail.com> wrote:
> Looks good, Chris. I'm up for another meeting.
> On Fri, Jun 8, 2012 at 11:19 AM, Chris Dinn <cd...@mdialog.com> wrote:
>> Everyone:
>> If you attended the meet up last month you probably saw me present an
>> asynchronous HTTP library we've been working on at mDialog, called Smoke. At
>> the end of the presentation, you may also have seen me promise to release it
>> in June.
>> While the examples included are pretty simplistic, we're successfully
>> using Smoke to power several fast, complex HTTP service components of our
>> video streaming platform.
>> Please, take a look. I'd love to hear what you think. If it looks
>> interesting to you, please note we're hiring:
>> http://www.mdialog.com/careers.html#4
>> Also, is there any interest in another meetup? I know some of the other
>> mDialog developers would love the chance to talk a little but about what
>> they've been working on.
I hope I can make it to the next one. By the way, I'm heading to the UK the week after next for the FastTrack to Akka course…anyone else from TO going?
> Congrats on getting Smoke out there.
> -------------------------------------
> http://www.tylerweir.com
> On Fri, Jun 8, 2012 at 11:44 AM, Tom Switzer <thomas.swit...@gmail.com> wrote:
>> Looks good, Chris. I'm up for another meeting.
>> On Fri, Jun 8, 2012 at 11:19 AM, Chris Dinn <cd...@mdialog.com> wrote:
>>> Everyone:
>>> If you attended the meet up last month you probably saw me present an
>>> asynchronous HTTP library we've been working on at mDialog, called Smoke. At
>>> the end of the presentation, you may also have seen me promise to release it
>>> in June.
>>> While the examples included are pretty simplistic, we're successfully
>>> using Smoke to power several fast, complex HTTP service components of our
>>> video streaming platform.
>>> Please, take a look. I'd love to hear what you think. If it looks
>>> interesting to you, please note we're hiring:
>>> http://www.mdialog.com/careers.html#4
>>> Also, is there any interest in another meetup? I know some of the other
>>> mDialog developers would love the chance to talk a little but about what
>>> they've been working on.
>>> Chris Dinn
>>> Technical Lead
>>> mDialog Corp
Good question. We looked at all those libs, some of them I liked a
lot. The short answer is that I wanted a tool that made HTTP services
easy to build with as little conceptual overheard as possible and
didn't feel any of them quite fit the bill.
Play2Mini was clearly an inspiration, but since it actually extends
the full-featured Play2 framework its DSL is relatively complicated,
designed for a wide variety of use cases we didn't need to support.
Spray is great, but it's big; it even contains its own HTTP client and
server libraries. Instead, Smoke uses Netty for async HTTP, which is a
project I'm pretty comfortable with and prefer to rely on.
Conceptually, BlueEyes is similar to Smoke. However, I feel Smoke
accomplishes a lot of the same goals in fewer lines of code and with a
model that's much easier to understand, at least for me.
We're generally training all our new hires on both Scala and Akka (and
hiring a lot). Having something that was conceptually easy to
understand was an important design goal. With Smoke, I can tell new
team members to read up on Scala, Akka, Netty and HTTP (good idea
regardless, I think) and have our (internally) ubiquitous HTTP library
make pretty good sense to them. It builds upon already familiar
concepts while trying to avoid introducing any new ones. Much of our
team comes from a Ruby background, where there's a strong tradition of
strong, focused, single-purpose libraries like this—do one thing and
do it well.
We have some internal improvements to Smoke that I'll push our team to
release today. After several months of usage on a variety of projects
it's held up pretty well, even at scale. If you choose to use it,
don't hesitate to contribute back, nothing would make me happier.
On Mon, Sep 10, 2012 at 4:23 PM, Ankur Mathur <ankursm...@gmail.com> wrote:
> Hey Chris,
> Smoke looks really good! We were looking for a lightweight framework to
> build an async REST API on Akka, and this fits the bill.
> I missed the last meetup, so I must ask - Why did you decide to build this
> beside Blueeyes, Spray, Play2Mini etc?
> Cheers,
> Ankur
> Technical Architect,
> Nurun Inc
> On Friday, June 8, 2012 11:19:33 AM UTC-4, Chris Dinn wrote:
>> Everyone:
>> If you attended the meet up last month you probably saw me present an
>> asynchronous HTTP library we've been working on at mDialog, called Smoke. At
>> the end of the presentation, you may also have seen me promise to release it
>> in June.
>> While the examples included are pretty simplistic, we're successfully
>> using Smoke to power several fast, complex HTTP service components of our
>> video streaming platform.
>> Please, take a look. I'd love to hear what you think. If it looks
>> interesting to you, please note we're hiring:
>> http://www.mdialog.com/careers.html#4
>> Also, is there any interest in another meetup? I know some of the other
>> mDialog developers would love the chance to talk a little but about what
>> they've been working on.
