Is there a better term to use to describe the concept of programming a service with short-lived executable blocks? Function-as-a-Service (FaaS) comes to mind, a

Is there a better term to use to describe the concept of programming a service with short-lived executable blocks? Function-as-a-Service (FaaS) comes to mind, although to me that implies a third party host. What's kind of funny is old web servers used to work almost exactly this way, running a program in isolation for every incoming request (CGI scripts anyone?), but that was well before the rise of REST and intentionally stateless development, so it didn't get a buzzword. We've come full circle.