Over this series of posts I’m going to look at recreating some of the basic functionality of Google Calendar including the capability of adding recurring events within Grails. We’ll start by looking at the model.
If you want to run a grails app (or any Java app that requires a servlet container) Tomcat is an excellent choice. You’ll need to do this if you’re hosting your app on a VPS like Linode (highly recommended) or if you’re using AWS and want a little more control than Elastic Beanstalk allows you. I preformed the following steps on an Ubuntu 10.04 server.
Note The RSS feed source referenced in this article is no longer available.
It seems that a lot of people are talking about taking their applications to “the cloud” (uggh) and are singing the praises of services like Amazon Web Services. On paper its “pay for what you use” approach would make it seem like a much cheaper option than a VPS hosting option such as Linode where the costs are fixed. This variable model only really makes sense if your usage is truly variable though. If you’re using AWS to deploy a few dedicated servers then you might be paying too much.
If you find yourself in a situation where you need to wire up a legacy Oracle stored procedure to a grails controller action, groovy makes this pretty simple. In my example I have a stored procedure with a single parameter that returns results through a reference cursor. Here’s our stored proc: