So far, I have created a number of actors that together make up a simple, non-exciting simulation. However, controlling these actors is still done in an ad-hoc fashion.
In the next couple of posts, I will extend the simulation with supporting objects that make it easier to create and run different kinds of simulations. This post is dedicated to the theory behind these next steps.
In this post, I will introduce Actor states, the Controller, Rule sets and Settings.
In my previous post, I created a specification for my Harvesters. Now it's time to actually implement them and let them conform to that spec.
This post is mostly about messaging between actors, the different choices in handling those messages, and the impact these choices have on the concurrency of your system.
In my previous post, I introduced the Producer actor. Now it's time to introduce the Harvester.
In this post I will define the specifications of the Harvester and show how to test the concurrency of the eventual implementation.
In order to do this, I will also dive into some of the cooler features of Scala, especially foreach, map, list-comprehensions and futures.
Now that the project has been set up, it's time to start creating the first steps in our simulation.
Every city simulation game I've played begins the same: getting workers to obtain raw materials. So let's create a text-only simulation that does just that.
This post is about Scala syntax, Scala Actors, Scala messages, and examples of pattern matching.
