APIs, IoT & DevOps
Secure APIs, connected devices and the servers that keep them running.
Backends that stay up
REST APIs, IoT integrations and deploy pipelines for systems that have to keep running.
Behind every app is a backend that has to be secure, fast and boring in the best way. I design REST APIs, connect IoT devices to them, and set up the servers and pipelines that run it all.
I containerise with Docker, automate releases with GitHub Actions, administer Linux servers over SSH and add caching with Redis where response times matter.
Skills & tools
What a APIs, IoT & DevOps project draws on
API Development
Secure, documented endpoints.
IoT
Devices that report in.
DevOps & Servers
Deployed, repeatable, monitored.
Performance
Fast under load.
How I
work
A look at how a typical APIs, IoT & DevOps project comes together
01
Design
I agree the API contract, the data model and the security rules with the teams that use them before the first endpoint exists.
Outcomes
- API contract
- Data model
- Security checklist
02
Build & Integrate
Endpoints are built and tested one by one, and devices are connected against the real API, not a mock.
Outcomes
- Tested endpoints
- Device integration
- Postman collection
03
Deploy & Operate
Containers, a pipeline that deploys on every merge and a server that is set up to be maintained by someone else.
Outcomes
- Docker images
- CI/CD pipeline
- Server runbook
Related Work
Yes. At Makerindo I deployed ML models as FastAPI services integrated with IoT devices, used by the web and mobile teams.
Yes. I have containerised apps with Docker, set up GitHub Actions pipelines and administered Linux servers over SSH.
Every endpoint I built at Makerindo was tested with Postman before the web and mobile teams consumed it.
Common Questions
Answers to what people ask most about APIs, IoT & DevOps
Need help with your project?
Let’s work together!