From 35d38f654fe69718caaea0ba8f22a78d4a701abf Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 26 Sep 2024 18:14:56 +0600 Subject: [PATCH] chore: update roadmap content json (#7234) Co-authored-by: kamranahmedse <4921183+kamranahmedse@users.noreply.github.com> --- public/roadmap-content/android.json | 30 +++++++++++++++++++++++++---- public/roadmap-content/redis.json | 10 ++++++++-- 2 files changed, 34 insertions(+), 6 deletions(-) diff --git a/public/roadmap-content/android.json b/public/roadmap-content/android.json index 50216cd62..f3885718c 100644 --- a/public/roadmap-content/android.json +++ b/public/roadmap-content/android.json @@ -535,13 +535,35 @@ }, "GWq3s1iTxQOp1BstHscJ9": { "title": "DataStore", - "description": "`DataStore` is a new and improved data storage solution by Android, meant to supersede `SharedPreferences`. It is important to understand that it comes in two different implementations: `Preferences DataStore` and `Proto DataStore`. `Preferences DataStore` uses key-value pairs similar to `SharedPreferences`, but it's more robust and handles runtime exceptions more efficiently. On the other hand, `Proto DataStore` uses custom data types to provide type safety. It lets you leverage the power of Protocol Buffers, a language-neutral, platform-neutral mechanism for serializing structured data, as the data storage format. Operating on data in `DataStore` is transactional, meaning that if an error occurs during an operation, all changes are rolled back, so the data remains in a consistent state.", - "links": [] + "description": "`DataStore` is a new and improved data storage solution by Android, meant to supersede `SharedPreferences`. It is important to understand that it comes in two different implementations: `Preferences DataStore` and `Proto DataStore`. `Preferences DataStore` uses key-value pairs similar to `SharedPreferences`, but it's more robust and handles runtime exceptions more efficiently. On the other hand, `Proto DataStore` uses custom data types to provide type safety. It lets you leverage the power of Protocol Buffers, a language-neutral, platform-neutral mechanism for serializing structured data, as the data storage format. Operating on data in `DataStore` is transactional, meaning that if an error occurs during an operation, all changes are rolled back, so the data remains in a consistent state.\n\nVisit the following resources to learn more:", + "links": [ + { + "title": "Documentation", + "url": "https://developer.android.com/topic/libraries/architecture/datastore", + "type": "article" + }, + { + "title": "Introduction to DataStore", + "url": "https://www.youtube.com/watch?v=9ws-cJzlJkU&list=PLWz5rJ2EKKc8to3Ere-ePuco69yBUmQ9C", + "type": "video" + } + ] }, "Bfg4So5RlI09zFNcburJd": { "title": "Room Database", - "description": "\"Room\" is a persistence library introduced by Google that provides an abstraction layer over SQLite to help with robust database access while harnessing the full power of SQLite. Room supports the creation of databases and defines queries in compile-time-checked SQL strings. These databases belong to the data classes that you create representing your app's data. Room comprises three main components: **Database**, a container that holds your app's data tables; **Entity**, representing a table within the database; and **DAO (Data Access Object)**, containing SQL query methods to interact with the database.", - "links": [] + "description": "\"Room\" is a persistence library introduced by Google that provides an abstraction layer over SQLite to help with robust database access while harnessing the full power of SQLite. Room supports the creation of databases and defines queries in compile-time-checked SQL strings. These databases belong to the data classes that you create representing your app's data. Room comprises three main components: **Database**, a container that holds your app's data tables; **Entity**, representing a table within the database; and **DAO (Data Access Object)**, containing SQL query methods to interact with the database.\n\nVisit the following resources to learn more:", + "links": [ + { + "title": "Save data in a local database using Room", + "url": "https://developer.android.com/training/data-storage/room", + "type": "article" + }, + { + "title": "The full beginner guide for Room in Android", + "url": "https://www.youtube.com/watch?v=bOd3wO0uFr8&t=10s", + "type": "video" + } + ] }, "A4kdaj6AFueUgPI7hwKi5": { "title": "File System", diff --git a/public/roadmap-content/redis.json b/public/roadmap-content/redis.json index 2505a33d0..7d62b734c 100644 --- a/public/roadmap-content/redis.json +++ b/public/roadmap-content/redis.json @@ -1,8 +1,14 @@ { "-3pADOHMDQ0H6ZKNjURyn": { "title": "What is Redis?", - "description": "", - "links": [] + "description": "Redis is an open-source, in-memory data structure store, primarily used as a database, cache, and message broker. It supports various data structures like strings, hashes, lists, sets, and sorted sets, making it highly versatile. Redis operates with extremely low latency due to its in-memory nature, enabling fast access to data. It is often used in real-time applications such as session management, leaderboards, or caching mechanisms, where quick data retrieval is critical. Additionally, Redis supports data persistence by periodically writing the dataset to disk, balancing memory speed with data reliability.\n\nVisit the following resources to learn more:", + "links": [ + { + "title": "What is redis?", + "url": "https://redis.io/docs/latest/get-started/", + "type": "article" + } + ] }, "M-EXrTDeAEMz_IkEi-ab4": { "title": "In-memory Data Structure Store",