We rewrote JSONata with AI in a day, saved $500k/year
1–10 of 278 posts
Re: We rewrote JSONata with AI in a day, saved $500k/year
#2For context, JSONata's reference implementation is 5.5k lines of javascript.
Re: We rewrote JSONata with AI in a day, saved $500k/year
#3> This was costing us ~$300K/year in compute, and the number kept growing as more customers and detection rules were added.
Maybe I’m out of touch, but I cannot fathom this level of cost for custom lambda functions operating on JSON objects.
Re: We rewrote JSONata with AI in a day, saved $500k/year
#4[deleted]
Re: We rewrote JSONata with AI in a day, saved $500k/year
#5The docs indicate there are already 2 other go implementations. Why not just use one of those?
https://docs.jsonata.org/overview.html
Re: We rewrote JSONata with AI in a day, saved $500k/year
#6Next maybe they will use a binary format instead of JSON.
Re: We rewrote JSONata with AI in a day, saved $500k/year
#7As long as you are using JSON, you will be able to optimize.
Did you know that you can pass numbers up to 2 billion in 4 constant bytes instead of as a string of 20 average dynamic bytes? Also, fun fact, you can cut your packets in half by not repeating the names of your variables in every packet, you can instead use a positional system where cardinality represents the type of the variable.
And you can do all of this with pre AI technology!
Neat trick huh?
Re: We rewrote JSONata with AI in a day, saved $500k/year
#8> This was costing us ~$300K/year in compute, and the number kept growing as more customers and detection rules were added. Maybe I’m out of touch, but I cannot fathom this level of cost for custom lambda functions operating on JSON objects.
It has to be satire right? Like, you aren't out of touch on this. I get engineers maybe making the argument that $300k / year on cloud is the same as 1.5 devops engineers managing in-house solutions, but for just json parsing????
Re: We rewrote JSONata with AI in a day, saved $500k/year
#9> The reference implementation is JavaScript, whereas our pipeline is in Go. So for years we’ve been running a fleet of jsonata-js pods on Kubernetes - Node.js processes that our Go services call over RPC.
> This was costing us ~$300K/year in compute
Wooof. As soon as that kind of spend hit my radar for this sort of service I would have given my most autistic and senior engineer a private office and the sole task of eliminating this from the stack.
At any point did anyone step back and ask if jsonata was the right tool in the first place? I cannot make any judgements here without seeing real world examples of the rules themselves and the ways that they are leveraged. Is this policy language intentionally JSON for portability with other systems, or for editing by end users?
Re: We rewrote JSONata with AI in a day, saved $500k/year
#10> This was costing us ~$300K/year in compute, and the number kept growing as more customers and detection rules were added. Maybe I’m out of touch, but I cannot fathom this level of cost for custom lambda functions operating on JSON objects.
It has to be satire right? Like, you aren't out of touch on this. I get engineers maybe making the argument that $300k / year on cloud is the same as 1.5 devops engineers managing in-house solutions, but for just json parsing????
I wonder if you've ever worked on a web service at scale. JSON serialization and deserialization is notoriously expensive.