A First Web Project with Clojure

Last nights GatorJUG prestation on Clojure with Eric Lavigne introduced us to Clojure's language elements. Say your customer, a timeshare company, wanted a new database driven reservation website. Build a case for Clojure and lay out a reasonable architecture, including use of existing Java components and object relational mapping, or not.

Views: 178

Replies to This Discussion

Permalink Reply by Eric Lavigne on January 16, 2010 at 11:19am
If I offered to finish the site in a week, would my client need further justification :-)

A timeshare reservation site would be fairly trivial from a technology perspective. For the web front-end, I would use Compojure, just as I did with the Wari contest. For database access, I would use clojure.contrib.sql, which has the same capabilities as java.sql but without being so incredibly verbose.

Architecture is important for big projects. This isn't a big project.
Permalink Reply by Michael Levin on January 16, 2010 at 12:10pm
So, Eric - can you say a few words about Compojure? Just enough to get us started. And, please point us to a reference. Is clojure.contrib.sql fairly full featured? Can it to stored procs and transactions? What are some of its strengths and limitations? Just a taste...

Eric Lavigne said:
If I offered to finish the site in a week, would my client need further justification :-)

A timeshare reservation site would be fairly trivial from a technology perspective. For the web front-end, I would use Compojure, just as I did with the Wari contest. For database access, I would use clojure.contrib.sql, which has the same capabilities as java.sql but without being so incredibly verbose.

Architecture is important for big projects. This isn't a big project.
Permalink Reply by Eric Lavigne on January 16, 2010 at 12:47pm
Compojure is a web development library with a focus on simple, RESTful applications. This example should give you a feeling for Compojure:

http://en.wikibooks.org/wiki/Compojure/Getting_Started#A_bit_more_v...

And here are some references:

http://en.wikibooks.org/wiki/Compojure/Core_Libraries
http://en.wikibooks.org/wiki/Compojure/Tutorials_and_Tips
http://github.com/weavejester/compojure


You can find some examples of clojure.contrib.sql here:

http://github.com/richhickey/clojure-contrib/blob/master/src/clojur...

And here's a reference:

http://richhickey.github.com/clojure-contrib/sql-api.html

clojure.contrib.sql has transactions and prepared statements. I don't know about stored procedures, since I have never used them in Clojure or Java.

RSS

Happy 10th year, JCertif!

Notes

Welcome to Codetown!

Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

 

Enjoy the site? Support Codetown with your donation.



InfoQ Reading List

Leapwork Research Shows Why AI in Testing Still Depends on Reliability, Not Just Innovation

Leapwork recently released new research showing that while confidence in AI-driven software testing is growing rapidly, accuracy, stability, and ongoing manual effort remain decisive factors in how far teams are willing to trust automation.

By Craig Risi

OpenAI Publishes Codex App Server Architecture for Unifying AI Agent Surfaces

OpenAI has recently published a detailed architecture description of the Codex App Server, a bidirectional protocol that decouples the Codex coding agent's core logic from its various client surfaces. The App Server now powers every Codex experience, including the CLI, the VS Code extension, and the web app, through a single, stable API.

By Eran Stiller

Does AI Make the Agile Manifesto Obsolete?

Capgemini's Steve Jones argues AI agents building apps in hours have killed the Agile Manifesto, as its human-centric principles don't fit agentic SDLCs. While Forrester reports 95% still find Agile relevant, Kent Beck proposes "augmented coding" and AWS suggests "Intent Design" over sprint planning. The debate: Is Agile dead, or evolving for AI collaboration?

By Steef-Jan Wiggers

Article: Proactive Autoscaling for Edge Applications in Kubernetes

Kubernetes often reacts too late when traffic suddenly increases at the edge. A proactive scaling approach that considers response time, spare CPU capacity, and container startup delays can add or remove instances more smoothly, prevent sudden spikes, and keep performance stable on systems with limited resources.

By Rajeev Kallayil Ravi

Chrome 144 Ships Temporal API: Advancing JavaScript Date/Time Standardisation

Chrome 144 introduces the groundbreaking Temporal API, revolutionizing date and time management in JavaScript. As a modern alternative to the criticized Date object, Temporal resolves parsing ambiguities, time zone complexities, and mutable arithmetic. With distinct types and built-in support, it empowers developers to handle dates seamlessly, though adoption varies across browsers.

By Daniel Curtis

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service