• Routing
• Sessions
• HTTP requests
• Error handling

At times writing code from scratch for above things can be time consuming. But by using express it’s only a matter of few methods. Express also helps in organizing your code. EXPRESS.JS is a light-weight Web framework for Node.js which means we can build web applications using JavaScript. Since it is light, one can do many things faster and with less lines of code, than a traditional Web application built using multiple technologies.

• Express supports MVC Architecture with little bit of work.
• One can build RESTful APIs faster.
• We can use many templating languages like Jade or EJS which reduce the amount of HTML code we have to write for a page.
• Has support for NoSQL databases out of the box.
• It provides convenient, basic web-server creation/routing tools, which so essential to bare-bones node,js
• It uses very flexible, modular middleware pattern, where special middleware modules used to process different requests.
• It is very friendly to functional programming and usage of Node.js core concepts – Event-emitters, Async flow and Streams.
• It requires almost nothing to create and run the easy testable web server

Share

The post Node.JS Web Application:: Express appeared first on Blog.

A GraphQL request can be either a query (read operation) or a mutation (write operation). For both cases, the request is a simple string that a GraphQL service can interpret, execute, and resolve with data in a specified format. The popular response format that is usually used for mobile and web applications is the JavaScript Object Notation.

Why GraphQL?

• Single-round trip: All data is fetched in a single round-trip vs. multiple-round trips in REST. In our example above, for a REST client to get all products in each category, it would need to first fetch the store’s categories from one API endpoint, and then for each category fetch their products from another API endpoint.

• No over-fetching: A client has full control of fetching only data that it needs vs. in REST API, on the server-side we have to balance between minimizing multiple round-trips (‘n+1’ problem) and over-fetching; we can eliminate ‘n+1’ problem we described above if we make the API that returns store categories, also return all products, but another set of clients that just wants categories of a store will be over-fetching.

• One endpoint to access your data- Single API endpoint to server all data needs
• Retrieve only the data your client needs in a single request (flexibility)
• No need to tailor endpoints for your views
• No versioning

Share

The post GraphQL appeared first on Blog.

Share

The post MEAN stack (mongoDB, Express.js, Angular.js, Node.js) appeared first on Blog.

Node.js can handle the client and server requests asynchronously. The benefit that Node provides in handling many different queries in a blazing fast manner significantly helps in reducing the latency. Another excellent advantage of Node.js is that it comes with an event loop that helps to handle multi-user requests in an effortless manner. The ability to handle multi-user requests make Node.js ideally suited for building chats and gaming apps. One can easily observe how real-time web apps are becoming the “Next Big Thing.” Node is a scalable framework which is of a paramount importance for any startup. Node.js framework has been designed in a way that it helps to support the development of real-time web applications starting from scalability, reduced development cycles to ability to work on the front-end and back-end using the same programming language.

Share

The post Node.js appeared first on Blog.

Each array element holds data specific to that object. Think of a Web Store where you have lots of items for sale. Each item would be stored in one element with all the data like price, description, and even urls to pictures in it. You could then pull that data and use it in your site without hard coding each item to into your HTML template. It is a much-more compact way of transmitting sets of data across network connections as compared to XML. I suggest JSON be used in any AJAX-like applications where XML would otherwise be the “recommended” option. With the rise of AJAX-powered sites, it’s becoming more and more important for sites to be able to load data quickly and asynchronously, or in the background without delaying page rendering. Switching up the contents of a certain element within our layouts without requiring a page refresh adds a “wow” factor to our applications, not to mention the added convenience for our users.

Share

The post JavaScript Object Notation ( JSON ) appeared first on Blog.