Clack: glue for web apps
1 like2,486 views
Clack is an abstraction layer for Common Lisp web applications that allows applications to run on different web servers. It provides composability through a middleware layer. Clack has evolved over time from an early stage of limited installation options and abandoned projects to the current age where it has reached version 1.0, is well tested and used as the foundation for many frameworks. The developer hopes more people will now build web applications using the mature Clack ecosystem.
Clack: glue for web apps
- 1. Clack: glue for web apps Clack Meetup #1 Eitaro Fukamachi
- 2. Thank you for coming.
- 3. I’m Eitaro Fukamachi @nitro_idiot fukamachi
- 4. Topics • What’s Clack? • As an Abstraction Layer • As a composable rule • History
- 5. Clack
- 6. • Web application environment • Intended to be a basement of frameworks • Abstracts web servers • Composability Clack
- 7. Clack (clackup (lambda (env) ‘(200 (:content-type “text/plain”) (“Hello, World”))) :server :hunchentoot)
- 8. Clack (clackup (lambda (env) ‘(200 (:content-type “text/plain”) (“Hello, World”))) :server :hunchentoot) Application
- 9. Clack (clackup (lambda (env) ‘(200 (:content-type “text/plain”) (“Hello, World”))) :server :hunchentoot) Application Web server to run the application on
- 10. Web server Abstract web servers Application Web server Web server Application Application
- 11. Web server Abstract web servers Application Web server Web server Application Application Clack
- 14. • Middleware wraps an application • Middleware can be reused • ex) access log, session manager “Middleware”
- 15. History
- 16. We lived 4 ages.
- 17. • asdf-install or clbuild (not reliable) • GitHub wasn’t popular • Posted a bug to mailing-lists • Many projects are abandoned or inactive • We couldn’t tell if a library works with other libraries BQ (Before Quicklisp = the Stone Age)
- 18. • Quicklisp made installation of libraries really easier • It make sure libraries can load at least AQ (the Tool Age)
- 19. • Hosted on GitHub • Has many tests • Tested on Jenkins • Has a documentation Clack was out 4 years ago
- 20. • We had Clack & Caveman1 • We had Quicklisp • No DBI, No ORM (CLSQL was terrible) • Many projects were abandoned • Clojure already had Ring Clack (the Bronze Age)
- 21. • Hunchentoot, Weblocks, web4r, RESTAS • Most WAF were built on top of Hunchentoot!! • Is Hunchentoot reliable and everlasting? Clack (the Bronze Age)
- 22. The Present Age • We have ningle and Caveman2 • We have CL-DBI, SxQL, datafly and Integral • We have Woo, a really fast web server • We have CIM/Roswell and qlot • Clack reached ver 1.0
- 23. • Moved many codes to an individual project • Could reduce 1583 lines • Made it stable • Made it faster • Started testing on Clack v1.0
- 24. So, what’s next?
- 25. • We have everything we need to build a web application • Just try. • Looking for a Common Lisp job? We’re hiring! The next move
- 26. Thanks.