Open Source alternative to Algolia and an Easier-to-Use alternative to ElasticSearch
-
Updated
Jun 2, 2022 - C++
{{ message }}
Open Source alternative to Algolia and an Easier-to-Use alternative to ElasticSearch
Give your data the treatment it deserves with a framework-agnostic, datastore-agnostic JavaScript ORM built for ease of use and peace of mind. Works in Node.js and in the Browser. Main Site: http://js-data.io, API Reference Docs: http://api.js-data.io/js-data
An implementation of the exact same app in Firestore, AWS Datastore, PouchDB, RxDB and WatermelonDB
Google App Engine Boilerplate
A cluster consistency platform
Daily Stock Forecasts using Machine Learning & Python
Clean Architecture Example in Go
YANG-based configuration and operational state data store for Unix/Linux applications
A lightweight, self-contained, RESTful, searchable, multi-format NoSQL document store.
This repository contains sample code. Its purpose being, to quickly demonstrate Android and software development in general, clean code, best practices, testing and all those other must know goodies.
A collection of Magnolia add-on modules
ViyaDB in-memory columnar analytical data store
Kotlin Multiplatform Mobile demo for Android and iOS. App for viewing Cat pictures
Its a playground application focusing on Paging3, MVVM architecture, Kotlin Extension functions, Retrofit, DSL, Navigation component, MotionLayout, SharedElementTransition, Single Activity Architecture, DataStore etc.
Batching and Caching layer using Redis as the Caching layer
This is a project built using Jetpack Compose on UI, Clean architecture, Dagger Hilt, Kotlin Flow, Navigation Components etc.
Add a description, image, and links to the datastore topic page so that developers can more easily learn about it.
To associate your repository with the datastore 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