Best Practices For Node.js App Development

  • It is of course very easy to get started on those Node.js projects but once you get beyond the basic “Hello World” application, knowing how to deal with errors and managing the right structure of your code seems a nightmare.
  • Let us look at few of the best Node.js practices that can protect you from the common Node.js traps:

    Prototypal inheritance is when objects inherit from other objects.

  • Below is the code by TJ Holowaychuk, the genius behind Express, Connect, Mocha and dozens of other Node modules.
  • You must always ensure that your node.js application is error free because errors bring down your entire application.
  • Developers must have handy tools for monitoring performance of node.js applications.

Node.js, a platform built on Chrome’s JavaScript engine helps to develop fast, scalable network application. It uses an event-driven, non-blocking I/O model which makes node.js lightweight and efficient. Node.js has become one of the most popular platforms over the last couple of years. It is of course very easy to get started on those Node.js projects but once you get beyond the basic “Hello World” application, knowing how to deal with errors and managing the right structure of your code seems a nightmare.
Continue reading “Best Practices For Node.js App Development”

Where to go next, after AngularJS

  • Home » News » Uncategorized » Where to go next, after AngularJS

    Where to go next, after AngularJS

    With the rapidly changing landscape of web user interfaces and the added factor of emerging standards around Web Components, the role of supporting JavaScript frameworks in web development continues to change rapidly.

  • Our Web UI Centre Of Excellence Team investigated the key JavaScript framework alternatives by building some core application functionality in Angular 2, ReactJS, and Polymer.
  • In this paper after briefly introducing the three web UI frameworks, we discuss:

    How we investigated
    What we investigated
    What we found
    Conclusions

    were hiring

    Intelliware Web UI CoE Team
    The Web UI CoE consists of a team of Intelliware experts that focuses on web front-end technology.

  • Overall, the goals of this team are to provide relevant insights on upcoming frameworks; create and distribute web components and tools; and help projects deliver faster by producing best practices and migration guides and propagating them throughout our delivery organization.
  • Please contact us for a more detailed discussion on the frameworks and our experiences – we’re happy to talk about it.

With the rapidly changing landscape of web user interfaces and the added factor of emerging standards around Web Components, the role of supporting JavaScript frameworks in web development continues to change rapidly. Our Web UI Centre Of Excellence Team investigated the key JavaScript framework alternatives by building some core application functionality in Angular 2, ReactJS, and Polymer. The Developer Experience was a key focus during our investigation.
Continue reading “Where to go next, after AngularJS”

GraphQL as a best practice for modern Angular apps?

  • GraphQL as a best practice for modern Angular apps?Angular, meet GraphQLIn this post, I’ll make the case for why Angular needs a best practice for communicating with the server, and why GraphQL should be that best practice.Best practicesThe Angular community is establishing best practices so that we all can benefit from making our apps more performant, easier to maintain, and more modern.Some of the current best practices include composing everything into Components, using one-way data binding, lazy loading, having an immutable global state management (Redux ng-rx), and more…That is all great, and means that if we will follow those best practices our apps will behave better and will look more modern……until we get to data fetching from the server.Data fetchingToday, whether we are developing in a large company, consulting, or writing our own app, when we fetch data from the server we are often left with old practices that don’t address the needs of a modern app.Also, we are kind of powerless and unable to decide how the data will be supplied to our apps by the server, even though the way we fetch the data to our app is at least as meaningful to the way our app behaves as how we present it.We should come up with best practices for data fetching that is more in line with the modern way we write our apps.
  • These should take into consideration the following needs: data documentation, network latency, server side rendering and faster initial loading, real time communication patterns, latency compensation, and optimistic UI.RESTREST is the current protocol we go around when we talking about app data fetching.
  • REST has its benefits, but it was evolved in a time where the web was very different from today, when everything was about static HTML and forms and not about apps.Here are the areas where REST is currently lacking:self documentation — when you send a request to a REST endpoint, there is nothing in the protocol that tells you what you are going to get (and not everyone has the resources to create a nice, updated documentation like Twitter)REST doesn’t support real time data fetchingtough choices when designing your REST endpoint, which I’ll elaborate on belowOver-fetching — When one endpoint serves all the data, each Component calls it again and again.
  • This creates many round trips for one Component as well as complex joins on the client.The Discourse REST API — look on the links at the bottom on the GraphQL version of thisRethinking data fetchingSo it looks like we need to rethink data fetching, just like we rethought web apps.Luckily, Facebook ran into the same problem in 2012 when they needed to rethink the way they fetch data as they wrote their mobile apps on top of their existing stack.They developed a solution, and open sourced it as GraphQL.GraphQLGraphQL is the new data communication protocol for modern apps.The server communicates what data it can provide and the client specifies what data it needs in a simple, graph-like structure, in one round trip, no matter how deep, how complex, or how many resources the data contains.GraphQL has built in documentation so any server can use the GraphiQL editor without the need of setupThis means: one request to get exactly the information the app needs, when it needs it.
  • You can connect it to an existing REST endpoint or SQL and NoSql databases.Shared best practices between frameworksFor all the reasons above, GraphQL is already the best practice for fetching data with React.

In this post, I’ll make the case for why Angular needs a best practice for communicating with the server, and why GraphQL should be that best practice. The Angular community is establishing best…
Continue reading “GraphQL as a best practice for modern Angular apps?”

Now might be the best time to replace your AngularJS Applications

  • Angular2 has been on the radar for quite a while, and so has the desire to retire legacy AngularJS applications.
  • However, with Angular2 in transitional development for over a year, and the ability to deliver better and faster than ever with AngularJS, most companies have still decided not to change.
  • As we all know, Angular2 is quite different than AngularJS — it’s arguably a different framework.
  • With AngularJS ending its life, and the rise of new standards such as web components, as well as the availability of enterprise-ready frameworks like ReactJS, Angular2 or even Polymer, we believe now is a great time to reconsider your UI strategy and pave the way for future revolutions.
  • Clearly frameworks and browsers are both going in a different direction than AngularJS.

Angular2 has been on the radar for quite a while, and so has the desire to retire legacy AngularJS applications. However, with Angular2 in transitional development for over a year, and the ability to deliver better and faster than ever with AngularJS, most companies have still decided not to change.
Continue reading “Now might be the best time to replace your AngularJS Applications”

SharePoint and AngularJS Lessons Learned from the Trenches

Here is a video that I presented on #SharePoint and #AngularJS as part of @COLLA365

  • Thanks to SharePoint 2013 it is a lot easier to be able to create client based solutions.
  • AngularJS is one of the solutions out there that allows developers to create applications very quickly through an MVC implementation.
  • In this session we will go over the basics of AngularJS in regards to apps, controllers, services and views.
  • The principles learned here can be used anywhere in SharePoint whether it is a Farm Solution in an on-premises environment or in an app on Office 365.
  • Come learn a lot of the pitfalls to avoid and some best practices that will help you love AngularJS as another tool in a developers tool belt.

Thanks to SharePoint 2013 it is a lot easier to be able to create client based solutions. AngularJS is one of the solutions out there that allows developers to create applications very quickly through an MVC implementation. In this session we will go over the basics of AngularJS in regards to apps, controllers, services and views. We will create a simple application built entirely through client technologies and in SharePoint. The principles learned here can be used anywhere in SharePoint whether it is a Farm Solution in an on-premises environment or in an app on Office 365. We will also explore some of the issues that you are likely to experience with the release of AngularJS 2.
Continue reading “SharePoint and AngularJS Lessons Learned from the Trenches”

Jumping into ng2 with Angular CLI

  • For this we invited an experienced tutor that will introduce you to the power of the Angular CLI!
  • This is also a great opportunity to connect with other Angular developers, whether you are one yourself or just want to find out what it is all about.
  • Angular2 has been production ready for about 5 months now, and along with all of the other exciting improvements it offers, there is also an official CLI tool for generating and maintaining projects, currently in a late beta release.
  • The angular-cli is a great way to hit the ground running with your first Angular2 project for both beginners and experienced Angular developers.
  • Having learned the hard way that his passion lies in product development he now specializes in helping others develop their projects efficiently and effectively using best practices and the latest production ready technologies.

Second month of 2017, and time for our second Angular talk this year!
We know that a lot of you are interested in hands-on activities, and even more want to start now with Angular 2. For this we invit
Continue reading “Jumping into ng2 with Angular CLI”

How to connect to the API backend Angular.js

How To Connect To The #API Backend #AngularJS  #javascript #AppDev #webdev #devops

  • Post() will create a new record, get() will get a record, etc.
  • We can go directly to the code.
  • It is performed only when the completed request to add transaction.
  • To get yourself a transaction, we can either use then() , a method of $object , which immediately returns us all transactions.
  • We ensure that the array is updated only after the transaction is successfully saved a new transaction to the server.

In this article we will learn how to connect our application with a simple API using Restangular library. Restangular – a popular alternative to the built-in self Angular.js library for working with REST API. On its advantages over the standard library are well described on the project’s page at github: https://github.com/mgonto/restangular. For example, it supports all the HTTP methods and devoid of various nasty bugs embedded in Angular.js library.
Continue reading “How to connect to the API backend Angular.js”