Designing a Core Framework for Application Composition and Lifecycle Management

[thejhh]

In order to achieve application compotization and effective lifecycle management, we are developing a TypeScript framework inspired by Java Spring Boot's concept of "Beans."

The primary objective of this framework is to break down application features into small, independent, and easily testable units. It will empower developers to compose these units seamlessly, creating a cohesive and functional product.

To ensure the success of this TypeScript implementation, we need to address the following key features:

1. HgApplication.run(): This method will be responsible for implementing the logic currently hardcoded in the project-specific ./main.ts file.

2. @Application Annotation: By introducing this annotation, developers can define the main class or function for applications. It will be utilized within the HgApplication.run() method.

3. @Component and @Service Annotations: These annotations will allow developers to tag classes, providing optional categorization for better organization and code clarity.

4. @Autowired Annotation: By employing this annotation, parameters, properties, and setters will be automatically wired based on their types. This will simplify dependency injection and improve code modularity. See Autowired annotation #96.

5. @Qualifier Annotation: This annotation will assist in resolving potential type conflicts by allowing developers to specify which type should be selected when multiple options are available.

6. Common Interfaces: We will define standard methods for lifecycle management, such as Disposable, which can be implemented by classes. These interfaces will promote consistency and provide a clear contract for developers.

7. Lifecycle Annotations: In addition to the common interfaces, we will introduce lifecycle annotations like @PreDestroy, enabling developers to define custom methods that adhere to our lifecycle standards.

8. Configurator Feature: This feature will offer dynamic autowire conflict resolution. For example, developers will be able to select the preferred database solution from multiple options, allowing end-users to customize their environment.

For further insights and references, please refer to the following resources:

• Spring Autowire
• Spring Shutdown Callbacks
• DisposableBean Interface

By incorporating these features, our TypeScript framework will facilitate application compotization and streamline the management of application lifecycles.