Scala at journi

Review of using Scala and Play Framework for 2 years at journi.

Transcript

1. A travel journaling app & web platform at Christian @papauschek
2. Challenges Web & Mobile platform 15000 users, 800 daily active users Real time (push-)notifications Storing lots of pictures (GBs / day) Handling Apple featurings …
3. Scala libraries we use • Play Framework 2.3 • Slick 2.1 • Akka (for “cronjobs”)
4. (Java libraries we use ;-) • ImgScalr • Amazon S3 Library • Twitter4J • LogEntries (Cloud logging) • Metadata extractor (EXIF) Started replacing them with Play-WS
5. Our experience • We love Scala. • We love Play Framework 2. • We have a love / hate relationship with Slick 2.
6. • Having type-safe db access is great. • Having generated SQL in combination with ancient query optimizers is not so great. • Had to write SQL manually in some cases :(
7. (intermission) Be careful when picking your database!
8. Framework 2 • Very stable • Very performant (something else will be slow :D) • Team-friendly • Akka in the backend opens up possibilities • Exciting future (ScalaJS + Play2, anyone?)
9. Project structure 4 project modules web mobile common tools JS/HTML JSON API everything and the kitchen sink command-line helpers
10. Where to run a Play 2 app? • Huge performance differences (SSD!) • Huge price differences • We evaluated AWS / DigitalOcean / Linode / Hetzner
11. Server Monitoring • Find issues before they become real problems. • Is Facebook down, or your app?
12. Uptime so far (includes 2 Apple featurings)
13. Thank you, Play Framework! ~148ms response time
14. Thanks! Got questions?