ACM Comm 2017 11 Hootsuite: In Pursuit of Reactive Systems (Notes)

"Reconfigurable Cambits" CACM November 2017

Hootsuite: In Pursuit of Reactive Systems p.36-43

Automatic Program Repair with Evolutionary Computation

"A discussion with Edward Steel, Yanik Berube, Jonas Bonér, Ken Britton, and Terry Coatta"
Scala and Lightbend offer a reactive application platform
Migration from LAMP stack to microservices.
Just how reactive is it?

People

1. Edward Steel
2. Yanik Berube
3. Jonas Bonér
4. Ken Britton
5. Terry Coatta, CTO at Marine Learning Systems an narrator.

Ideas

1. Migrated from PHP to Scala because Twitter did.
2. Erlang Actor system
3. Embrace the "let it crash" philosophy. Adds robustness.
4. After all, coding for asynchronous distributed systems has long been considered ground that only the most highly trained Jedi should dare to tread.
5. With integrated message passing you don't really need functions. Each function can be an actor passing messages to other function actors.

References

1. Hootsuite[1] Social Media SaaS.
2. Scala[2]
3. Scala Futures - Sending messages.
4. Lightbend[3]
5. Akka[4] Scala library
6. Actor Model[5]
   1. Actor Models are hierarchies. Hmmm.
7. Single Task Actor
8. ZeroMQ

Internal Links

Parent Article: Reading Notes