plba/requirements/vision.md

Vision

Product vision

PLBA should be a transparent runtime for business applications.

The desired feeling of the platform:

• simple to read
• explicit in behavior
• small number of core concepts
• easy to debug
• no architectural legacy artifacts

Core concepts

The platform should be understandable through three ideas:

• ApplicationModule assembles the app
• Worker owns lifecycle and execution
• business behavior lives in application routines and services

Non-goals

PLBA should not become:

• a framework of many specialized runtime roles
• a queue-centric architecture by default
• a compatibility shell for legacy abstractions
• a place where business logic hides inside infrastructure classes

Utility components

Some utility components may still exist, for example InMemoryTaskQueue.

They are acceptable when they stay:

• optional
• local
• implementation-oriented

They should not redefine the main platform model.