Saturday, March 06, 2010 8:40 PM
Before I start cramming code, I’ll like to know what you guys think. I’ve been working heavily on my key value store and it has been working as expected, however, the main reason for me building this store does not seem to be completely eliminated with the functionalities that I have in place so far. therefore, I’ll like to add an extra piece to the jigsaw but before I do so I’ll like to hear what you have to say.
The storage engine itself is solid and it works with the minimal functionalities that it currently has. As a king of simplicity, I intentionally built it with everything in its simplest form and no worries, I’ll beef them up as need for whatever changes arise. Ok, that being said for you to use this database, you’ll need to use a client and at this point in time, I have implemented two clients; namely memory and network and I’ll like to add a third which is what this post is all about.
Note: Regardless of which client you are using persistent storage is always available.
Memory Client
Allows you to run the store completely in memory and disk if persistent mode is enabled. This could be used more or less like a caching mechanism or an embedded database.
Network Client
With this client you can connect to the store using an IP address and port number across a network or local, you have to be running the network server client somewhere. This client is what you will use to connect to where the network server is running.
Web Application Client (proposed)
Since the reason for building this database was because of a long grown frustration which is (speed and simplicity), I wanted a database that will allow me to put out a web application very fast and efficiently while being reliable and fast. After implementing the above 2 clients, a thought came to me – what if I also add a third client which allows the developer to build a web application right on top of my KVS? By doing so, developers will be able to build applications using (XHTML, JSON & JavaScript) completely client side. it doesn’t get any better than that. Here are some of the requirements:
- should allow for ASP.NET pages including ASMX pages
- should allow because XHTML
- should allow JavaScript
- should contain a canned admin tool
- should allow use of existing websites
- should implement some sort of template engine
- should allow the developer the ability to indicate which framework should be included such as JQuery
- should include its own KVS JavaScript framework, that will allow the developer to communicate with the database easily
- should be very light weight
- should be RESTful
So what do you think, does the Web Application Client raise your eyebrows? Do you see yourself opening up the KVS UI application, click on”Add New Web Application”, config a few things, open up your favorite editor, code a whole web app in XHTML and JavaScript and using JSON as your data type – everything is fast and client side while also supporting your existing ASP.NET pages and code behind code?