Clojure Tales From Behind The Firewall
This month John Stevenson will share his experiences of running a Clojure team in a large corporation and the practices used to help spread Clojure to other development teams.
The larger an organisation is, the more decisions on tooling are fixed. So I was expecting many battles of persuasion, but it turns out many things were much easier than expected, especially getting our favourite development tooling accepted. Building a streamlined development and deployment pipeline for Clojure was a bit more challenging, especially due to the constraint on using a specific CI server. We experimented with the Netflix approach to continuous integration and using Maven (without much XML).
Encouraging other teams to adopt Clojure has changed our developer tooling, as I wanted to make the gap to Clojure as small and manageable as possible. This involved reviewing the merits of IntelliJ, Atom, Visual Studio Code and of course Emacs from the viewpoint of the corporate developer.
Arguably the biggest technical challenge was the corporate firewall itself, especially when it came to downloading Clojure libraries only on Clojars.org. We found two solutions, one very hacking and ultimately failed, the other was trivial and worked perfectly.
So come along to the event and discover what technology stack we are using, our different development tooling choices, how we build our Clojure apps, how we got other teams to build Clojure apps and generally manage a Clojure application that processes millions of transactions a day across the world.
YOU MAY ALSO LIKE:
- Open Source your digital life with Emacs (SkillsCast recorded in December 2018)
- Real-time Systems with Spark Streaming and Kafka (in London on 30th September - 1st October 2019)
- CloudNative London 2019 (in London on 25th - 27th September 2019)
- Keynote by Ryn Daniels on Designing Sustainable Ops Cultures (in London on 21st August 2019)
- Fast Track to DevOps Fundamentals (in London on 23rd - 24th September 2019)
- Introduction to Docker Fundamentals (in London on 30th September - 1st October 2019)
- Weaveworks Special Event - Workshop: Your Path to Production Ready Kubernetes (in London on 5th September 2019)
- ProgNET London 2019 (in London on 11th - 13th September 2019)
- London Java Community August Meetup (in London on 28th August 2019)
- London Java Community August (in London on 28th August 2019)
- One Build to Rule Them All - Software development made easy with snap (SkillsCast recorded in August 2019)
- Designing Sustainable Ops Cultures (SkillsCast recorded in August 2019)
Thanks to our sponsors
Clojure Tales From Behind The Firewall
John Stevenson
John is a speaker, author, conference organiser & community obsessed developer. Loves Clojure, Emacs, Cats, Cycling & Agile development. He is a conference organiser for Clojure Exchange, London Java Conference, etc) with 20 years of speaking experience.
This month John Stevenson will share his experiences of running a Clojure team in a large corporation and the practices used to help spread Clojure to other development teams.
The larger an organisation is, the more decisions on tooling are fixed. So I was expecting many battles of persuasion, but it turns out many things were much easier than expected, especially getting our favourite development tooling accepted. Building a streamlined development and deployment pipeline for Clojure was a bit more challenging, especially due to the constraint on using a specific CI server. We experimented with the Netflix approach to continuous integration and using Maven (without much XML).
Encouraging other teams to adopt Clojure has changed our developer tooling, as I wanted to make the gap to Clojure as small and manageable as possible. This involved reviewing the merits of IntelliJ, Atom, Visual Studio Code and of course Emacs from the viewpoint of the corporate developer.
Arguably the biggest technical challenge was the corporate firewall itself, especially when it came to downloading Clojure libraries only on Clojars.org. We found two solutions, one very hacking and ultimately failed, the other was trivial and worked perfectly.
So come along to the event and discover what technology stack we are using, our different development tooling choices, how we build our Clojure apps, how we got other teams to build Clojure apps and generally manage a Clojure application that processes millions of transactions a day across the world.
YOU MAY ALSO LIKE:
- Open Source your digital life with Emacs (SkillsCast recorded in December 2018)
- Real-time Systems with Spark Streaming and Kafka (in London on 30th September - 1st October 2019)
- CloudNative London 2019 (in London on 25th - 27th September 2019)
- Keynote by Ryn Daniels on Designing Sustainable Ops Cultures (in London on 21st August 2019)
- Fast Track to DevOps Fundamentals (in London on 23rd - 24th September 2019)
- Introduction to Docker Fundamentals (in London on 30th September - 1st October 2019)
- Weaveworks Special Event - Workshop: Your Path to Production Ready Kubernetes (in London on 5th September 2019)
- ProgNET London 2019 (in London on 11th - 13th September 2019)
- London Java Community August Meetup (in London on 28th August 2019)
- London Java Community August (in London on 28th August 2019)
- One Build to Rule Them All - Software development made easy with snap (SkillsCast recorded in August 2019)
- Designing Sustainable Ops Cultures (SkillsCast recorded in August 2019)
Thanks to our sponsors
Clojure Tales From Behind The Firewall
John Stevenson
John is a speaker, author, conference organiser & community obsessed developer. Loves Clojure, Emacs, Cats, Cycling & Agile development. He is a conference organiser for Clojure Exchange, London Java Conference, etc) with 20 years of speaking experience.