Ticket #57 (new enhancement)

Opened 6 months ago

Last modified 6 months ago

Codify application infrastructure best practices/usage patterns

Reported by: MartinLeidig Assigned to: MartinLeidig
Priority: major Milestone: 1.0.0
Component: Core (general) Version:
Keywords: requirements_paper_20080521 Cc:

Description (Last modified by MartinLeidig)

Similar to the Spring framework Pustefix should take the best practices and design patterns that have been proven over the years and codify/integrate them. Here's a list of common problems, which could be supported by the framework:

  • Lazy initialization: loading data from observed ContextResources, backend services databases on demand, e.g. declarable with annotations
  • Asynchronous backend calls and client notifications
  • Parallel backend calls
  • Transaction handling support for distributed service calls (e.g. compensation function triggering, rollback, etc.)
  • Messaging mechanism for inter-component communication

Change History

07/16/08 15:50:29 changed by MartinLeidig

  • description changed.

07/16/08 16:01:07 changed by MartinLeidig

  • description changed.