How do you do dependency injection with the Cake pattern without hardcoding?

by

Since mixing in traits is done statically in Scala, if you want to vary the traits mixed in to an object, create different objects based on some condition.

Let’s take a canonical cake pattern example. Your modules are defined as traits, and your application is constructed as a simple Object with a bunch of functionality mixed in

val application =
    new Object
extends Communications
   with Parsing
   with Persistence
   with Logging
   with ProductionDataSource
application.startup

Now all of those modules have nice self-type declarations which define their inter-module dependencies, so that line only compiles if your all inter-module dependencies exist, are unique, and well-typed. In particular, the Persistence module has a self-type which says that anything implementing Persistence must also implement DataSource, an abstract module trait. Since ProductionDataSource inherits from DataSource, everything’s great, and that application construction line compiles.

But what if you want to use a different DataSource, pointing at some local database for testing purposes? Assume further that you can’t just reuse ProductionDataSource with different configuration parameters, loaded from some properties file. What you would do in that case is define a new trait TestDataSource which extends DataSource, and mix it in instead. You could even do so dynamically based on a command line flag.

val application = if (test)
  new Object
    extends Communications
      with Parsing
      with Persistence
      with Logging
      with TestDataSource
else
  new Object
    extends Communications
      with Parsing
      with Persistence
      with Logging
      with ProductionDataSource

application.startup

Now that looks a bit more verbose than we would like, particularly if your application needs to vary its construction on multiple axes. On the plus side, you usually you only have one chunk of conditional construction logic like that in an application (or at worst once per identifiable component lifecycle), so at least the pain is minimized and fenced off from the rest of your logic.

More Related Contents:

  1. How to define “type disjunction” (union types)?
  2. Spark – load CSV file as DataFrame?
  3. What is a higher kinded type in Scala?
  4. How to define partitioning of DataFrame?
  5. In Scala, what is an “early initializer”?
  6. Case class equality in Apache Spark
  7. What is the difference between Scala’s case class and class?
  8. Confused with the for-comprehension to flatMap/Map transformation
  9. What is the motivation for Scala assignment evaluating to Unit rather than the value assigned?
  10. Dropping a nested column from Spark DataFrame
  11. sbt-assembly: deduplication found error
  12. What does param: _* mean in Scala?
  13. Syntax sugar: _* for treating Seq as method parameters
  14. How to create a TypeTag manually?
  15. Weird behavior trying to convert case classes to heterogeneous lists recursively with Shapeless
  16. java.lang.NoClassDefFoundError: org/apache/spark/streaming/twitter/TwitterUtils$ while running TwitterPopularTags
  17. How to use COGROUP for large datasets
  18. Build.scala, % and %% symbols meaning
  19. Can I get a compile-time list of all of the case objects which derive from a sealed parent in Scala?
  20. How are Scala traits compiled into Java bytecode?
  21. Why are singleton objects more object-oriented?
  22. In Scala, what does “view” do?
  23. How to explode an array into multiple columns in Spark
  24. forall in Scala
  25. Treating an SQL ResultSet like a Scala Stream
  26. Scala asInstanceOf with parameterized types
  27. Queries with streaming sources must be executed with writeStream.start();
  28. How do I run an sbt main class from the shell as normal command-line program?
  29. Singletons as Synthetic classes in Scala?
  30. Akka-Stream implementation slower than single threaded implementation

Leave a Comment