Resonance PHP Framework

Resonance is optimized for several development scenarios:

• Rapid Prototyping: Quickly validating product hypotheses and features.
• SaaS Development: Creating and scaling Software as a Service applications.
• High-Performance PHP: Building applications that require high performance and memory usage optimization.
• Service Orchestration: Managing cross-service communication and asynchronous task management.
• Codebase Management: Streamlining refactoring through standardized and readable development patterns.
• AI Integration: Integrating applications with open source, self-hosted Large Language Models (LLMs).

Extractors are a feature in Resonance designed to map a user's fuzzy, unstructured input into strictly formatted data or to pull specific data points out of a text block.

Important Compatibility Note: All extractors are tested using Mistral Instruct 7B. If you use a different LLM—particularly smaller models like Phi-2—you may experience inconsistent results or failures in following the required schema.

The AssetFileRegistry provides built-in protection against Path Traversal attacks and optimizes performance through the following mechanisms:

• Path Traversal Mitigation: The registry indexes all files from the directory defined by the DM_PUBLIC_ROOT constant. It only serves files explicitly found in this internal registry. If a requested path is not in the registry, it returns a 404, preventing attackers from accessing files outside the public root.
• Performance: Because the file list is kept in memory, Resonance avoids expensive filesystem checks during every request.
• Optimized Transfer: Once a file is validated, Resonance uses Swoole's $response->sendfile(...) method to transfer the file efficiently.

The Gemma model expects a specific turn-based structure for chat interactions. The template follows this pattern:

<start_of_turn>user
{message}<end_of_turn>

<start_of_turn>user
knock knock<end_of_turn>

Resonance is designed around the principle of Asynchronous PHP, treating PHP not just as a website generator, but as a communication hub between infrastructure services.

Key design goals include:

• Consistent speed of development: Maintaining productivity regardless of project scale.
• Ease of maintenance: Ensuring long-term project health.
• Ease of integration: Facilitating connections with external services.
• Service-oriented architecture: Allowing developers to prototype features in PHP and later replace them with specialized services (written in other languages) via API calls without re-architecting the entire system.

Note that performance and security are treated as baseline requirements rather than distinct features.

routeSymbol is a unique name assigned to a route via the #[RespondsToHttp] attribute. Instead of using raw strings for URLs, Resonance encourages using an enum that implements HttpRouteSymbolInterface.

This approach provides:

1. Consistency validation: Prevents typos in internal links.
2. Bootstrap checks: Allows the framework to verify that all referenced route symbols actually exist during the server bootstrap phase.

Example implementation of a Route Symbol enum:

namespace App;

use Distantmagic//... (imports)

enum HttpRouteSymbol implements HttpRouteSymbolInterface
{
    use CastableEnumTrait;
    use NameableEnumTrait;

    case Homepage;
}