GFS and GAE Architecture, RESTful Architecture

3. The Network Effect Metcalfe's law: Network value rises by the square of the number of terminals. Robert Metcalfe Metcalfe's law characterizes many of the network effects of communication technologies and networks such as the Internet, social networking, and the World Wide Web. http://en.wikipedia.org/wiki/Robert_Metcalfe http://en.wikipedia.org/wiki/Metcalfe's_law

4. Google App Engine Architecture GAE SDK IDE Your GAE Application Python / Java Framework Admin Console Blobstore Capabilities Channel URL Fetch Images Mail Memcache Users Multitenancy OAuth Task Queues XMPP Google App Engine Runtime (Python, Java, GO) Google App Engine DataStore BigTable Google File System Google Server Cluster

5. Google File System GFS is optimized for Google's core data storage and usage needs (primarily the search engine), which can generate enormous amounts of data that needs to be retained; Google File System grew out of an earlier Google effort, "BigFiles", developed by Larry Page and Sergey Brin in the early days of Google, while it was still located in Stanford. Files are divided into chunks of 64 megabytes, which are only extremely rarely overwritten, or shrunk; files are usually appended to or read. It is also designed and optimized to run on Google's computing clusters, dense nodes which consist of cheap, "commodity" computers, which means precautions must be taken against the high failure rate of individual nodes and the subsequent data loss. Other design decisions select for high data throughputs, even when it comes at the cost of latency. http://labs.google.com/papers/gfs.html

6. File A (80M) Google File System Architecture Chunk Data #1 (64M) Chunk Data #2 (16M)

8. GAE SDK 1.5.1

9. JDK 1.6

10. EJB와 같은 JavaEE관련 기술을 모두 지원하지 않음.

11. Thread 생성을 지원하지 않음.

12. Servlet(JSP)

14. http://java.sun.com/javase/downloads/index.jsp

15. Google Web Toolkit

16. http://code.google.com/intl/ko-KR/webtoolkit/

17. Eclipse IDE

18. http://www.eclipse.org/downloads/

19. Google Plugin for Eclipse, for Eclipse 3.6 (Helios)

20. http://dl.google.com/eclipse/plugin/3.6GAE for Java 개발 환경

22. HTTP Session support (need to enable explicitly)

23. JRuby (Ruby)

24. Jython (Python)

25. Quercus (PHP)

26. Rhino (JavaScript)

27. Spring Framework**: JSF 1.2 and JSF 2.0 should also work if you set the com.sun.faces.enableMultiThreadedStartup context parameter to false to your web.xml file. *** JSP session beans are not supported; to enable EL parsing, add <%@page isElIgnored="false" %> to your JSP. http://groups.google.com/group/google-appengine-java/web/will-it-play-in-app-engine

29. Apache POI

30. ICEFaces

31. Hibernate보안 ‘sandbox’ 환경에서 구동 - 쓰레드를 독자적으로 실행할 수 없음 - 로컬 파일 시스템에 접근할 수 없음 - Socket 오픈 할 수 없음 http://groups.google.com/group/google-appengine-java/web/will-it-play-in-app-engine

32. JSR을 중심으로 다음과 같은 표준 기술을 지원한다. GAE for Java의 기술 표준

33. RESTful Architecture Representational State Transfer (REST) is a style of software architecture for distributed hypermedia systems such as the World Wide Web. The term Representational State Transfer was introduced and defined in 2000 by Roy Fielding in his doctoral dissertation.

34. RESTful Architecture Constraints Client–server Clients are separated from servers by a uniform interface. Stateless The client–server communication is further constrained by no client context being stored on the server between requests. Each request from any client contains all of the information necessary to service the request, and any session state is held in the client. Cacheable As on the World Wide Web, clients are able to cache responses. Layered system A client cannot ordinarily tell whether it is connected directly to the end server, or to an intermediary along the way. Code on demand (optional) Servers are able to temporarily extend or customize the functionality of a client by transferring logic to it that it can execute. Uniform interface The uniform interface between clients and servers, discussed below, simplifies and decouples the architecture, which enables each part to evolve independently.

35. RESTful Web Service ITEM 0001 POST /item/0001 GET /item/0001 PUT /item/0001/01 DELETE /item/0001/

36. RESTful Web Service Design Data Store (BigTable) Jersey Or Spring REST Spring Component (Bean) JDO (PMF)

37. Demo

39. Jersey is the open source, production quality, JAX-RS (JSR 311) Reference Implementation for building RESTful Web services.

40. But, it is also more than the Reference Implementation. Jersey provides an API so that developers may extend Jersey to suit their needs.http://jersey.java.net/ http://simple.sourceforge.net/

42. 여기서 이들은 개방형시스템(Open System)의 독점적 아키텍처(Proprietary Architecture)가 경쟁에서 승리하는데 가장 중요한 요소라고 이야기 하였습니다. Service Service SaaS Service 독점적인 서비스 아키텍처 Proprietary Service Architecture Scalability New Service Service 서비스 기반의 개방형 시스템 Service Based Open System Service Service Service Service Service Service Service Service Configurable Multi-tenant efficient Jang, Sun-Jin (jangsunjin@softwareinlife.com)

43. 감사합니다. http://code.google.com/p/devmento-gae-seminar