1. Robert Lyon  Design Review  November 11, 2011

2. Transitionary Time

4. Filebucket

6. Smoke

7. Not quite the cloud But works the same way

8. Simple Storage Service (S3)

9. Ruby Rack

10. Buckets No folders!

11. Objects / Keys path/to/my/file.txt

12. Use the same tools to access data stored on standard file systems as you do for the cloud.

13. Request received by the Proxy Server

14. REST

15. GET, PUT, DELETE, POST Index, Show, Edit, Update, New, Create and Destroy

16. PUT /bucket/file.txt HTTP/1.0 Content-Md5: c8fdb181845a4ca6b8fec737b3581d76 Content-Type: text/plain Content-Length: 1024 Date: Thu, 17 Nov 2005 18:49:58 GMT X-Amz-Meta-Author: foo@bar.com X-Amz-Magic: abracadabra …. Body ….

17. Authentication Proxy Auth

18. Signed request based on access ID and secret key.

19. Authorization: AWS 44CF9590006BF252F707:5m+HAmc5JsrgyDelh9+a2dNrzN8=

20. Action Proxy Auth Parse Action GET PUT DELETE POST Also HEAD

21. Retrieve Information Proxy Auth Parse Action Get Data

22. Backing Database PostgreSQLVolatile MemoryMySQLSQLite

23. Generate Response Proxy Auth Parse Action Get Data Respond

24. Generate Response Proxy Auth Parse Action Get Data Respond

25. Why not build this directly into filebucket?

26. Scalability Flexibility Transitional Bridge Long Term Goals

27. Phase 1

28. Location Infrastructure Versioning ACLs Remote Clients Filebucket Integration

29. Why not other faux S3 implementations?

30. Why S3?

31. Identified Issues DNS Style Buckets Many Different Request Styles

32. Direct Cost: $0 Indirect Cost: $10,000 ~400 personnel hours required

33. December 14 th Phase 1 Completed