-
Updated
Nov 27, 2020 - Java
in-memory-database
Here are 116 public repositories matching this topic...
-
Updated
Nov 28, 2020 - C++
-
Updated
Aug 8, 2020 - C#
We don't want to build releases on any tags, just for releases
-
Updated
Sep 26, 2020 - TypeScript
-
Updated
Oct 18, 2019 - C++
-
Updated
Nov 27, 2020 - JavaScript
-
Updated
May 15, 2017
-
Updated
Nov 26, 2020 - JavaScript
-
Updated
Nov 2, 2019 - Pony
-
Updated
Apr 19, 2020 - Clojure
-
Updated
Oct 4, 2019 - Dockerfile
-
Updated
Feb 2, 2020 - TSQL
-
Updated
Aug 21, 2018 - JavaScript
-
Updated
Oct 1, 2018 - Java
-
Updated
Nov 20, 2018 - JavaScript
-
Updated
Nov 25, 2018 - Erlang
-
Updated
Mar 4, 2020 - Java
-
Updated
Nov 29, 2020 - JavaScript
-
Updated
Nov 23, 2020 - C#
-
Updated
Sep 24, 2020 - Clojure
-
Updated
Feb 28, 2019 - Java
-
Updated
May 1, 2018 - C#
-
Updated
Mar 1, 2019 - Go
-
Updated
May 2, 2017
-
Updated
Sep 9, 2017 - C#
-
Updated
Feb 25, 2020 - Java
-
Updated
Dec 30, 2017 - Kotlin
Improve this page
Add a description, image, and links to the in-memory-database topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the in-memory-database topic, visit your repo's landing page and select "manage topics."
Now that we support more than 1 data type, we should include the values data type in cache nodes. This give us a way of easily identifying what type of data a key points to e.g. string, queue (and more types in the future)
Currently a cache node object consists of a
Key, aValueand aTTL. We should also add a field specifying the type of theValue