📖
📖
📖
📖
Dev Docs
Search
⌃K
README
Basic Concepts
Step by Step Tutorial
Billing
Example TApps
Advanced TApps
Functions
Glossary
Actor
Adapter
App AES Key
AuthKey
back_end_actor
Birth Control
Blockchain Listener
Capability
CML Auctions
Commands
Consensus
Context
Conveyor
Conveyor: Mutable vs Immutable
enclave
Followup
Front-end
GlueSQL
GPS
Hosting Actor Handlers
Hosting CML
hosting_profitability
Magic of WASM
mini-runtime
OrbitDb
Order of Txns
party-actor
party-fe
Party-state-actor
Providers
Public Service
queries
Remote Attestation
Staking to Hosting CML
Staking to TApp
State
State Machine
State Machine Actor
State Machine Replica
TEA ID
TPM
Transactions
VMH - Virtual Messaging Hub
Where Messages are Stored
Powered By GitBook

back_end_actor

Using the TEA Party TApp as an example, the party-actor compiles to the actor that runs inside a hosting_cml.
Since it's an actor, it's loaded and runs inside the enclave (also called the mini-runtime).
The only thing that the back-end actor does is handle incoming requests.
This back_end_actor is different than the state_machine_actor which run inside the enclaves of the state machine replicas. Those state machine actors handle the queries and commands that directly interact with the state machine. In traditional web 2.0 applications, these are usually called Stored Procedures that run inside the database server.
Previous
AuthKey
Next
Birth Control
Last modified 6mo ago