P7bmlogb3nhz6wxslgpo
SkillsCast

(Rails->Clojure :Remove Database)

4th December 2017 in London at CodeNode

There are 23 other SkillsCasts available from Clojure eXchange 2017

Please log in to watch this conference skillscast.

670714469 640

During this talk, you will discover how Hugo and team re-wrote one of their core web applications from Rails to Clojure. While this sounds like a typical story there is one key difference - you will learn that the new service has been implemented without a database. Due to some unique requirements of the application, it was decided that rather than reading data from a database instead, you could keep your data in memory, all the time. This of course led to some challenges of the application itself which Hugo will share more on, most importantly "how do you keep that data up to date?". Spoiler alert, data persistence does exist, however the service itself is loosely coupled and not reliant on it for serving requests, doing more than just caching data. You will learn how Hugo managed to implement this service using Clojure and some of the key features that was found that made it all possible such as agents, transducers, and Stuart Sierra's component library.

YOU MAY ALSO LIKE:

Thanks to our sponsors

(Rails->Clojure :Remove Database)

Hugo Firth

Hugo is a software developer with uSwitch where he spends his days writing Clojure and avoiding writing Ruby on Rails. Previously he worked with ThoughtWorks Australia where he worked with a range of languages and had his first experience with Clojure.

SkillsCast

Please log in to watch this conference skillscast.

670714469 640

During this talk, you will discover how Hugo and team re-wrote one of their core web applications from Rails to Clojure. While this sounds like a typical story there is one key difference - you will learn that the new service has been implemented without a database. Due to some unique requirements of the application, it was decided that rather than reading data from a database instead, you could keep your data in memory, all the time. This of course led to some challenges of the application itself which Hugo will share more on, most importantly "how do you keep that data up to date?". Spoiler alert, data persistence does exist, however the service itself is loosely coupled and not reliant on it for serving requests, doing more than just caching data. You will learn how Hugo managed to implement this service using Clojure and some of the key features that was found that made it all possible such as agents, transducers, and Stuart Sierra's component library.

YOU MAY ALSO LIKE:

Thanks to our sponsors

About the Speaker

(Rails->Clojure :Remove Database)

Hugo Firth

Hugo is a software developer with uSwitch where he spends his days writing Clojure and avoiding writing Ruby on Rails. Previously he worked with ThoughtWorks Australia where he worked with a range of languages and had his first experience with Clojure.

Photos