This set builds vocabulary for git-driven platform-as-a-service deployment concepts.
0 / 5 completed
1 / 5
At standup, a dev describes a cloud platform where pushing to a connected git branch automatically builds and deploys a web service with minimal manual configuration. Which type of platform fits?
A platform-as-a-service like Render connects directly to a git repository and automatically builds and deploys a service on each push, abstracting away manual server provisioning and deployment scripting. This lowers the operational overhead compared to configuring infrastructure by hand. It targets teams who want to focus on application code rather than server management.
2 / 5
During a design review, the team wants a background worker process that runs continuously without serving HTTP traffic, separate from their web service. Which concept fits?
A background worker service type runs continuously to process jobs, like a queue consumer, without exposing an HTTP endpoint, distinct from a web service that handles incoming requests. Platforms like Render let both service types be defined and deployed from the same repository. Separating concerns this way keeps request-serving and background processing independently scalable.
3 / 5
In a code review, a dev configures a managed database instance provisioned and maintained by the platform rather than self-hosted on a separate server. What is this called?
A managed database service handles provisioning, backups, and maintenance on behalf of the team, reducing the operational burden compared to self-hosting and administering a database server directly. This tradeoff favors convenience and reduced ops work over the finer control a self-managed instance offers. Most modern PaaS platforms offer this as a companion to their compute services.
4 / 5
An incident report shows a service experienced a cold start delay after scaling to zero during low traffic, causing a slow first request. What tradeoff does this reflect?
Scaling a service down to zero instances during idle periods saves cost, but the next incoming request triggers a cold start, incurring extra latency while a new instance spins up. Teams with strict latency requirements often configure a minimum instance count to avoid this tradeoff. Understanding this behavior helps in deciding when scale-to-zero is appropriate versus keeping a warm instance running.
5 / 5
During a PR review, a teammate asks how a PaaS like Render differs from manually provisioning a virtual machine and configuring a web server. What is the key distinction?
Manually provisioning a virtual machine requires configuring the OS, web server, and deployment process by hand, while a PaaS automates build and deployment directly from a git push, trading some low-level control for significantly less operational overhead. This tradeoff suits teams that want to move fast without dedicated infrastructure expertise. The choice depends on how much control versus convenience a project needs.