News for hackers. Stuff that matters.

A comment on Give Me Back My Monolith. Parent comment

Re:Give Me Back My Monolith by Rapzid on Wednesday March 13, 2019 @09:03PM (#19385600)
JSON parsing IS expensive. Way more expensive than many people realize. There is actually an almost-underground JSON parser SCENE in the .Net ecosystem where people develop new parser and try to squeeze the maximum performance using all sorts of tricks: https://github.com/neuecc/Utf8Json . Here there is discussion of needing JSON support in .Net core that's faster than Json.Net: https://github.com/dotnet/announcements/issues/90 .

And people say web applications are never CPU bound :)

[ Parent | on HN ]
Re:Give Me Back My Monolith by NicoJuicy on Wednesday March 13, 2019 @09:07PM (#19385623)
gRCP is a little bit faster, Google created protobuff which should be easier to migrate to than gRPC, but the protocol is unreadable ( binary)...

JSON has its advantages, I prefer a feature flag when I need performance ( protobuff vs Json), http headers do the rest

[ Parent | on HN ]
Re:Give Me Back My Monolith by stouset on Thursday March 14, 2019 @02:44AM (#19386974)
gRPC is built on top of protobuf. It’s literally just RPC with protobufs.
[ Parent | on HN ]
Re:Give Me Back My Monolith by tekknik on Wednesday March 13, 2019 @10:35PM (#19386077)
one could argue that if serialization/deserialization is the majority of what your api is spending time on then you’ve got distributed monoliths and shouldn’t be making the call in the first place. also ensuring you have the fastest json parser before having a real problem is premature optimization
[ Parent | on HN ]
Re:Give Me Back My Monolith by 0815test on Wednesday March 13, 2019 @09:24PM (#19385722)
> JSON parsing IS expensive

Well, maybe

https://news.ycombinator.com/item?id=19214387

[ Parent | on HN ]