software engineer

In this first episode we discuss the big picture ideas that make functional programming distinct from other styles of programming.  No experience required! If you're interested in learning what the fuss is about, this is the episode to start with.

Tell us what you think at contact@lambdacast.com

Transcription provided by Eric Inman
https://drive.google.com/file/d/0B3raKkneFJOXSU1rWEstSUwxTk0/view?usp=sharing

1: Overview Of Functional Programming

This time around we'll be talking over the core benefits of FP and why you might want to consider its use in your projects.

Tell us what you think at contact@lambdacast.com

Show Notes:
https://www.destroyallsoftware.com/talks/boundaries
http://blog.ploeh.dk/2015/08/17/when-x-y-and-z-are-great-variable-names/

3: Why FP?

Peter Bourgon discusses his work at Weaveworks, discovering and imlemeting CRDTs for time-stamped events at Soundcloud, Microservices in Go with Go Kit and the state of package management in Go.

Why listen to this podcast:

 - We’ve hit the limits of Moore’s law so when we want to scale we have to think about how we do communication across unreliable links between unreliable machines.
 - In an AP algorithm like Gossip you still make forward progress in case of a failure. In Paxos you stop and return failures.
 - CRDTs give us a rigours set of rules to accommodate failures for maps, sets etc. in communication that result in am eventually consistent system.
 - Go is optimised to readers/maintainers vs. making the programmers’ life easier. Go is closer to C than Java in that it allows you to layout memory very precisely, allowing you to, for example, optimise cache lines in your CPU. 
 - Bourgon started a project called Go Kit, which is designed for building microservices in Go. It takes inspiration from Tiwtter’s Scala-based Finagle which solved a lot of Micoservice concerns. 
 - Go has a number of community-maintained package managers but no good solution; work in ongoing to try and resolve this.

Notes and links can be found on: http://bit.ly/2kaHC9k

Work at Weaveworks
Gossip vs. Paxos
CRDTs at SoundCloud
Go
Go in large teams
Go and Java package management
Microservices in Go with Go Kit
Logging and tracing in a distributed environment

More on this:
Quick scan our curated show notes on InfoQ. http://bit.ly/2kaHC9k

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

InfoQ Podcast

Show Notes

Peter Bourgon on Gossip, Paxos, Microservices in Go, and CRDTs at SoundCloud

Jonas Bonér, CTO of LightBend and creator Akka, discusses using Akka when developing distributed systems. He talks about the Actor Model, and how every Microservice needs to be viewed as a system to be successful. 

Why listen to this podcast:

 - Akka is JVM-based framework design for developing distributed systems leveraging the Actor Model - an approach for writing concurrent systems that treat actors as universal primitives and the most successful model with abstraction has been streaming
 - Circuit breakers in Akka are a backup and retry policy; they protect you by capturing failure data and allow you to roll back 
 - Every Microservice needs to be viewed as a system, it needs to have multiple parts that run on different machines in order to function and be fully resilient - thus is a Microsystem
 - Two different trends have emerged when it comes to hardware and environments: one is the trend toward Multi-core, the is a movement toward virtualized environments and the cloud
 - Saga pattern of managing long running transactions in a distributed system fits very well with messaging style architectures

Notes and links can be found on: http://bit.ly/2kwB2eB

Akka
The Actor Model
When Akka and the Actor Model is the perfect choice
Circuit breakers patterns in distributed systems
Two trends toward Multi-core
Reactive Manifesto
Event Driven vs. Message Driven
Reactive Programming and Streams
Microliths to Microsystems
What do you have to get right before you start trying to deploy a distributed systems?
Working with ML / AI at Lightbend to understand tracing through distributed system
Saga Pattern

More on this:
Quick scan our curated show notes on InfoQ http://bit.ly/2kwB2eB

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Jonas Bonér on the Actor Model, Akka, Reactive Programming, Microservices and Distributed Systems

The kind of type system a functional language uses has a large impact on the way you use that language. In this episode we discuss the tradeoffs involved in using a static or dynamic language.

Our patreon sponsors this month:

Javier Troconis
Andrew Newman
Derek Morr
Olov Johansson

Show Notes:

Philip Wadler Talk: https://www.infoq.com/presentations/category-theory-propositions-principle

Denotational Design 

Scott Wlaschin Poker Implementation
https://exit.sc/?url=https%3A%2F%2Ffsharpforfunandprofit.com%2Fddd%2F

Conal Elliot presentation on Denotational Design
https://www.youtube.com/watch?v=bmKYiUOEo2A

Our recomendation for a DDD book
https://www.amazon.com/Patterns-Principles-Practices-Domain-Driven-Design/dp/1118714709

14: Dynamic and Static Languages

Software engineers, architects and team leads have found inspiration to drive change and innovation in their team by listening to the weekly InfoQ Podcast. They have received essential information that helped them validate their software development map. We have achieved that by interviewing some of the top CTOs, engineers and technology directors from companies like Uber, Netflix and more. Over 1,200,000 downloads in the last 3 years.

Peter Bourgon on Gossip, Paxos, Microservices in Go, and CRDTs at SoundCloud

InfoQ

Related tracks