I published this essay Contrasting Enterprise Node.js Frameworks: Hapi vs. Kraken vs. Sails.js vs. Loopback on the Capital One engineering blog . Feel free to leave a comment! Here’s a blurb:
As with any new platform, there are a lot of Node.js/Io.js frameworks to choose from. However, before we proceed, we need to define what enterprise means. For the sake of simplicity, an enterprise project is one where you have teams of more than 10 developers working on it, where you have huge traffic to handle and high stakes, meaning the services must be running 24x7x365.
Judging frameworks is highly subjective. When it comes to building enterprise-level applications, we need to consider some of the following things:
- Best practices and patterns: Whether the framework is DIY or provides clear patterns to use.
- Configuration: How easy it is to configure the framework.
- Convention: Is there a convention to follow if that’s the preferred route?
- Horizontal scaling: How easy it is to scale apps built with this framework.
- Testing: How to test the application.
- Scaffolding: How much developers have to code manually vs. using built-in code generators.
- Monitoring: How to monitor the application
- Track record: How proven a framework is, i.e., who supports it and how well it is maintained.
- Integration: How rich the ecosystem of plugins/connectors is.
- ORM/ODM: Is there an object relational/document mapper.
While performance is important, it varies on the requirements and business logic of a particular project. Running meaningful benchmark tests is non-trivial.
The main focus of this post is to compare the four Node.js/Io.js frameworks: Hapi, Kraken, Sails.js and Loopback.
The full essay is at http://www.capitalone.io/blog/contrasting-enterprise-nodejs-frameworks.
Most of the people outside of Capital One think of it as a bank with those visigoths commercials and the “What’s in your wallet?” slogan. Few people know that Capital One is a startup in the financial world if you compare it other big names such as Wells Fargo, Bank of America or Chase. Capital One started only a couple decades ago as a data driven technology company. Before it, there was only one type of credit card and people with less than stellar credit just weren’t eligible for it. Capital One revolutionized the credit card industry by analyzing risks and consumer profiles. It turned out to be a big success. Then came the visigoths, along with the acquisitions of traditional brink and mortar (such as Chevy Chase) and online banks (ING DIRECT which is Capital One 360).
I hated Jade as many other Node.js developes do. But I changed 180 after I realized that it has tons of features.
At Storify and DocuSign we used Jade for EVERYTHING. We used Jade even in the browser. There is a little trick called jade-browser. It was developed by folks at Storify. I maintained it for a bit.
The funny thing is that DocuSign team used jade-browser long before they met me. They swear they hired me without knowing that I was involved in that library. :-)
Anyway, after covering Jade and Handlebars in previous posts, it’s time to apply them to do some real work. In this post, I’ll cover:
- Jade and Handlebars usage in Express.js 4
- Project: adding Jade templates to Blog
Getting a job of your dreams might be easier than you think. Apply these five hacks and see for yourself.
Study after study has showed that being satisfied and happy at a job is paramount for a healthy, productive and long life. In other words, if you’re miserable at a job, then other areas of your life will suffer as well: personal life, health, spirituality, family, friends, etc.
Here are the 5 Hacks that will help you to get your dream job:
- Write a book
- Create a strong web presence
- Boost your LinkedIn profile
- Speak at a conference
- Take a MOOC (Massive open-online course)
You can use these five hacks to get the job of your dreams in pretty much any industry or field. And most of them will cost you nothing or close to nothing!
Of course, any of these hacks are useless if you don’t know what your dream job is. If you are not sure, then before reading any further, answer these questions:
- How much money do you want to make in a year or an hour?
- How much maximum commute can you tolerate (e.g., 30min, 1hr)?
- Do you like a certain area of your city?
- Do you want to work with certain technologies or in a particular industry?
- What kind of benefits do you want to have (ideally)?
Go crazy with these questions, let your fantasies go wild… yet remain realistic, otherwise you won’t believe it’s possible.
We are not separate people when we go to work and come back from it. We cannot separate our jobs from the rest of our lives. The quality of your job and its factors are in direct proportion to your happiness and physical and mental health.
So let’s start with my favorite hack.
I’ve wrote how I struggled with Jade, but I had no choice except to master it. However, before beginning to understand Jade, I admired Handlebars GREATLY. I did it mostly for its simplicity and similarity with plain HTML.
If you want to write templates for Node.js apps, then consider Handlebars. This short tutorial will get you started on the path of becoming a pro. And if you haven’t even heard about Handlebars, then you’re missing out big time!
Here’s the outline of this post:
- Handlebars syntax
- Handlebars standalone usage
When I started working at Storify as a Node.js Engineer. The tech stack was Express and Jade. I hate to admit it, but I struggled with Jade a lot!
Before, I mostly worked with Underscore, and Handlebars. I attempted to modify some HTML in the Jade templates. Other times I would only change the text. Those were trivial updates, but very often they cause the whole server to crash.
I was failing miserably to learn by trail and error. I hated Jade. I was starting to hate editing templates as well. Then I had a light bulb moment: I need a tutorial. I went to the official docs. I wish this article existed at that time. After spending just an hour learning Jade, I was able to use Jade and make all the changes to templates smoothly.
Smart people learn by their mistakes, and wise people learn from others. Don’t repeat my folly. Skim through this Jade tutorial to harness the power of this wonderful template language.
The goal of this mini-project is to add a few tests for Blog.
The project is on GitHub at https://github.com/azat-co/blog-express.
We won’t get into headless browsers and UI testing, but we can send a few HTTP requests and parse their responses from the app’s REST end points.
Test-driven development (TDD) , as many of you might know, is one of the main, agile development techniques. The genius of TDD lies in increased quality of code, faster development resulting from greater programmer confidence, and improved bug detection (duh!).
Historically, web apps have been hard to autotest, and developers relied heavily on manual testing. But, certain parts such as standalone services and REST API can be and should be tested thoroughly by the TDD. At the same time, rich user interface (UI) / user experience (UX) can be tested with headless browsers such as PhantomJS.