• DocumentCode
    2533758
  • Title

    Persistent middle tier components without logging

  • Author

    Lomet, David

  • Author_Institution
    Microsoft Res., Redmond, WA, USA
  • fYear
    2005
  • fDate
    25-27 July 2005
  • Firstpage
    37
  • Lastpage
    46
  • Abstract
    Enterprise applications need to be highly available and scalable. In the past, this has required "stateless" applications, which essentially require the application to manage its state explicitly by storing it in transactional resource managers. Despite "stateful" applications being more natural and hence easier to write and get correct, having the system manage this state automatically has been considered too difficult and too costly. The Phoenix/App system showed how to manage state in stateful applications transparently, by logging interactions between components, guaranteeing "exactly once" execution of the application. By introducing some minor restrictions on Phoenix/App components, no logging need be done for middle tier components, thus making it easy to provide both availability and scalability. Because there is no logging, the performance of failure free application executions is excellent.
  • Keywords
    commerce; middleware; object-oriented programming; Phoenix/App system; enterprise applications; persistent middle tier components; stateful applications; transactional resource managers; Application software; Availability; Computer crashes; Costs; Data engineering; Databases; Logic programming; Robustness; Scalability; Writing;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Database Engineering and Application Symposium, 2005. IDEAS 2005. 9th International
  • ISSN
    1098-8068
  • Print_ISBN
    0-7695-2404-4
  • Type

    conf

  • DOI
    10.1109/IDEAS.2005.43
  • Filename
    1540893