Skip to main content

The domain

Note: Blogger is probably gonna mess up the styles in this post pretty bad, so forgive me if I re-post a couple o' times. View the original post if the feed item is garbled.

I've figured I need to get rolling on the example/reference case for the Action Domain Object-talk.

After some long and hard pondering I drifted away from the insurance domain and into something far more web 2'ish: an online community site.

I'm gonna call it The Universe. It's pretty simple, facebook'ish application that includes Worlds, Groups, Rooms and People.



Some cases:

  • The Universe can crud (save, browse and delete) Worlds
  • A World can crud Groups , Rooms and People
  • A Group/Room can add/remove People (members)
  • (or a Person can join/part Rooms and Groups)
  • A Person can send messages to People or Rooms
  • A Room is like a chat-room, as opposed to Group which is a more permanent organization of People
These 6 different entities are my Action Domain Objects.

It does have some complexing features, like a bunch of many-to-many relations, and plenty of alternative ways to implement the domain model, i.e. which entity is responsible for sending messages, manage People, etc.

Now, this wouldn't be any fun to implement without some restricting rules making it hard for me:

No Services and DAOs, only (a few) aspects/interceptors.

It will be implemented in Java.

Only one file/class per entity.

Operations should be RESTable.

They should be executable from a console application.

No XML (!).


So, then I started thinking about some URLs. Thinking URLs are a great way of getting an elegant web application. You get re-usable action chunks (cause you start thinking of atomial simple operations) and pretty URLs.

Let's trigger some operations:

Behold, The Universe:
/universe/browse
Create a World in the Universe:
/universe/worlds/create?name=earth
Next, create a Group in The newly created World:
/universe/worlds/earth/groups/create?name=developers
Create a person:
/universe/worlds/earth/people/create?name=ferris

Oh, I just discovered I need a couple of other entities to represent relations between People, Groups and Rooms. I'll use memberships for Groups and visits for Rooms.

Add me to the developer group (I'll skip the /universe/worlds/earth/ from this point):
.../memberships/create?member=ferris&group=developers
Later on, I log in:
.../members/ferris/login?password=postit
And join the chat-room "hackers":
.../visits/create?visitor=ferris&room=hackers
Send a message to the hackers-room, oh copy to John by the way:
.../messages/create?subject=Hey&sender=ferris&receipients=hackers;john

Right, think the idea is starting to come through. Now it's getting a bit late so I'll think I'll have to leave it like that. These URLs are very much subject to change, and if anyone can see any pitfalls I'm running in to, please comment.

Next week I'm gonna figure out whether I'm gonna make this happen with Grails or Struts2, or some other technology.


The following have been the inspirations to this post:

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 operating on many repositories at the same time.

I discovere…

Working in Teams over Working as Individuals

I recentlypostedthis sketch on Twitter:

Thanks to a few mighty retweets, it gathered a lot of views (9000 impressions, whatever that means). While that's fun and all, I still felt a bit sad that such an awfully simple insight can garner much more popularity than a thorough blog post that I put some hours into.

So, rather than let Twitter get away with this, I'll steal my own content back into the blog :)

The thread went like this:

Pondering how to battle individualism in companies. For some, it is counter-intuitive that teams can be more responsive, faster and even more accountable than single individuals.

Having "teams" in place is no guarantee that team work is happening. Be wary of too large teams, "I/me/mine", personal contact details instead of team point of contact. Good team is sailing crew, not galley slaves.

Beware heroes, go-to persons, calling in favors and other shadow handling of work. Real teams make the work explicit, both requests/needs and re…

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

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 science a…

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 without the…