For e-commerce companies who have in-house call centers, investing in an enterprise grade interactive voice response (IVR) system doesn’t make much sense. Throwing thousands of dollars into a solution that swallows a huge chunk of the annual budget isn’t practical, especially if their customer base is just starting to build.
A couple years ago, the web was a stateless environment. Interactive features were treated as isolated units within a website, encapsulated within Flash or Java Applets. In 2009, NodeJS was released by Ryan Dahl aiming to create more interactive websites by establishing two-way connections. NodeJS enables asynchronous, event-driven input/output (I/O) making lightweight and efficient connections even in data-intensive applications.
The figure above shows the internal structure of Node.JS. Here, you see that only a single thread (i.e. file I/O, DNS, etc.) connects Node to the rest of an application. This single thread handles all incoming requests concurrently and can interface with one another. The architecture also allows the thread pool to interact with Node.JS’ low-level libraries to perform operations such as database transaction, file system access, etc. The asynchronous processing is done by libuv which enables Node to move without having to wait for the outcome of a current event.
Mono is a free, open source development platform based on the .NET Framework that enables the creation of cross-platform applications, improving overall programmer productivity. Its development is led by Xamarin, a Microsoft subsidiary which aims to not only run Microsoft.Net applications on different platforms, but also provides tools to Linux developers. Mono can run on Android, PlayStation 3, Wii, Xbox, OS X, Solaris, BSD, and most Linux distributions.
Almost everyone brings their devices to work – in fact 87 percent of us do, according to a recent study by Kaspersky. Bring your own device (BYOD) has gained momentum as businesses see its advantages, including increased employee satisfaction, productivity, and engagement, and a reduction in capital expenditures and overhead costs. In
Here’s a nightmare scenario: The night before you deploy your build to production, your colleague notices a bunch of libraries need to be updated and decides to update them, thinking it’s for the best. And then the unspeakable happens: your build breaks. You have to revert back the compatible version – search it, copy it, and test it again. You could have saved the app if not for the 20 libraries that you have to manually restore one by one. Someone has to inform the project manager that deployment has to be postponed. Unfortunately, that someone is you.