Kanika Sud

Campbell Ritchie wrote:Why do you think there is one road?

Don't know, but personally something tires me about lack of direction.

When you are at career crossroads and you want to step out of technology development, what's the one road you should consider, keeping aside personal skills of course. What happens when you are multi skilled and you can't narrow down on one skill?

And after a failed startup what do you do?

Tim Moores wrote:I don't know if 6 out of 10 is all that impressive :-)

I also liked Sherin Mathew's answer here: https://coderanch.com/t/737598/languages/Practical-hapi-Hapi-Express

@Mic

Similar question
https://coderanch.com/t/737598/languages/Practical-hapi-Hapi-Express

One more thing

Always see how server requests and responses are chained in a framework. How database connectivity can be maintained.

I like the server object maintainability in Hapi. Provides quite a lot of options.
My only complaints with express are lack of community support, and too many ways to do the same thing - less maintainability.

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.

Congratulations guys.

I would welcome any queries throughout the reading of this book, and yes reviews here, on Amazon or anywhere are more than welcome.

You know where to reach me, yes?
kanika@codnostic.com
www.codnostic.com

Campbell Ritchie wrote:Welcome to the Ranch It shows even old discussions can still be interesting.

Considering this thread, we might as well start a forum on language.

Hi Tim,

That's a good question.
When making a choice for learning a new language, I suggest a framework that has a good to grasp learning curve.

When making a choice for an application, the performance of a framework is definitely a factor. Hapi would pass the test if your queries are well structured. I haven't noted a great fall in performance per say. Sometimes, the nature of the apps that you want is also a factor. The apps that I have worked on using hapi, used customer queries of a max 50,000 at the same instance. And it was good enough as per our client's expectations.

Personally, I come from a JAVA background, and unless a framework has a guided approach to solving problems, I don't prefer it. I don't let developers in a large team use Express, because of the way they can handle the same thing in so many different ways.

Here's something that you might go through(even though an old post):
https://dzone.com/articles/hapi-vs-express-in-2018-nodejs-framework-compariso

Note that Node.js is better in performance any day, but if you have to consider a framework at all, you'd consider the community behind it, the stability of its versions and the out of the box features provided by the framework. Choosing a framework in any language though is a matter of disucssion and requires context.

Happy Coding.

Hi Sathya, Good Question.

See a reply here:
Similar Question if you need to choose when learning.

And here if you need to see how to choose, when making an app.

The point about learning Hapi is the clarity of its docs, the convenient learning curve, the strong backing and then adapt yourself to all frameworks.

Also, the best part is that there is a particular approach to things in Hapi. Compared to the slightly loose approach of Express where the developer can make decisions about how to approach the problem. Hapi guides decisions.

Go through the following:
https://raygun.com/blog/hapi-vs-express/#:~:text=Both%20frameworks%20are%20extensible%20and,the%20abstractions%20provided%20by%20Hapi.
https://stackabuse.com/hapi-vs-express-comparing-node-js-web-frameworks/

My approach in all these years has been to take up a framework that I can grasp fast and to not stop at it. Learn other frameworks after you're clear with one. Because you're likely to encounter more than ne frameworks in a job.

As a solution, choose a framework which has a good balance of plugins and which also, guides a solution, unless of course you want complete control, and the system will never be coded by anyone else. In a large team, a guided framework works.

Thank you so much everyone!!!

Hi Jignesh

As mentioned this is the HapiJS framework on hapi.dev

Apart from that I talk about Rest APIs, asynchronous JavaScript, database connectivity. A reader has reviewed it on Amazon, and I would look forward to your reviews as well.

SunilK Chauhan wrote:Hi all,

I am thinking like in today's market Microservices are very demanding. And seems like apps like low in memory consumption and giving the same features compare to others is booming.

So I think node js is the language which comes as best in those parameters and also it can provide the same features by consuming less memory compare to java.

And also node can handle more requests than Java for the same api build.

So is it true that node js will be the replacement of Java in future?

Anu suggestions are welcome.

Thanks.

Not at all. Java was, and is more robust than Node.js
Node.js became popular because of the Everything in Javascript Approach, and those quick dirty applications which can stand a loosely written script. If your front end is controlled by Javascript, considering Node.JS for a backend is not a bad option at all. Java is always the first choice for high security systems, which want to target complex frameworks in the making. Smaller applications where a bunch of micro services is enough of the business logic - NodeJs is indeed helpful with feature rich frameworks and a less steeper learning curve.

Infact, my book discusses this in brief. https://www.apress.com/gp/book/9781484258040

Monica Shiralkar wrote:If one creates multiple services for a requirement, how can one ensure that no code is duplicated ?thanks

The best way is to keep the database normalised. If the database is normalised, no developer would write similar code, leave alone duplicate for different entities.