# Durable - Serverless Temporal

**URL:** <https://community.temporal.io/t/durable-serverless-temporal/10849>\
**Category:** Show & Tell\
**Created:** [January 30, 2024, 9:57am UTC](https://community.temporal.io/t/durable-serverless-temporal/10849 "2024-01-30T09:57:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![danzilberdan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/danzilberdan/32/4690_2.png) [@danzilberdan](https://community.temporal.io/u/danzilberdan)\
**Post date:** [January 30, 2024, 9:57am UTC](https://community.temporal.io/t/durable-serverless-temporal/10849/1 "2024-01-30T09:57:33Z")

</div>

Deploy Durable Workflows using Serverless Compute.

- **Durable Execution** - Get all the benefits of Temporal
- **Serverless** - Deploy faster without the need to maintain servers
- **Cost** - Pay-per-use model. Idle long-running functions incur no compute costs

Check it out [here](https://github.com/danzilberdan/Durable-Serverless-Starter) 🙂

---

<div class="post-metadata">

**Author:** ![Chad\_Retz](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/chad_retz/32/1396_2.png) [@Chad\_Retz](https://community.temporal.io/u/Chad_Retz)\
**Post date:** [January 30, 2024, 8:21pm UTC](https://community.temporal.io/t/durable-serverless-temporal/10849/2 "2024-01-30T20:21:56Z")

</div>

Neat! I read some of the code at [pydurable · PyPI](https://pypi.org/project/pydurable/) (is it available in source form anywhere?). One thing I couldn’t find, what triggers the serverless code to run/scale when there is work to do?

---

<div class="post-metadata">

**Author:** ![danzilberdan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/danzilberdan/32/4690_2.png) [@danzilberdan](https://community.temporal.io/u/danzilberdan)\
**Post date:** [January 30, 2024, 9:02pm UTC](https://community.temporal.io/t/durable-serverless-temporal/10849/3 "2024-01-30T21:02:14Z")

</div>

Thanks!

I actually created a service that invokes the Lambda functions on the user’s behalf. Will work more on the documentation and the accessibility of the project.  
Will love some feedback as well.

Dan
