Requestor allows users to create an account, create groups, add other users to these groups, post tickets in their groups, manage roles in their groups, and manage tickets in their groups. The main idea here was, of course, for the entire program to be server-less, only using AWS services. With this in mind it would have been very easy to implement the entire system just saving groups and ticket info in a DynamoDB database and constantly querying or updating those entries through an Api Gateway. I wanted the design for this to instead be more ticket focused. A ticket's info is valuable and relevant up until it has been archived. I decided to mirror the life of a ticket using a state machine through AWS Step Functions. Each group created on Requestr would still be saved in a DynamoDB database, but each group would then have a corresponding state machine that each ticket made in that group would run on. Each ticket's info is stored only within whatever state it is currently on in the state machine and eventually when a ticket is archived, its execution in the state machine is terminated.  In summary, groups created on Requestr are saved to a DynamoDB database while ticket's entire lifecycle is represented as executions of a state machine. The State Machine built through AWS Step Functions can be found in the system architecture diagram below.