Please log in to watch this conference skillscast.
I wrote a database in Clojure, it's not a very good database but I had a lot of fun doing it. One of the common questions I found myself asking the Clojure community was ""how on earth do you deal with resources in a non-pure and lazy functional programming language?""
The database had file handles, pointers to native code and various network sockets and loading all of the data into memory wasn't an option. What was tried and discarded and what patterns did I end up with? This will be a very quick whirlwind tour with a potentially controversial set of conclusions.
YOU MAY ALSO LIKE:
- Functional Concurrency in .NET with C# and F# (in London on 9th - 10th September 2019)
- Fast Track to F# with Tomas Petricek & Phil Trelford (in London on 9th - 10th September 2019)
- Haskell eXchange 2019 (in London on 10th - 11th October 2019)
- Clojure eXchange 2019 (in London on 2nd - 3rd December 2019)
- Causal inference and the data-fusion problem (in London on 18th June 2019)
- The wonders of IBM: Watson, artificial intelligence, Swift coding and databases! (in London on 19th June 2019)
- Scala 2.13 and Beyond! (SkillsCast recorded in April 2019)
- Distilling Agile for Effective Execution (SkillsCast recorded in April 2019)
Resource management in clojure
Rob Ashton is a freelance developer providing project-based development efforts to clients all over the world. He has been a core committer to the RavenDB project since the early days of pre-release, contributing features such as the dynamic indexes