So my job is: Write server-side code as part of my application, targetting some platform API. Once finished, invoke some deployment routine. The service provi

So my job is: Write server-side code as part of my application, targetting some platform API. Once finished, invoke some deployment routine. The service provider's job is: Receive a request from me to deploy my server-side code and keep it running on some server cluster. That's not a serverless applications architecture because the application contains server-side code. If you don't want to call it a deployment strategy, fine, I won't insist on that name, even though in my view using a service provider for deployment deserves to be called a deployment strategy. More generally, it's an approach to make my server-side code run once I'm finished writing it. Call it what you will.