Dean Wampler, Ph.D.
Software developer, expert in Big Data, Scala, and Functional Programming,
O'Reilly author, and frequent public speaker living in Chicago.
Polyglot Programming is a website dedicated to exploring the benefits (and drawbacks) of combining multiple programming languages and multiple "modularity paradigms" in application development. The "paradigms" include Functional Programming, Object-Oriented Programming, and Aspect-Oriented Programming.
Aspect Oriented Programming
AOP is an attempt to address cross cutting concerns in applications. The dominant decomposition into modules usually reflects the domain model or perhaps the implementation infrastructure. However, it becomes difficult to add in globally-consistent features, like logging, that cut across these module boundaries. AOP attempts to solve this problem.
Talks & Papers
Why Spark Is The Next Top (Compute) Model
Numerous Venues - 2014, 2015
Spark has emerged as the replacement for MapReduce in Hadoop applications. This talk explains why.
Spark on Mesos
Strata + Hadoop World London 2015
While Spark is now popular on Hadoop, managed by YARN, it emerged as demonstration project for Mesos. This talk explores Mesos, compares it to YARN, and argues for why you should consider a Spark + Mesos cluster.
Data Science at Scale with Spark
GOTO Chicago 2015
Using examples, I show how to use Spark for Data Science at scale in ways that were previously not feasible with other tools.
The Unreasonable Effectiveness of Scala for Big Data
Scala Days 2015.
Why Scala has proven so effective as the general-purpose programming language for Big Data development.
Reactive Systems - The Why and the How
Software Architecture 2015 and CJUG May 2015
What exactly are Reactive Systems, as described by the Reactive Manifesto, and why are they important for modern architectures?
Error Handling in Reactive Systems
React Conf San Francisco 2014, Software Architecture 2015
Failure handling must be "first-class" in reactive systems, to satisfy the resilient trait. This talk discusses how reactive models and libraries support failure handling (or don't).
See all my talks and papers.