Insurance policies, etc. are complicated graphs even for a relational database model. I am not convinced you have to use clojure's functional data structures for these graphs. I've seen good ORM frameworks run out of steam on insurance apps as well.
As part of the _processing_ of insurance functions, I would use the functional structures for sure. But the full graphs (insurance documents) themselves? Not so much. After working with various insurance implementations, I currently believe one of the best representations is a good graph database (whether durable on disk or just in memory). Something like AllegroGraph provides additional features like querying and inference over v.large graphs. It's real hard building insurance graph processing from scratch but clojure can use the java API to AllegroGraph, and there are other good open source graph/semantic systems as well. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
