I’m continuing to play with CloudDB as the data store for the computerist solutions site. Currently the sidebar links are stored in clouddb, as well as optionally storing most page content in it. Currently, only the home page has its content in clouddb. It’s built so most pages check on first load if content is available in clouddb, otherwise render the normal view.
So all this makes me think.. why not add a users table and go full on CMS with it. I think it would work. So why not also build our own blog engine too. Again, it might just work but it becomes a question of size restrictions. I just don’t know what clouddb will allow/handle. I’ll have to ask the team about it.
Speaking of features, CloudDB is working on the next version. It may get released by the time this gets published. I’m waiting to see what changes there are. There will be JSON support I’m told, which will make be wonder whether to stick with the current webservice method of calling it or move to the JSON method.
Overall, I like clouddb. It’s perfect for the csinc site. It maintains the portability directive because we can host anywhere and still fetch data from clouddb. Plus we have some nice flexibility with the content. It really is an enticing solutions. It took some thinking to centralize the data access and caching, but worked out. Now I’m just waiting to see what clouddb v3 brings.
I’ll probably post again on CloudDB when the next version comes out. I’ll do some code samples at that time. Maybe a working sample project for people to try.
Other Goings On
In other news, I recently found myself considering buying a new vacuum. It was a good vacuum when we bought it but it had lost its power over the last year. Thanks to some random review, I rechecked the filter I thought I cleaned and found that it was actually just the housing for the actual filer. After cleaning it, the power is back! How many times have you felt you code base is old and worn out? Maybe you just need clean it out a bit instead of throwing it away. Add some tests, maybe use clouddb, or refactor some common code. Having made the clouddb changes to csinc, it feels refreshed and not so stale. I still want some more clean up and better testing but I like where its going. ..just a little life lesson applied to work.