Unix Domain Socket in 100 seconds
Vložit
- čas přidán 7. 06. 2024
- Do you run TCP for IPC on a single machine? Running out of TCP ports? You might want to try Unix Domain Socket instead. In this video We will see how to use unix domain socket with Node.js, and also pros and cons of Unix Domain Socket compared to TCP.
Related videos:
• You might not need HTTP
• Unix Socket HTTP in 10...
• Unix Named Pipe in 100...
Playlist:
• You might not need
#linux #javascript #100secondsofcode #webdevelopment #computerscience #networking #nodejs #programming #software - Věda a technologie
What is that thumbnail ? 😭😭
domain expansion
domain expansion: infinite knowledge
Domain Expansion: Infinite Compatibility
Open source domain expansion
Last thing you see before linus sticks his fingers up your bum
one of the thumbnails of all time
The domain expansion thumbnail is the only reason I clicked on this. And I'm glad I did.
the thumbnails got me click this video :)
領=域展開!!!
and the video has really good information.
This was so quick, straight to the point. Great video man.
man linux and calculus have some cool domains expansions
Love me jjk reference
Every time I see this thumbnail I click into this video. It is on par with the quality of the contents
Where was this video my whole life
It was uploaded just recently
That’s true, I’m definitely not 3 weeks old myself
You could read the docs
great thumbnail 😂 Also good video 👍
i ackchyually like and suscribe for the quality/length of this video.
thumbnail is absolutely goated LOL, also great video dude! subbed
You can also send file descriptors over domain sockets.
I had no idea this existed, perfect for my next project though.
glad I found this channel, entertaining content :)
I had to like just for the thumbnail
Socket files can run entirely in memory! Crazy
`> find / -type s ` is super helpful
10/10 thumbnail
Yes, it supported under Windows, but only as a wrapper around named pipes. For most software this slight overhead is unnoticeable, but if you need to squeeze every last drop of performance, you'd might want to use named pipes directly. But than again, if this communication is the bottleneck of your application, you already have most likely already made some bad design decisions earlier. Usually IPC is used to communicate from a user-space front-end utility to a background service/daemon process, but in some cases it also used for communication between forked processes...
awesome vid man!
Ryoiki Tenkai Malevolent Sockets!!
I came here to watch ultimate lobotomy kaisen edit, but this is also good.
exquisito video man .
Good content, keep it up!
Nice content, keep bringing it, please!
Bruh I've been searching for this for a week now
nice vid. Subbed
I keep watching this even though I’ve already known what a UDS is. For the thumbnail.
Great video! Btw what do you use for the slides?
Unix Domain Socket expansion!
This feels like a better and user-friendly way to communicate with busy threads. And hide load spikes from hawkish admins. 😏
With the classic approach of synchronous IO (blocking read/write) and one thread per connection, there's generally no difference between local TCP/IP and Unix domain sockets - the stack memory and scheduler overhead for so many threads stays the limiting factor. Also in theory, TCP runs out of port numbers after one listening socket and 65,534 connections; with Unix domain sockets, the connecting side often gets an anonymous socket address, of which there can be arbitrarily many.
Not the domain expansion 😭 it's perfect
What if I provision a TLS through PKI or a local root CA ? Then can the traffic be routed through port 443 ?
What do you use to make your videos?
It isn't infinite socket file, that number is the number of limits defined to the kernel usually below 32k and can be restricted by ulimits for users.
Why have I never heard of it and why would anyone still use tcp with the loopback address? Where's the catch?
TCP on the loopback adapter is most useful with programs that can work both locally and over the network, or if you interface with a program that's only designed around network connections. For example, the game Minecraft has used a server-client architecture for a long time; if you enter a singleplayer world, it starts a game server (which you can open up to your local network at any point) and connects to it on localhost. That said, many Java programs still use loopback for IPC because Unix domain sockets were only added to the standard libary in Java 16 after they were universally supported.
Anyone have a comparison of the throughput difference between domain and TCP sockets, when both processes are running on the same machine?
Linus Domain expansion : sudo rm -Rf. Not even Sukuna can counter this.🤣
Can I ask what tools did you use for the illustration
gruvbox dark was mentioned further below.
Which colorscheme is this?
gruvbox dark
This is how to do "pipe" instead of loading the entire network stack for localhost, do any other applications that nginx really need to load network stack? I have about 200 UDS behind the same endpoints in nginx. It's a monolithic solution deployed separately for each route, hence each route can be down or be replaced without the rest of the solution having to be down. Further I can pick and choose which dev environment each route uses: R, Python, Swift, and / or Rust as pr my knowledge.
Thank you for the idea. Thinking about R how do you deal with blocking? Let's say that my R model takes 1 min to answer.
@@quantinvest7968 Always for front loading, so it's not a web facing interface as such; the route will respond with a job number and timestamp only, however its result[s] will be indexed after the fact, and / or put in PostgreSQL.
Linus Torvalds: if Windows implements more improved kernel versions in the future it may give me some problems...
...Nah I'd Win
Linus Torvalds domain expansion is Linux.
Is it used in real life? PHP-FPM makes heavy use of Unix Domain Sockets. Most databases use them as well. If you’re running a website on a single system I am pretty sure Unix Domain Sockets are involved somewhere.
views mostly because of thumbnail.. clickbait skill unlocked
MySQL also use Domain sockets
gud
1:30 Not to mention postgresql
But would you lose?
Nah I'd win
In Windows, it's not available to non-insiders.
1:36 One Piece ftw
insane thumbnain lmaoi
why is it just plain black?
I think it's valuable going over the rest of the list and some further reasons why you would want this over another. It seems half done, really.
Why the GenZ call-out?
Unix Domain Expansion . 😂😂😂😂
This isn't C...
I was liking this video until you said the example in JS...
guys can anyone tell me how can i learn all this, i'm getting into IT so new to this stuffs i just know frontend backend and networking stuff but this whole ssh, tcp IPC, unix domain is over my head
Windows is primarily a realm that likes the MVC paradigm. Linux is more the reversal or mirroring of that framework. ETL mechanisms that pull messy marked up structures back into raw data ( serializables). All for reloading back into yet another MVC (ie databases, browsers, and tcp-based client-servers (ie Apache/IIS)).
@@wanderingfido i appreciate your comment man, now i will read in depth of these things you told, thank you.
We don't do ETL in Windows servers because the data sets tend to be huge. And Microsoft has more memory leaks.
Microsoft == Boeing== Ford
versus
Linux == AirBus == BMW
I just had an epiphany after that domestic versus foreign product quality comparison. Domestic systems really suck. Wow. I didn't fully realize until I lined a few up together. We here in the West need to pull our heads back out of our own butts. And go take a long soul-searching shower. And then go watch more telly. Cuz. What else can we really do now? It's already over.
If you're a beginner web developer, this is the foundation on which the web is built. It's good to get familiar with networking. When you said you "know" it, I don't know if that means you know of its existence, or if you're experienced and this is a prank. Sorry for the autism.
ssh means secure shell. It lets you use the terminal on another machine.
TCP/IP means Transmission Control Protocol/Internet Protocol. It defines the technology which makes packets reach their destination.
Unix domain sockets are something I just learned about watching this video. They're an alternative to using TCP/IP to send information between processes on the same machine, if I understand correctly. It seems better because you don't run out of ports.