Ticket #57 (closed enhancement: fixed)

Opened 4 years ago

Last modified 2 years ago

Codify application infrastructure best practices/usage patterns

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

Description (last modified by MartinLeidig) (diff)

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

Changed 4 years ago by MartinLeidig

  • description modified (diff)

Changed 4 years ago by MartinLeidig

  • description modified (diff)

Changed 2 years ago by MartinLeidig

  • status changed from new to closed
  • resolution set to fixed

these kind of best practices are or should be implemented on the Spring/OSGi layer and Pustefix already seamlessly integrates with Spring/OSGi

Note: See TracTickets for help on using tickets.