A modern programming language that makes developers happier.

kotlinlang

Hello, World! :wave:
The *<https://github.com/apollographql/apollo-kotlin-normalized-cache|new>*<https://github.com/apollographql/apollo-kotlin-normalized-cache| normalized cache> has reached <https://github.com/apollographql/apollo-kotlin-normalized-cache/releases|RC>! Now is a perfect time to try it and and report any issues/feedbacks/questions you may have! :blush:
• <https://apollographql.github.io/apollo-kotlin-normalized-cache/migration-guide.html|Migration guide>
• <https://apollographql.github.io/apollo-kotlin-normalized-cache/welcome.html|Documentation>

I was wondering - are there any performance improvements in the new one?

Yes indeed, especially around the SQL cache.

Awesome, we'll be trying it out in March I believe. Pardon the lazyweb here - I think it technically should be possible but I assume that you'd know best - is it possible to run both old one and new one side by side?

It is possible if you're going to have 2 different caches (so, probably, 2 different clients).

We'll most likely AB test the change - so a single client, but using one or the other

Oooh then yeah, this is possible. They use different package names so can cohabit in the same app. Note that the new SQL cache will delete the old cache data and schema from the database the first time it runs. So from that point, you can't go back to the old cache. Unless you use 2 different files (one for the old cache / one for the new cache).

Awesome - unfortunately we don't use SQL cache yet, just in-memory one, however we really would like to enable it but now that there is a new version you've just released, there is no point in doing so before upgrading. We just want to make a quick check that our in-memory one works fine after upgrade and then we will start implementing the SQL one :kodee-happy: