HTTP/2 is poised to eliminate much of the waste that developers deal with. Multiplexed connections will eliminate the need to bundle JavaScript libraries together. But is HTTP/2 a panacea to all our problems? What about WebSocket? Allan Denis tells us what HTTP/2 is good at and debunks some myths about what it can do.
Research and publish the best content.
Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
Already have an account: Login
JavaScript for Line of Business Applications
596.1K views |
+0 today
Keeping track of current JavaScript Frameworks that help design your clientside Business Logic Layers.
Curated by
Jan Hesse
 Your new post is loading...
Your new post is loading...
Scoop.it!
In this tutorial we are going to build a character voting app (inspired by Facemash) for EVE Online - a massively multiplayer online game. You will learn how to build a REST API with Node.js, save and retrieve data from MongoDB, track online visitors in real-time using Socket.IO, build a single-page app experience using React + Flux with server-side rendering and then finally deploy it to the cloud. 
Scoop.it!
There are a lot of new fancy web applications out there that are using real-time functionality. You can see examples of this used to great effect in Google Docs' multi-user editing, and the way all the social media sites update you of whats happening in real time. All of these applications are a far-cry from the old "request-response" pages of the early 90s, in fact the only way to achieve realtime web communication back then was to use Java Applets, and I believe you could use Flash for it too. Luckily I'm not 8 years old in 2015, and today we have Web Sockets that allow us to maintian persistent connections between client and server!
Scoop.it!
When doing real world web apps, there is a very common pattern: single source of truth shared by multiple clients. The best example of this is a chat: the message list, and the user list, must be readable and kept up to date for every connected client. Lets assume for a moment that all your clients are React apps executed in the same browser window. Then its easy: just use Flux! All clients will update their components every time the stores representing the message list and the user list is updated. Message posting will just be an action dispatch, as well as users joining or leaving a room. The problem is that all your clients are not in the same browser window. They actually are on different computers, on different hosts, and their only means of interacting with the server it through asynchronous communication (typically HTTP requests). This seems like a hard problem. Or is it?
Scoop.it!
Agenda * Introduction * WebSocket and Node.js *WebSocket using JSR 356 * Server * Client * Securing WebSocket * Embedded WebSocket * Load Balance WebSocket * Pub/Sub over WebSocket * STOMP over WebSocket * MQTT over WebSocket * REST and SSE * Scalability * Debugging * Production Tips
Scoop.it!
In this part, I will show you how to use your existing express-based node.js app to create a chatroom backend with WebSocket support. Now we have a chat system capable of broadcasting a message received via websockets to all other connected clients, it saves the message to the database and retrieves the last 10 messages to give context to every new user who joins the chatroom.
Scoop.it!
The Node.js cluster module is a common method of scaling servers, allowing for the use of all available CPU cores. However, what happens when you must scale to multiple servers or virtual machines? That is the problem we faced when scaling our newest HTML5 MMORPG. Rather than trying to cluster on a single machine, we wanted to get the benefit of a truly distributed system that can automatically failover and spread the load across multiple servers and even data-centers.
Scoop.it!
An introduction to WebSockets and why Primus might be a better fit for your project.
Jan Hesse's insight:
Scoop.it!
From
medium
One of our key products is a trading dashboard that handles hundreds of thousands of events from football matches and related betting markets. To consistently deliver value, we need to be able to handle this flurry of messages over a WebSocket connection and reliably keep the UI in sync. At its peak, on a typical Saturday afternoon, each WebSocket connection will receive upwards of 500 messages per second. Translating each of these messages into a UI update yields incredibly bad performance: the incumbent dashboard does just that, but as the business has scaled, we are hitting the limits of the current solution. So that we can continue to provide value to our users, we need to think about ways we can separate the concerns of receiving messages and updating the UI. Doing so has pushed us to evaluate our tech stack and rebuild portions of our dashboard from the ground up.
Scoop.it!
From
medium
A journey with ws, Socket.IO, Engine.IO, and Primus For a current project at WhoScored, I needed to learn JavaScript, Node.JS and WebSocket channel, after seven years of writing web applications with Java and Spring framework. We wanted an application that can send data to thousands of concurrent users, and Node.JS appeared to be the right way of doing it with its event-driven, non-blocking I/O model that can scale up easily. Compared Frameworks * einaros / ws Performance limits
Scoop.it!
I have been working in a prototype using the Twitter Streaming API with Socket.io and ReactJS for the frontend, Node.js in the backend, cool stuff! I used several articles as a reference, the one using the streaming API using socket.io(but AngularJS and ntwitter npm package), real-time django using node.js and socket.io or a modern python stack for a real time web application. In the end as I said I used nodejs, the twit package and socket.io in the backend. With all these tools was incredibly easy to have something running fast. And these are the different parts composing the example, the installation of the different tools is beyond the scope of this article just because I want to focus more in functionality and I don't want the article to be very long. Anyway if you have a question/criticism here I am. :-)
Jan Hesse's insight:
More ReactJS Intro: http://javaguirre.net/2014/02/09/reactjs-by-example/
Scoop.it!
In this blog post I’m going to show you how to build a VNC client using AngularJS and Yeoman. We should have a VNC server on the machine we want to control. This machine provides interface accessible through the RFB protocol. The proxy in the middle has RFB client, which knows how to talk to the RFB server. The proxy also provides HTTP server, which is responsible for serving static files to the client and also allows communication through socket.io. The last component in our diagram is the “AngularJS VNC client”, which consists few HTML and JavaScript files provided to the browser by the proxy. This is what actually the user of our VNC client sees. He or she use the form provided in the “AngularJS VNC client” in order to enter connection details and connect to the machine he or she wants to control
Scoop.it!
During the workshop I explained exactly how to take a single player HTML5 game and turn it into a multiplayer one using Node.js and WebSockets. Each player is identified using a unique client.id number. We'll use this later when communicating game updates to other players. For now the util.log line will output the client identification number to the terminal on connection. The client.on event listeners are used to detect when a player has either disconnected or sent a message to the server. Right now they point to handler functions that don't exist.
|
Scoop.it!
In 'Totally Tooling Tips' web developers Matt and Addy discuss the latest topics, issues and work arounds for building apps and libraries to help mop up your Totally Tooling Tears.
Scoop.it!
SocketCluster is an open source, multi-process realtime engine for Node.js. You can build entire applications on top of it or you can use it alongside existing systems written in other languages. SC supports both direct client-server communication (like Socket.io) and group communication via pub/sub channels. SC is designed to scale both vertically across multiple CPU cores and horizontally across multiple machines/instances (via pub/sub channel synchronization).
Scoop.it!
The virtual DOM is one of the key characteristics of React. When you render a component, React creates a lightweight description of the UI, diffs it with the previous version, and generates a minimal set of changes to apply to the DOM. That diffing algorithm is very fast, making React particularly well suited for apps with a lot of UI changes. That prompted me to revisit a type of application I’ve built in the past with different languages and frameworks: a trader desktop showing real time market data updates. This new version uses React for the client-side and Socket.io to push simulated market data updates to the client.
Scoop.it!
In this first tutorial, we'll learn how to build a Socket.IO library for AngularJS to help improve the responsiveness of your web application's user-interface. | Difficulty: Intermediate; Length: Medium; Tags: JavaScript, AngularJS, Web App, Web Development
Scoop.it!
Skipping collaborative apps, these days even a single user needs to sync his/her devices. The device landscape is getting predominantly mobile, so an average user has multiple powerful devices with unreliable internet connections. Popular solutions suck for one simple reason: common sense fails us in distributed systems. Proper sync needs some math like a GPS device needs some relativity formulas. Yes, that is just a box that says your x and y. No, it can’t work by common sense alone; it needs math.
Scoop.it!
In this blog post I’m going to share how could be build WebRTC chat with React.js. In the beginning of the blog post I mentioned that React.js application contains a finite amount of React.js components composed together. In this subsection I’ll illustrate, which are the different components of our application and how they are composed together.
Scoop.it!
In this article, Jeremy Likness shows how to connect to WebSockets using both message-based and real-time connections from Windows Store apps.
Scoop.it!
From
kwand
KWAND JavaScript Full Stack Web Development for the Next Generation of Web and Mobile Applications Uses Koa · WebSockets · Angular · Node · Dokku like this: Client:
Server:
Storage:
Develop:
Test:
Package:
Deploy:
Scoop.it!
I've been playing around with Vert.x for a couple of weeks and I'm really starting to like the simplicity of the framework. With very little configuration you can quickly get impressive results. In this article I'm diving a bit deeper in how to set up browser to browser communication using the Vert.x eventbus by using the javascript client side API. In short I'm going to show you the following things:
I'm going to skip the explanation on how to set up Vert.x. If you want more information on that look at this article where I explain the setup I've used in this example. So let's get started with the first step.
Scoop.it!
This is a step-by-step guide about how to expose live data from a C# console application to a web browser using WebSockets. The example has been implemented and tested on Windows7.
Scoop.it!
Given that the client didn't want to move his server for is current hosting provider, but was complaining all the time of how slow things were, I realised that I had to find a way to improve application responsiveness by having the data already stored locally when the user/UI actually needs it. Conceptually, I like the idea of having my cache resembling a database and and an ORM implementation. Having that I mind, my implementation would require the following components:
Scoop.it!
Front-end application frameworks have given developers the tools to build client side applications with rich user experiences. Let’s say your application is built with one of these frameworks and you want to notify connected clients that something on the server has changed – how can you do that while keeping a rich user experience? This is where Pusher and angular-pusher come into play. Using Pusher will allow us to subscribe to events triggered by other clients. First I’ll show you the simple changes needed in our ItemListController to use angular-pusher. Then I’ll show you an example of using Pusher in a Node.js server when an item is updated.
|
