The Backend process of TaxiApp Backend are built using the core components of Node, Express, MongoDB, Passport JS. TaxiApp Backend has also been constantly incorporating various other latest technologies.
Ideally, if you are writing a mobile app, you want to cover all the bases – iOS, Android, and Windows – in order to obtain maximum market share or to grant your mobile workforce flexibility in device choice. A straightforward way to accomplish that is to write all the app’s logic in Node JS and place it on the backend. The user interface then runs on the mobile device under another language.
Express JS is a prebuilt Node JS framework that can help you in creating server-side web applications faster and smarter. Simplicity, minimalism, flexibility, scalability are some of its characteristics and since it is made in Node JS itself, it inherited its performance as well.
In short, Express JS did for Node JS what Bootstrap did for HTML/CSS and responsive web design. It made coding in Node JS a piece of cake and gave programmers some additional features to extend their server-side coding. Express JS is hands down the most famous Node JS framework - so much so that when most people talk about Node JS they surely mean Node JS + Express JS.
Passport is an authentication middleware for Node JS. Extremely flexible and modular, Passport can be unobtrusively dropped in to any Express-based application. Passport recognizes that each application has unique authentication requirements. Authentication mechanisms, known as strategies, are packaged as individual modules. Applications can choose which strategies to employ, without creating unnecessary dependencies.
Socket.IO is an event-based bi-directional communication layer for realtime web applications. It abstracts many transports, including AJAX long-polling and WebSockets, into a single API. It allows developers to send and receive data without worrying about cross-browser compatibility. Socket.IO provides both server-side and client-side components with similar APIs.
- On the server-side, Socket.IO works by adding event listeners to an instance of
- The HTTP server will begin to serve the client library at
Since both the server and client's Socket object act as EventEmitters you can emit and listen for events in a bi-directional manner.