One year ago a team at Getty Images began building the foundation for a new asset management platform to replace a set of third-party systems. The team adopted Scala and the Akka framework centered around a queue-based architecture via RabbitMq, relying on event sourcing for persistence. The new system runs on AWS featuring "immutable servers" by automating ready-to-go AMI's built with Packer and Puppet and deployed with AWS CloudFormation.

In this talk we'll explore some of the design decisions which went into the system and the patterns which emerged as the system developed.

How do you wire asynchronous, queue based systems together?

Why event sourcing?

What are "immutable servers" and how do they solve build-and-deploy problems?

What patterns emerge when building actor-based systems with Akka?

Developing API's with Akka and Spray and sharing them with Swagger

SPONSOR AND HOST

We'd like to thank Tumblr for hosting our April 21 event and sponsoring pizza and refreshments.