Rock Solid Haskell Services (Part 6)
summary
Concrete Haskell code for running fault-tolerant services appears: a component-based app composes remote queue and remote topic abstractions, a worker pool reads SQS into a local queue to spread batches, and SNS/SQS are wired via Amazonica and localstack endpoints. A toxic proxy is created/cleaned as a component so tests can inject network faults, and operations are wrapped in a circuit breaker to fail fast — the repo and makefile are used to run and verify it.
AI-written summary · about
chapters (9)
- 0:00Main
- 2:30crawler
- 8:45remoteQ
- 16:45test logic
- 18:28remote topics
- 21:10hashmap
- 26:01build
- 26:42remotequeue
- 29:25toxic
related talks
37mBuilding Reactive Services Using Functional Programming
47mWhirlwind Tour of the Scala Functional Programming Ecosystem
27mFrom Supercomputing to Serving: A Case Study Delivering Cloud Native Foundation Models
53mWhirlwind tour of the Scala Functional Programming ecosystem
26mBuilding A Python Service Using Open Source Components That Connect, Transform & Deliver Data In RT
01h 07mBuilding Reactive Pipelines
53mBuilding Agentic Applications w/ Heroku Managed Inference and Agents
21mHarnessing Microservices for Scalable, Fault-Tolerant ML Systems