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

Class 12: Web Frameworks, APIs, and Conclusion

Class 12: Web Frameworks, APIs, and Conclusion

Notes for 8/1/2013

Ian Luke Kane

August 01, 2013
Tweet

More Decks by Ian Luke Kane

Other Decks in Technology

Transcript

  1. Web  Applica+on  Frameworks Designed  to  support  the  development  of  dynamic

      websites,  web  applica9ons,  web  services  and  web   resources. Aims  to  alleviate  the  overhead  associated  with  common   ac9vi9es  performed  in  web  development.   Gathering  libraries  for  database  access,  caching,  and   session  management  (plus  more),  and  they  o>en   promote  code  reuse.
  2. Framework  Feature  Examples Caching The  caching  of  web  documents  in

     order  to  reduce  bandwidth   usage,  server  load,  and  perceived  "lag".   Security Authen9ca9on  and  authoriza9on,  enabling  the  web  server  to   iden9fy  the  users  of  the  applica9on,  and  restrict  access  to   func9ons  based  on  some  defined  criteria.   Database  Access Many  web  applica9on  frameworks  create  a  unified  API  to  a   database  backend,  enabling  web  applica9ons  to  work  with  a   variety  of  databases  with  no  code  changes,  and  allowing   programmers  to  work  with  higher-­‐level  concepts.   Form  Valida9on
  3. Frameworks  and  MVC A  so>ware  architecture  paRern  which  separates  the

      representa9on  of  informa9on  from  the  user's   interac9on  with  it.   The  model  consists  of  applica9on  data,  business  rules,   logic,  and  func9ons.   A  view  can  be  any  output  representa9on  of  data,  such   as  a  chart  or  a  diagram.   The  controller  mediates  input,  conver9ng  it  to   commands  for  the  model  or  view.
  4. Applica+on  Programming  Interface In  prac9ce,  most  o>en  an  API  is

     a  library  that  includes   specifica9ons  for  rou9nes,  data  structures,  object   classes,  and  variables.   Sound  familiar? Dronestagram TwiRer  API Pinterest  API?  Not  Yet.
  5. Final  Thoughts The  Computer HTML CSS Git  /  Source  Control

    Cathedral  and  the  Bazaar The  Magic  Cauldron Homesteading  the  Noosphere Javascript jQuery Databases APIs N-­‐Tier  Architecture So>ware  Licenses Development  Methodologies LAMP Language  Overview Procedural  Programming Object  Oriented  Programming Responsive  Design UI/UX
  6. Final  Thoughts:  Next  Steps What  do  you  want? What  technologies

     interest  you? What  person  resources  do  you  have? What  web  resources  do  you  have? Prac9ce,  prac9ce,  prac9ce.