Mic Majewski wrote:Hi Kanika,
congrats on your publication!
I was wondering what's your perspective on comparison between hapi vs. express(as the most popular one) and also other frameworks out there (for example Sails, Koa).
I'm in the beginning of the coding journey, having some grasp on express, but no experience with other frameworks.
Would your recommendation (for greenhorn) be to choose hapi as first framework to dive into deeper or you would say to really be able to use hapi potential you need strong express fundamentals?
Cheers!
Hi Mic
I've answered the same question on other threads in the same forum.
What I keep telling professionals is to notice the context when choosing a framework. For an app with a large team, you'd not choose a framework like express because the same thing can be done in so many ways. Hapi though provides a guided, fixed approach to doing things.
When you are grasping a new language, don't stop at one framework, learn two or three. Because you're most likely to use them alternatively.
When performance is a key factor, use native node instead of a framework.
I come from a
Java background, and I know that the pitfalls of Hapi are more often than not because of the nature of JavaScript engines. Nothing like Java.
For quick to launch apps, Hapi does give a lot of support with a good backing. I haven't observed pitfalls in performance when I used it for an app with 50,000 hits on the database because my performance was measured in terms of query optimization.
For me a good framework means a good backing(like Walmart in this case), a structured approach, stable versions, community support and structure in the Frame itself.many times the choice is governed by the nature of the app.
