Bruce Eckel reviews some of the ideas and practices of the development community, outlining patterns of the problems related to communication, organization, process, etc. it has been trying to resolve.
Adrian Cockcroft discusses strategies, patterns and pathways to perform a gradual migration towards modern enterprise applications based on cloud, microservices and denormalized NoSQL databases.
Aviran Mordo introduces Wix's architecture, a highly available eventually consistent system, along with patterns for rendering many websites with a relatively small number of servers.
Mike Amundsen reviews patterns in developer practices and trends in services and libraries - from the increase in the number of client-side libraries such as EmberJS, Angular, and Bootstrap to the appearance of new "API composition" platforms such as Strong Loop - that give us a picture of why it's important to identify and leverage the growing sentiment that "Clients Matter, Services Don't".
Stuart Sierra discusses various Clojure features: protocols, records, DI, managing startup/shutdown of components, dynamic binding, interactive development workflow, testing and mocking.
Uwe Friedrichsen discusses several easy to implement resilient software design patterns, when to use them and how to actually implement them - code included along with options to extend and improve those patterns in order to make an application more robust step by step in order to achieve the next level after agile and clean code: Becoming a resilient software developer!
Mitchel Sellers uses multiple real-world applications to show practical implementations of Async within actual applications, covering various scenarios and implementations of the Async pattern.
Adam Warski shows how to replace features of DI containers with plain Scala code using MacWire, and adding interceptors using macros.
Adam Rosien introduces scalaz, how to use it to make code simpler and type safer, how it compensates for Scala issues, and how it encapsulates DI and data validation.
Jamie Allen reviews some of the actor patterns as implemented in Akka and Scala.
Jamie Allen describes three patterns using Akka actors: handling a lack of guaranteed delivery, distributing tasks to worker actors and implementing distributed workers in an Akka cluster.
Nat Pryce, Steve Freeman advise on design principles useful to create code structures with objects that fit together and communicate, and where the capabilities and the information flow are explicit.