Building A P2P Network With Deno 🌐

JavaScript Framework Developer Tools Web Frameworks

Socket.io Landing Page
1

Socket.io

Realtime application framework (Node.JS server)
Pricing:
- Open Source
Naturally, I immediately sought to develop this kind of system in... JavaScript! That's indeed possible, thanks to the WebSocket protocol. In this post, I propose to build, step by step, a (decentralized) P2P network based, not on ExpressJS x SocketIO, nor NestJS (to speed up the project), but directly from Deno 🦕.

#Developer Tools #App Development #Mobile Push Messaging 716 social mentions
Nest.js Landing Page
2

Nest.js

A progressive Node.js framework for building efficient, reliable and scalable server-side applications.
Pricing:
- Open Source
Naturally, I immediately sought to develop this kind of system in... JavaScript! That's indeed possible, thanks to the WebSocket protocol. In this post, I propose to build, step by step, a (decentralized) P2P network based, not on ExpressJS x SocketIO, nor NestJS (to speed up the project), but directly from Deno 🦕.

#Web Frameworks #Developer Tools #JavaScript Framework 182 social mentions
ExpressJS Landing Page
3

ExpressJS

Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
Pricing:
- Open Source
Naturally, I immediately sought to develop this kind of system in... JavaScript! That's indeed possible, thanks to the WebSocket protocol. In this post, I propose to build, step by step, a (decentralized) P2P network based, not on ExpressJS x SocketIO, nor NestJS (to speed up the project), but directly from Deno 🦕.

#JavaScript Framework #Node.js Framework #Web Frameworks 423 social mentions
Deno Landing Page
4

Deno

A secure runtime for JavaScript and TypeScript built with V8, Rust, and Tokio.
Pricing:
- Open Source
#Typescript #JavaScript #Web Development Tools 195 social mentions
cURL Landing Page
5

cURL

cURL is a computer software project providing a library and command-line tool for transferring data...
Pricing:
- Open Source
Here is the second API to create a new WebSocket client. Explicitly, the user will need to provide the client node's target URL via a REST protocol POST call. When the client is opened (onopen), it is added to the peer list of the current server; on the other hand, when the client is closed (onclose), this same client is removed from the list. Finally, the API returns a simple message with a status 201 (CREATED), or an HTTP 400 code (BAD REQUEST) if the URL value isn't present in the body of the call. Since this is a POST request, it is necessary to use a REST client: cURL, Postman, etc...; to query the API.

#API Tools #APIs #Developer Tools 105 social mentions