Posts with keyword: patterns

4 entries

Reactive Programming Patterns: Examples from Fuse

Tue Apr 5 17:23:00 2016

Reactive programming requires new programming techniques and methods. This post describes common patterns in asynchronous reactive programming and gives examples from the open-source code base for the Fuse connected car platform. While the examples below are based on the pico platform, they are equally applicable to other Actor-based reactive programming platforms like Akka.
Continue reading {Reactive Programming Patterns: Examples from Fuse}

Using the Scatter-Gather Pattern to Asynchronously Create Fuse Reports

Wed Sep 16 16:42:00 2015

This post describes how I used the scatter-gather pattern to move from a synchronous process for generating fleet reports to an asynchronous solution, avoiding some failures that were caused by load and short HTTP timeout values. The result is a system that is more reliable and scalable than the previous, request-based synchronous solution.
Continue reading {Using the Scatter-Gather Pattern to Asynchronously Create Fuse Reports}

Sharing in SquareTag: Borrowing my Truck

Wed Jul 17 13:39:00 2013

The introduction pattern allows one cloud to introduce two clouds to each other. This is useful for sharing and delegating and forms the basis for social products in SquareTag.
Continue reading {Sharing in SquareTag: Borrowing my Truck}

KRL Patterns: Building Event Intermediaries

Wed Sep 29 09:38:00 2010

Recently we somewhat quietly added a BIG new feature to KRL: explitic events. Using an explicit event, one rule can raise an event for another rule. Explicit events are raised in the rule postlude like so raise explicit event foo [for ] with fizz = "bazz" and fozz = 4 + x; If the optional for clause isn't given, the event is raised for the current ruleset, otherwise it's raised for the named ruleset. The with clause allows the developer to add event parameters to the explicit event. The right-hand side of the individual bindings in the with clause
Continue reading {KRL Patterns: Building Event Intermediaries }