In my "Day Job", we design and build our applications using Microsoft technologies. In particular, we’re using C#, Silverlight, and IIS to build and deploy our web applications. This makes good sense because the vendors we use are well versed in the Microsoft technology, and like the IT infrastructure of a lot of medium and large companies Microsoft solutions are at the forefront. It’s becoming apparent though that we’re going to have to consider our options and possibly embrace a different technology stack to properly scale and support the applications we’re building.
While I knew that Java servlets and the Spring Framework were the answers, credit goes to my boss Scott Ellis for really doing a deep dive into what technologies are on offer, and coming up with using Grails and Groovy as the best solution for us. Which brings me to the reason for this blog post. I’ve been spending some time playing around with Grails and Groovy, and familiarizing myself with the technology and what is on offer. I intend to do a series of posts here about my discovery process, what problems I encounter, and how I resolve them.
From the searching I’ve had to do in order to get answers or better understanding about the challenges I’ve faced, I think I have a chance to be a real resource to others who are just starting out with Grails and Groovy. What’s more I’m writing from the perspective of a relative newbie to the Java world. Stay tuned as you follow my journey into Grails and Groovy. *Spoiler alert* - I like it, a LOT!