Is JSON Blazingly Fast or...?

Is Json really that slow? Can the most popular interchange format really be that bad?
Twitch
Everything is built live on twitch
Twitch : bit.ly/3xhFO3E
Discord: discord.gg/ThePrimeagen
Spotify DevHour: open.spotify.com/show/4MLaDrQ...
Editor
All my videos are edited by Flip. Give him a follow! / flipmediaprod He is also open to do more editing, so slide deeeeeeeeep into his dms.
Join this channel to get access to perks:
/ @theprimeagen
Links
Linode: linode.com/prime
/ discord
Twitch: / theprimeagen
Insta: / theprimeagen
Twitter: / theprimeagen
VimRC & i3: github.com/ThePrimeagen/.dotf...
Keyboard 15% off bit.ly/Prime360 USE CODE PRIME360
#vim #programming #softwareengineering

[@ginowadakekalam]

JSON is like the python of language, slow but convenient to use

[@ThePrimeagen]

I think this is the perfect description

[@worstfellow]

We want to know more about JSON alternatives

[@tattipodapatti]

@@worstfellow Yes, but definitely not XML

[@nature-.]

@@tattipodapatti yes even non programmers can understand JSON easily, government of india is using it in websites like income tax for the users to download as json

[@guruji-.]

@@codyking9491 yes already we have too many javascript frameworks don’t want too many data formats 😅

[@CemKavuklu]

These videos are getting better and better both in quality and entertainment factor :)

[@ThePrimeagen]

That's what I like to hear

[@vaisakhkm783]

@@ThePrimeagen to bad you cannot 'hear' that... unless you made a speech to text app in RuSt... :) edit: text to speech

[@oliverchalkley1187]

@@vaisakhkm783 if he had then it would have been blazingly fast

[@MrMw1979]

Great video. Thanks for introducing me to Deku. I think there is a lot of information left out here. I'm gonna outline my opinions below even if they don't matter: 1. JSON is not for computers it's for humans. Trouble shooting binary requests isn't easy. 2. GZIP compression can greatly reduce the bytes over the wire. JSON with lots of repeating keys can greatly benefit from gzip. 3. A lot of the time the database is your actual bottleneck and serialization doesn't matter for performance. In fact, 1,600 requests per second is more than most companies/services will ever see. 4. Having the document define the schema allows for flexible data. You can't just send arbitrary data with a binary protocol. This has pros/cons. For a public facing web service that only receives a couple thousand requests per second I would pick JSON over any other structured binary protocol almost every time. Yes there is a cost to simplicity but there is also a cost to complexity. Make it easy for internal (engineers) and external (users) to troubleshoot. Just use JSON unless you have identified that serialization is the bottleneck in your endpoint.... For most endpoints/services, I would wager serialization is not the bottleneck.

[@vaisakhkm783]

things like scientific applications involving high density of data collected in small amount of time(rocket controls, explotions tests..), and things that are inherintly binary(vnc), JSON is not a good choice anything involving man, it's good to use JSON

[@evasiveutopian]

to your 3rd point. It was even greater 1,600 requests per milliseconds ~ which would be 1,600,000 requests per second

[@alkolaqi83]

on point

[@odnoletkov]

Comments like this keep my hope in the humanity

[@thekwoka4707]

Why gzip when we can Brotli?

[@scottiedoesno]

BLAZINGLY SLOW. Thanks for another great technical video! I hadn't actually thought about it until now, but this explains perfectly why we use protobuf so much in embedded work

[@ThePrimeagen]

Absolutely. By the way, I haven't responded to your discord message. I'm on a flight to meet my boss right now, and then I'll be able to update you

[@scottiedoesno]

@@ThePrimeagen Thanks a ton. Have a safe flight and hope the meeting goes well

[@skyamaz5913]

@@ThePrimeagen you have a boss? thought ur the boss

[@dickheadrecs]

blazingly slow is the new blazingly fast

[@DaddyFrosty]

@@dickheadrecs I just heard that sentence with Fireships voice thanks for making my day

[@VanDelao]

It would be nice to see a video comparing sending JSON/XML/Apache Avro/Protobuf over the wire with Rust/Go/JS. Great video, as always;

[@ebrelus7687]

Absolutely must happen

[@es68951]

For sure. I am also curious why “deku” instead of using exactly Avro or Protobuf. This approach doesn’t seem to take into account forward/backward compatibility, unless I missed something?

[@ThePrimeagen]

Hey, did you like the video? I really enjoy making this kind of content. That's fun. Do you think I should do something with promises? (MAKE A COMMENT, Do not respond, KZbin has the worst notifications)

[@codewithguillaume]

I think you should learn french

[@filipebraganca2558]

It kinda landed right at the best moment, as I'm trying to improve the performance of our microservices where are transferring millions of JSON messages and can see the real cost of JSON serialize/deserialization growing super fast. I was studying GRPC and just learned about this protobuf here, thanks again for sharing this kind of content!!!

[@asdqwe4427]

GRPC is wonderful. And reading the proto files is so much better than working with swagger

[@Ether_Void]

There is actually a successor to GRPC & Protobuf called Cap’n Proto. Afaik it's made by the same person but they are no longer working for Google. It's faster because Cap'n Protos RPC can "travel back in time" (send a rpc using the output of a another call before the call has even finished) and it does direct in-memory modification rather than adding extra encoding & decoding steps. You of course keep the benefit of having a separate protocol definition that can be used across multiple languages.

[@ko-Daegu]

@@Ether_Void “before call is even finished” sounds cool but also scary this rings so many alarms in my head as a security analyst

[@dealloc]

Binary formats are difficult to maintain and scale at certain points, as ThePrimeagen notes, it's also not easy to version; you'll have to change your parser to read data correctly, or know where to take up unused space to give room for future improvements without breaking the protocol. But it's really good for real-time systems that need to deliver a lot of data in a small amount of time. For example game servers where feedback should be fast and responsive both on the client and across other clients with different network conditions at 60fps, while also dealing with other systems like rendering.

[@ko-Daegu]

Protobuf then?

[@alexgochenour8740]

I can't stop loving this content. JSON is something I use daily but never really think about. A deeper than usual deep dive, yet still accessible. Thank you my good man

[@ThePrimeagen]

ty ty ty

[@MantasJurkuvenas]

As an embedded C engineer i love efficient code. I think JavaScript is the evidence of the decline of our civilization.

[@ThePrimeagen]

Facts

[@andersoncunha7079]

looking at the comments: seems most people consume messages without checking what they are ingesting (some even say that is the safe way), never heard of network endianness, didn't realize a few bits in the beginning of the frame can specify version, size and any other desirable property, don't know what rpc is, think computers should communicate in human, and the list goes on... so I think you are right.

[@virtuosisimo]

I'm with you man, I have an embedded arm Linux mature project I recently spend some time optimizing code that the GCC profiler marked as high usage. There is some json in the project, this video makes me want to rethink it, so the device runs more cool, other people don't this beneficial, but I don't see the benefit of heating the atmosphere

[@Dayun123]

Absolutely loving these performance deep dives! Keep ‘em comin!

[@camillenovak8359]

These types of videos are super valuable and I really appreciate the way you go into the technicalities and explain these topics. Loving the format!

[@BlueeyesChineseguy]

For the algo

[@ThePrimeagen]

For the thankfulness

[@drborisyum9977]

Love this form of content Prime! 👍 You make harder concepts (for me anyway) as digestible as possible! So invaluable.

[@kortes8914]

Your production quality has gone up and the humor is on point. Today I decided to subscribe! I can officially say that I like this channel now :) great content my dude!

[@GeekMasher]

Amazing video as always, please keep them up!

[@js-ny2ru]

Recently I was comparing Deno and Rust. What surprised me was how much simple JSON response weigh...

[@ThePrimeagen]

People just don't realize how expensive simplicity is

[@enclave2k1]

@@ThePrimeagen I'm a simple man; consequently, an expensive one as well.

[@notsojharedtroll23]

@@enclave2k1 xd

[@paulgupta2454]

been watching a lot of your videos, I feel like your newer 'hot take' videos on blogs are fine and all, but you're a good teacher and I'd like to see more of these more informative/objective vids from you because you're a pretty good teacher when you do this sort of content!

[@headlights-go-up]

Really enjoyed this. It just seems like, for better or for worse, the ease and convenience of JSON trumps everything else.

[@localboxcrox]

i love that akame wallpaper behind your transparent terminal with nvim open. nice touch.

[@arkayv]

I think JSONs fall into the same pitfalls as document storage DBs. They are so easy to understand and implement, yet so goddamn hard to let go off even after you learn about better and BLAZINGLY FAST-er alternatives (like good ol' postgres or protobufs in this case). This requires a change in mentality more than anything. I suppose old habits die hard.

[@ThePrimeagen]

Exactly. Simplicity is amazing. I cannot stress that enough. But it also costs a lot.

[@diegolikescode]

Prime, these videos make us all better programmers. Thank you so much, I have been so much healthier programming and having fun doing it just because of your content, and that makes me a much better programmer

[@ThePrimeagen]

Love to hear that giga Chad

[@OcarinaOfVali]

holy gigachad comment

[@calder-ty]

Love these style videos. Keep it up!

[@ThePrimeagen]

Thank you. I feel like it's a fun break from the VIM content

[@tibixdev]

This was a really cool deep-dive, but also very entertaining and straight to the point. Looking forward to more stuff like this. :)

[@ThePrimeagen]

I think I could have done a better job and got a bit slower on binary representation. But, it's such a hard balance to not be long-winded, but be entertaining. So thank you for the note!

[@thehibbi]

Very informative and comedic video, thanks :) Keep up the good work TheScienceagen

[@Omikronik]

I interned at an insurance company where the way they received new insurance data was through a single string that was about 5000 characters long and parsed it by slicing that string at intervals and it almost always caused issues with encoding because it used ascii encoding and all the responses were in utf-8 so it had a billion safeguards that would always break when someone entered a non ascii character. I'd say it doesnt get more blazingly fast than this but its written in the most cursed and blazingly slow C# code ive ever seen in my limited experience. Best part is they moved to c# from java like 7 years ago but just kept this system instead of rewriting it to use xml or "jizzle"

[@sunnyheheheh9401]

Your jokes in this type of developer/programming videos is funny and unique and I would love to see more of em keep up the good work.

[@mariumbegum7325]

Great video, some interesting points mentioned here. Looking forward to seeing more

[@laupetre]

I really enjoy these comparison videos, especially with your humor.

[@alexandrosvangelatos9979]

Love your videos dude! What's with the dancing squirrel 💃🐿️? 🤣🤣🤣 Good one!

[@wety789]

I love this style of video! The live stuff is neat as well but I find these are much easier to focus on

[@muhamedkarajic]

Exactly what I was looking for. Thank you!

[@asdqwe4427]

Very cool video 😎 Would be interesting to see jsons position challenged. I wonder how gRPC would compare, as I have never used it in the browser. But, before we hate on JSON, let’s remember that it freed us from XML

[@TesterAnimal1]

It didn’t really. All these horrible front end “frameworks” go through linguistic and development hoops to preserve XML. UIs are defined in some bastard munged XML+JS format that can’t be merged. UIs can be described in JSON. But a bunch of HTML authors from 1994 still want to do

[@ABaumstumpf]

Yeah, it "freed" us from a more structured approach that also supports comments and validation....

[@lydianlights]

@@ABaumstumpf you dont need to send comments over API requests, lol. XML is fine for a lot of cases if you like it, but it makes no sense to use it for network traffic.

[@ABaumstumpf]

@@lydianlights "you dont need to send comments over API requests" Who said anything about API request?? "but it makes no sense to use it for network traffic." Then that applies exactly the same to Json.

[@lydianlights]

@@ABaumstumpf ...the whole video was about network traffic... ...thats what the original comment was about...

[@vedrankaracic265]

Love these videos! Keep 'em coming!

[@ThePrimeagen]

Trying!

[@playea123]

This is awesome! More of these deep dives please!!

[@nikensss]

Loved it, thanks for this type of videos

[@gayedemiray]

insanely high quality video. thank you for all the information!

[@zeachco]

I just love your content, it's smart, useful, in dept and quite entertaining!

[@stryhx]

damn! that sub request was really well placed and timed! nice one!

[@victorvirgiliocalderonsoto8689]

I loved this video! Thank you Primeagen

[@suic86]

This was great. I can't wait for more videos like this.

[@MrBaudin]

Great video, please do more subjects in depth. These nuggets of knowledge help us all! Thank you.

[@Guilherme-qk9so]

your technical videos are so good!

[@0e0]

I really love this sort of content from you

[@drilkus1312]

Crazy timing. My frontend team at work is frequently wondering why we're not doing JSON payload, so i can send this! Super informative, thanks!

[@ThePrimeagen]

hah! well if your backend is dictating it, they are smert

[@waylag9144]

I'm loving the new editing style. not too much but just the right amount of sass

[@st-jn2gk]

W video, more more more. Too many videos out there aimed at beginners, very few aimed at intermediates (other than theo and fireship). Love the content. Love the streams. Good job dad.

[@7xr1e20ln8]

Dude this guy is on another level. Love your videos.

[@adam8685]

Love this type of video, I wasn't aware of Deku before watching. I'd be keen to see a breakdown of Protobuf vs Deku We used Twitch's Twirp framework for Golang at a previous company I worked at for exactly this reason

[@mdfalexis]

This is an algorithmic message to let you know that this type of content is really really appreciated !

[@ahmedeatsplanets]

This is one of the best videos on programming I've ever seen. I feel enlightened and empowered

[@WilliamCulver]

I don't know how I got here guy, but I'm absolutely glad to be here - some slick vim keystrokes, nice editing and explanations. Keep it coming good sir.

[@erikuusitalo]

Awesome stuff. Keep making videos like these.

[@pemedeiros]

For more information on that topic I recommend chapter 4 of Designing Data-Intensive Applications. Really good video :D

[@digicyc]

I absolutely vote for more videos like this, but maybe some more involvement in the creation of the code. Loving it! SO much JSML o_O

[@HYPERLOG]

0:08 made me laugh way too hard, thank you Mr. Prime

[@blackfrog1534]

yah yahh, prime is on a roll! This is the best tech content on the internet if you ask me. Would be delighted if you pumped up even more of these. Plus the streams were you write the code for these experiments are so much fun :)

[@christophergruendell8089]

The lab coat and theme when you went all sciency gave me serious Garand Thumb vibes. I love it. You guys even kind of look like each other.

[@TownspersonB]

This was very interesting and something I hadn't really given second thought to when I'd use JSON

[@aus10d]

this was really beneficial and interesting. thanks for posting it. i learned a lot

[@echobucket]

As someone who tried writing this kind of stuff back before JSON and even before XML, the reason we went with this stuff was for debugging purposes. At the time it was so nice to just watch the stuff on the wire, and be able to have it be human readable. However, I would argue this was mostly because there was not a de-facto binary protocol well understood by common tooling. I think it's entirely possible for us to have a nice binary encoding that our tooling (things like wireshark, Charles proxy, Chrome dev tools) could read and understand without it being fat and bloated like JSON.

[@user-px4pk2wd4s]

This

[@billeterk]

Insert obligatory xkcd standards cartoon here ;-)

[@phoenix-tt]

I guess it would be really beneficial for the adoption of protobufs as well, if you could just upload a .proto to devtools and see all the underlying data

[@camenraidercc6625]

Hi Man! So it's been a couple of weeks since you started to appear in my recomendations, for some reason KZbin is suggesting me all your VIM videos, now i don't give a damn about VIM and i didn't found the thumbnail any interesting so i decided to ignore it, but today it suggested me this one....so i watched it.....and now i've watched almost all of your videos :D This is very good and entertaining content, keep up the good work ( i'm still not gonna watch the VIM videos btw )

[@YatesyTea]

Thank you for this one, was really informative to me. Can't believe I wasn't taught this in University 😂

[@Sakrosankt-Bierstube]

The deserialization from json from the requests and the database to serialization to the response are actually in the top 5 of our bottlenecks in the company i work in. 40ms of a 100ms request are just for de-/serialization from/to json.

[@ThePrimeagen]

That is incredible. And if you're using a garbage collected language, don't forget the effects of garbage collection.

[@Sakrosankt-Bierstube]

@@ThePrimeagen Well, we use Java so... yeah.. xD

[@fabianschwarzfritz]

I like this format! Could be even a bit deeper / more technical and longer :). Anyway, super cool format!

[@tobiasweyer5063]

This kind of videos are just pure gold and a lot of educational content is in. Thanks for the education and entertainment at the same time. :)

[@lastink444]

MY GOD, this was so satisfying to watch and listen to

[@HaydonRyan]

This was great - we need more people to think about how efficient programs that run at scale are, as well as how efficient the data we send through the net. There is this horrible trend of as chips and network transmission gets faster to just send things using the least efficient method. I totally agree with your point though on being able to inspect the payload is helpful for debugging what's going on though.

[@JanKammerath]

Anyone else currently looking at a JSON parser and your head constantly screaming "Jéson!"?

[@adrianospiotos364]

More deep dives! These are excellent 🚀

[@rafaelgil6895]

I'm, just using "edn" (extensible data notation) by default since it's not only "blazingly" but also "extensibly" fast :D Amazing video btw, like always!

[@ThePrimeagen]

Tytyty

[@nanthony007]

Great stuff! I’m curious about differences with a simpler encoder like message pack which the Serde docs say is similar to json but binary encoded…

[@teej_dv]

message pack is what nvim uses :)

[@pif5023]

Yes!!! Gold content!!! I have never heard any other dev talking about serialization encodings!!!!

[@sammysheep]

Excellent work, Dr. Prime!

[@guidoambrosino693]

I really liked the video. Keep it up Prime

[@aryklein]

Awesome video. Keep doing that!

[@adelarsq]

I don't even work with Rust and NodeJS, but it's pretty fun your videos. Keep going!

[@robinbauhn8685]

Would be interesting to see comparison between deku and MsgPack since it sits somewhere in between binary and json

[@AlphaWatt]

Love this kinda content Prime

[@bsqrd]

I would like to take a moment and say the videos you put out are excellent, both in educational and entertainment value. Very much appreciated! ✨BLAZINGLY AWESOME ✨

[@itjustworks4824]

Keep them coming !!! Lets make blazingly synonym for ThePrimeagen

[@pauloffborba]

Yeah, the technical videos are great! ❤️

[@marcelfahle]

Love this.. I'm messing with binary protocols in erlang right now, for some multiplayer shenanigans.. very cool!

[@yxtqwf]

I think another benefit of JSON (though it may not be as relevant in this example as in, say, a web application) over any binary format is that it is immediately readable to any user. I can't count the number of scripts or alternative clients I've been able to write just by inspecting the JSON data a website sends. A universal, plain-text format like JSON frees the potential of how software is used from just the developer and places some choice in the hands of the user as well. Another thing, I've found that I really like the TSV (tab-separated values) format for storing any tabular data. It's so simple, effortless to parse, and much more compact compared to JSON or even CSV (the schema is usually just the first line, or can even be omitted). I'm not sure how it would work as a data transfer format, and though I don't see it commonly used, I doubt there would be any significant problems.

[@mosslightstudio]

love it when the scienceagen comes in to do some blazingly fast research for us all

[@anthonyh618]

Really loving this, Prime.

[@ethanwilkes4678]

This one was a BANGER. Nice job prime

[@SzTz100]

This was a great video, thank you.

[@focusEngineered]

I loved this idea, And this is the first time I see how slow is JSON, I never thought about it before Thanks for the great ideas and videos, Please keep up the good work I love watching your videos, it is useful, funny and interesting to me

[@MohitDodhia]

had to pause at the intro just to mention how smooth that subscriber plug was. ggwp edit: what a great video

[@bharathgajjala3437]

Love these kinda videos

[@franswaweingartz2162]

Thank you this was very usefull :)

[@ximon-x]

I love this man's videos SOOOOOO much. 😅

[@amrsaber5457]

I really love those performance test videos

[@TheyCallMeIce]

Deku looks interesting, but it also looks like it was made for transferring objects of a known structure, and mainly size. Like, what if an object contains an array of an unknown size? Or even simpler, how do you transfer strings?

[@quintondeanmusic]

Great video. Super interesting to see! The “XML is worse” part got me in kidneys. I have to work with shitty XML everyday as a messaging schema between our app and other companies integrations (LEGACYYY). Slow and terrible to work with. The worst of both worlds.

[@seyofori]

Loved this!😂

[@dandreani]

having just seen Mark Robber's last Olympiad for squirrels. I can appreciate the squirrel for science...

[@ThePrimeagen]

Science squirrels are incredibly important

[@evancornish656]

I loved this, very fun.

[@KroshkaMu]

I want an update of this video, this time featuring JDSL and Tom the genuous