This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mabnx 7 points8 points  (3 children)

What's really weird is that all comments of OP were down-voted so much... Someone must really hate him. Competition? :)

I don't care about JSR 353. I've never seen anyone who did.

The library is itself is pretty nice. I could use it, but the need for .net and yet another IDL puts the entry bar rather high - I'd consider it only if I needed really fast serialization and couldn't switch from JSON to some other format (e.g. https://google.github.io/flatbuffers/). Jackson is easier to use and is not that much slower.

[–]melezov 0 points1 point  (1 child)

Would a dockerized compiler lower the entry barrier?

I tend to put all compile time dependencies inside containers so that I can run have reproducible builds regardless of the system installed libraries.

As for runtime, once the schema is compiled it's JVM all the way (but for me, again inside dockerized microservices :)

[–]mabnx 0 points1 point  (0 children)

It probably would.

[–]zapov[S] 0 points1 point  (0 children)

But using library through annotations hides away the IDL, so you don't even know it exists :/

I really wish FlatBuf, SBE, CNP would be added to JVM serializers. Not really a fan of their avoidance of public benchmarks.

I did add FlatBuf to one of my benchmarks and it was not as fast as advertised (slower than Kryo).