Skip to main content

Replacing a repository

They say you should blog about something you like, stick to the subject, be informal, and write something useful. Add subjective knowledge to the community.

My thoughts on the field of content management haven't really evolved much since I began working one month ago, but I have encountered a portal/CMS system which I sooner or later will have to use and develop with, I guess. Now the sorry thing about this portal is that I can't utilize my experience with the Java content repository (JCR) standard JSR-170. The portal vendor *could* implement support for it, but as I guess the internal datastructure is, this would lead to an entire replacement of the existing repository, throwing some years of development and use out of the window.

My gut feeling tells me this would not be worth it at this point. But for the sake of argument, let's wheigh the implications of replacing a homegrown repository with for instance Jackrabbit.

Negative implications

Implementation. The datastructure needs to be re-written. The persistence mechanisms might not be loosely bundled enough, or interfaced in the same way as the JCR, so the old repository can't just be unplugged and replaced with Jackrabbit.

Existing content. There are probably thousands of pages of existing content using the old data structure. Literally this is an implication you get to feel when migrating from one CMS to another, but it also applies when changing the content repository alone. Imagine all the customers that will have to migrate their content when they wish to upgrade to the latest version of the portal.. Ugh.

Positive implications

Developer friendly. I know JSR-170, so I already know how to use the repository. I don't need to spend X weeks learning the repository domain model and its API.

It's a standard. The repo becomes compliant with the standard. Content can be imported and exported between other JCRs.

Free stuff. Jackrabbit has implemented alotta nice features the spec provides, versioning, security, search, transaction management and access control to name a few.

Any more implications? To me, the migration one stands out as the biggest blocker. And as long as the customers don't have a need for stuff like that, JCR-compliance remains a (rather weak) sellng point.

Haven't got any more time now, will try to write back with the "conclusion" later on. In a couple o' weeks I will actually get to meet the lead guy of this portal's development, and I have until then to come up with the arguments to convince him. But first I have to convince myself :)

Comments

Popular posts from this blog

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well: I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there. It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences. To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer s

Using Voice-Chat for Gamers in Distributed Teams

This is a post going into the usefulness of live voice-chat tools in distributed teams. If you've ever seen the Leeeeeroooooyy Jeeeenkiiins video of World of Warcraft fame, you've heard this kind of tool in action. It's how the participants in the video are speaking with each other - this is not a feature built into the World of Warcraft game - it's a separate team-oriented VoIP software, and it's all about letting gamers communicate orally while gaming.  Since these tools are for gamers, they have to be fast (low latency) light (as not to steal CPU-cycles from heavy games graphics)  moderate in bandwidth usage (as not to affect the game server connection) There are several options around: TeamSpeak , Ventrilo , more recently the massively grown Discord , and finally Mumble , which is the open-source alternative of the gang. A few years ago, when I joined eyeo (a distributed company), several of the operations team were avid gamers, and had a TeamSp

Joining eyeo: A Year in Review

It's been well over a year since I  joined eyeo . And 'tis the season for yearly reviews, so... It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling. Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes: How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies wit

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --