Upgrade to Pro — share decks privately, control downloads, hide ads and more …

A_resource_oriented_framework_using_the_DI___AOP___REST_Triangle.pdf

Akihito Koriyama
August 02, 2013
15

 A_resource_oriented_framework_using_the_DI___AOP___REST_Triangle.pdf

Akihito Koriyama

August 02, 2013
Tweet

Transcript

  1. A resource oriented framework using the DI / AOP /

    REST Triangle Version 0.1 (27 July [email protected] meetup #2)
  2. What’s BEAR.Sunday ? (1) • DI / AOP / REST

    centered framework DI AOP REST
  3. DIP • Code should depend on things that are at

    the same or higher level of abstraction • High level policy should not depend on low level details
  4. Object instantiation / usage separation • Don’t mix (compile /

    runtime ) • One time object construction DPNQJMF SVOUJNF
  5. Application object graph by context • Application is single big

    one valuable • Change structure, not behavior $app Object i/f i/f Object i/f i/f Object Router Response JSON XM L
  6. Aspects • log / cache / validation ... are aspects.

    • Core concern is your domain model, not aspects.
  7. API driven development • API is hub • test friendly

    DB API Mobile Web API Cloud Mock URI API
  8. What’s BEAR.Sunday ? (2) • Resource oriented framework • no

    control-object paradigm • information has name
  9. What’s BEAR.Sunday ? (3) • Connecting framework • DI -

    object to object • AOP -business logic to app logic • REST - information to information
  10. Performance • Super fast • cache compiled object • cache

    all objects • http friendly architecture