GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - mp42/java-hashMap-X: Simple implementation of a volatile in-memory key-value store backed by Java's HashMap with support for transactions.

BranchesTags
Open more actions menu

Latest commit

 

History

7 Commits
7 Commits

Folders and files

NameName
Last commit message
Last commit date
src/hashMapX
src/hashMapX
 
 
.gitignore
.gitignore
 
 
README.md
README.md
 
 

Repository files navigation

java-hashMap-X

Simple implementation of a volatile in-memory key-value store backed by Java's HashMap with support for transactions.

LIMITATIONS

  1. Single-threaded process
  2. Only supports 1 data type (Strings)
  3. No recovery
  4. Currently only supports commands through a command line interface.

TO USE Compile and run Main. Supported commands are:

  1. SET KEY VALUE - adds/updates the key with the value and returns the previous value (if the key existed) or null if the key didn't exist yey.
  2. UNSET KEY - removes the key from the db. Returns the previous value if the key existed or null if the key didn't exist.
  3. GET KEY - retrieves the current value of the key or null if the key doesn't exist.
  4. BEGIN - starts a transaction block (can be nested)
  5. ROLLBACK - undo-s all commands in the current transaction block.
  6. COMMIT - commits all transaction blocks
  7. END - exits the session

FUTURE WORK/FEATURES

  1. Modify structure so that it can be easily imported to use in applications instead of just CLI
  2. Use concurrent data structures to allow for multi-threaded accesses to the data store.
  3. Model transactions as threads
  4. Add / allow more data types (use Generics)

MAYBE?

  1. Persistence (leaning towards a Redis clone instead of memcached)
  2. Recovery

About

Simple implementation of a volatile in-memory key-value store backed by Java's HashMap with support for transactions.

Resources

Readme
Activity

Stars

2 stars

Watchers

1 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.