temporalio / temporalio/temporal
Support for in memory db and setup for running temporal with limited resources
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
My organization has a use case (IoT, Edge) where We need our app to be reliable running under limited resources (hardware with limited capacity, for instance: CPU with 2 cores and 2 Gb ram). We consider temporal as the right choice, to build our apps, however, we realized that the current default setup of temporal might need adjustments, documentation on how to run properly under such scenarios. Also, we consider that perhaps an in-memory DB along with simple binary (temporal) would be a better choice for executing workflows with good throughput. After discussing with Wenquan Xing, this looks feasible.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing Temporal's current default setup and the stated feasibility of an in-memory database with a simple Temporal binary for limited-resource hardware. Done requires a defined implementation or documentation scope for that deployment scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100