Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why did we choose Hapi? #129

Open
chapel opened this issue Nov 8, 2014 · 0 comments
Open

Why did we choose Hapi? #129

chapel opened this issue Nov 8, 2014 · 0 comments

Comments

@chapel
Copy link

chapel commented Nov 8, 2014

As some of you may know I work at WalmartLabs (the incubator of Hapi thanks to @hueniverse and team). What many don't know is that I don't work with @hueniverse and the choice to use Hapi was made by solely by our team based on the features and support Hapi had at the time, and has proven to only get better since then.

I would like to talk about what we were using before Hapi as well as how we decided on choosing Hapi over sticking with Express or using something like Restify. Finishing up with how it has performed for us over the last year and a half.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants