Lucas Cavalcanti Clojure Remote 2017 Speaker Interview

Lucas Cavalcanti will be giving a keynote at Clojure Remote 2017. He will be speaking about building microservices using Clojure.

Follow him on Twitter and GitHub.

PurelyFunctional.tv: How did you get into Clojure?

Lucas Cavalcanti: I started writing Clojure professionally when I joined Nubank over 3 years ago today. At that time there was some literature about the Clojure language and some of its tools, but not much on service design patterns or how to use the power of functional programming to build real world applications. So me and the rest of Nubank's team adapted our previous experiences on OO languages, experimenting lots of styles and patterns until it eventually got to a simple and productive way of building and evolving services.

PF.tv: What is your talk about?

LC: Is an experience report on the microservices architecture we've built at Nubank, covering how we design and organize code in a single service and how they interact and compose with each other, and some simple patterns that emerged and helped us make the code simpler.

PF.tv: Who is your talk for?

LC: Anybody which are developing backend services.

PF.tv: What do you hope people will take away from the talk?

LC: A suggestion on how to organize your service code and patterns of integration and composability between services

PF.tv: What concepts do you recommend people be familiar with to maximize their experience with the talk?

LC: Hexagonal Architecture aka Ports and Adapters, synchronous and asynchronous integrations, schemas and forward compatibility

PF.tv: What resources are available for people who want to study up before the talk?

LC:

PF.tv: Where can people follow you online?

LC: I'm @lucascs on Twitter and GitHub.

PF.tv: Where do you see the state of Clojure in 10 years?

LC: Clojure would be the inspiration of newer simple and functional languages and will be one of the top 5 programming languages

PF.tv: If Clojure were an animal, what animal would it be?

LC: A Dolphin, because it's smart and looks like parenthesis ;)