“Design patterns are a surefire way to make your projects scalable, maintainable and optimised. At Google I/O 2018, Google introduced the BLoC pattern. It took a bit of time for me to understand the concept totally and to be able to actually use it in one of my projects. To help my fellow developers out, I detailed below my process of integrating BLoCs in the applications that I develop. I hope sharing this can help other developers understand the pattern easily.”
As often happens, I have about 50 browser tabs open, and in an effort to close some of those down, these are some of the best links I found while working with RxJava a week or two ago:
The first thing you do is create a new Gradle/Java project with these commands:
mkdir MyProject cd MyProject gradle init --type java-application
With that project created you can begin creating some Java/RxJava code.
I’m a big fan of the book, Functional and Reactive Domain Modeling, and these are some of my notes (“CliffsNotes”) from the book, most of them coming from the first chapter.
In this short blog post I will try, in 10 minutes or less, to present what Monix library is and convince you that it is good to know it.
Formerly known as Monifu, Monix is a library for asynchronous programming in Scala and Scala.js
PayPal Engineering has an article titled, Learning from Using a Reactive Platform — Akka/Squbs.
I’m not yet sure if I like the book Functional and Reactive Domain Modeling, but one thing is for sure: I couldn’t begin to understand it if I didn’t first do the research to write Learning Functional Programming in Scala. The author immediately jumps into monads as if they are commonly understood, and also designs his functions as “modules” in a very Haskell-ish way. I’m not saying the book is bad, just that it has a high barrier to entry.
This image comes from a reactivesystems.eu article titled, Things I wish I knew when I started building reactive systems.
Lightbend has a good article by Jonas Boner and Viktor Klang titled Reactive Programming versus Reactive Systems. This quote describes the article: “looking at the differences between writing code in a Reactive Programming style, and the design of Reactive Systems as a cohesive whole.”