A shorter path from code to running.
Defining a simpler deployment path for OCI Functions, with clear responsibilities for the platform and the developer.
The problem
Developers arriving from other serverless platforms expected to upload code and run it. The existing container workflow asked them to handle packaging, image builds, registry setup, and runtime maintenance before they reached that first success.
My contribution
Brought customer and field feedback into a product definition for code-only deployment and authored the requirements.
Worked with engineering and design on the responsibility split: the platform manages the supported runtime; developers keep control of their code, dependencies, and testing.
Worked through runtime updates, version control, and the developer experience across existing tools. Planned staged customer validation and helped prepare the launch.
The decisions
A managed runtime reduces setup work, but enterprise teams still need to test updates and decide when to adopt them. The design had to make both responsibilities clear.
The simpler path also needed to fit existing release workflows while preserving the container option for workloads that need more control.
Where it landed
Code-only deployment became publicly available in September 2026. I authored the launch article explaining the experience and its tradeoffs.
The release gives developers a simpler deployment option. Its effect on adoption and broader platform growth has not been established in this case study.