topless 0.1.0

Tailored OPerations for serverLESS

Action Execution Model

The Topless actionexecution model is processed in two different steps:

1. Action Handler Registration Every action created with one of the provided decorators (route, schedule, bucket or topic) is registered on the main Topless app instance. The instance is created on the client side (main.py file), and is shared throghouth the framework modules by a singleton pattern.

Flow of execution:

sequenceDiagram
    box Client
    participant C1 as bootstrap.py
    participant C2 as main.py
    end

    box Core
    participant T1 as bootstrap.py
    participant T2 as app.py
    participant T3 as handler.py
    end


    C1->>C2: Import main.py
    C2-->>C1: Topless instance and registrations
    C1->>T1: Start framework bootstrap
    T1->>T2: Load all modules
    T2->>T3: Map action handlers
    T1-->>C1: Finish setup
    

2. Action Handler Execution When lambda is called, the client bootstrap.py handle method is executed. Every lambda resource on the template.yaml (dinamically generated by topless framework), will call this method at first, which will dispatch the bootstrap.handle method, to localize the action handler that is needed on that call.

sequenceDiagram
    participant L as Lambda Event
    participant CA as app.py (Client)
    participant CB as bootstrap.py (Client)
    participant TA as app.py (Core)
    participant TB as bootstrap.py (Core)
    participant TD as dispatcher.py (Core)
    participant TH as handler.py (Core)

    L->>CB: Trigger Lambda Function
    CB->>TB: Call framework bootstrap handler
    TB->>TD: Execute Dispatcher
    TD-->>TB: Construct action envelope and look for the correct action to be executed