Work
Client work is under NDA, so the case studies describe the problem, the approach and the outcome without naming the client. The interactive example shows the kind of system I design.
How a data pipeline copes
Data arrives from many sources, waits in a queue, is normalised into one model, then stored and served. Use the controls to put it under pressure.
Scroll sideways to see the whole flow.
Example sources
- HTTPAPIs and webhooks
- MQTTDevices and sensors
- IBM MQEnterprise message queues
- SMTPEmail-based feeds
Files, databases and other feeds join the same way.
- Queued
- 0 / 12
- Normalised
- 0
- Dropped
- 0
- Reads from cache
- 0%
- Incoming message (shape by source)
- Normalised record
- Read served to a consumer
Illustrative simulation. Not a client or employer system.
Case studies
- RH-02.1Designing a resilient service architecture
[Fixture] A target architecture that let a growing product survive the loss of a zone without downtime.
- RH-02.2Planning a multi-system cloud migration
[Fixture] Architecture and delivery plan for moving several interdependent systems to the cloud without a big-bang cutover.
- RH-02.3Infrastructure security audit
[Fixture] A review of an existing cloud estate for vulnerabilities, with a prioritised plan to fix them.