Haskell on PaaS

BFPG lightning talk about the state of Haskell on Platform as a Service (PaaS) offerings.

Transcript

1. Haskell on PaaS Fraser Tweedale September 23, 2014
2. Disclosure I work for Red Hat. Red Hat is a PaaS provider (OpenShift Online).
3. What is PaaS? Platform as a Service
4. What is PaaS? Platform as a Service Software execution environment
5. What is PaaS? Platform as a Service Software execution environment Don’t think about hardware / OS
6. What is PaaS? Platform as a Service Software execution environment Don’t think about hardware / OS Don’t think (much) about network
7. What is PaaS? Platform as a Service Software execution environment Don’t think about hardware / OS Don’t think (much) about network DNS handled for you
8. What is PaaS? Platform as a Service Software execution environment Don’t think about hardware / OS Don’t think (much) about network DNS handled for you SSL/TLS termination
9. What is PaaS? Platform as a Service Software execution environment Don’t think about hardware / OS Don’t think (much) about network DNS handled for you SSL/TLS termination Auto-scaling (depending on provider/platform)
10. What is PaaS? Platform as a Service Software execution environment Don’t think about hardware / OS Don’t think (much) about network DNS handled for you SSL/TLS termination Auto-scaling (depending on provider/platform) dev/stage/prod environments are easy
11. Who is PaaS? OpenShift (Red Hat) †‡
12. Who is PaaS? OpenShift (Red Hat) †‡ Heroku †
13. Who is PaaS? OpenShift (Red Hat) †‡ Heroku † Cloud Foundry (Pivotal) ‡
14. Who is PaaS? OpenShift (Red Hat) †‡ Heroku † Cloud Foundry (Pivotal) ‡ FP Haskell Centre (FP Complete) ‡
15. Who is PaaS? OpenShift (Red Hat) †‡ Heroku † Cloud Foundry (Pivotal) ‡ FP Haskell Centre (FP Complete) ‡ . . . various others.
16. Who is PaaS? OpenShift (Red Hat) †‡ Heroku † Cloud Foundry (Pivotal) ‡ FP Haskell Centre (FP Complete) ‡ . . . various others. † free tier available
17. Who is PaaS? OpenShift (Red Hat) †‡ Heroku † Cloud Foundry (Pivotal) ‡ FP Haskell Centre (FP Complete) ‡ . . . various others. † free tier available ‡ runs on free software i.e. you can run an instance yourself
18. Haskell on OpenShift Supported via “community cartridges”
19. Haskell on OpenShift Supported via “community cartridges” GHC 7.8
20. Haskell on OpenShift Supported via “community cartridges” GHC 7.8 Variants for major frameworks (Snap, Yesod, scotty, HappStack)
21. Haskell on OpenShift Supported via “community cartridges” GHC 7.8 Variants for major frameworks (Snap, Yesod, scotty, HappStack) Manifest URLs: http://www.haskell.org/haskellwiki/Web/Cloud
22. Haskell on OpenShift Supported via “community cartridges” GHC 7.8 Variants for major frameworks (Snap, Yesod, scotty, HappStack) Manifest URLs: http://www.haskell.org/haskellwiki/Web/Cloud Currently a bit broken (I have submitted a PR to fix)
23. Haskell on OpenShift Supported via “community cartridges” GHC 7.8 Variants for major frameworks (Snap, Yesod, scotty, HappStack) Manifest URLs: http://www.haskell.org/haskellwiki/Web/Cloud Currently a bit broken (I have submitted a PR to fix) Manage using rhc command-line tool.
24. Haskell on OpenShift % rhc app create parks \ http://www.accursoft.com/cartridges/snap.yml \ postgresql-8.4 \ --from-code https://github.com/bfpg/brisparks.info.git
25. Haskell on Heroku Supported via “buildpack”.
26. Haskell on Heroku Supported via “buildpack”. https://github.com/begriffs/heroku-buildpack-ghc
27. Haskell on Heroku Supported via “buildpack”. https://github.com/begriffs/heroku-buildpack-ghc Manage using heroku command line tool.
28. Haskell on Heroku Supported via “buildpack”. https://github.com/begriffs/heroku-buildpack-ghc Manage using heroku command line tool. Cloud Foundry appears to be similar, but I haven’t tried it yet.
29. Haskell on Heroku % echo ’web: cabal run -- -p $PORT’ > Procfile % git add Procfile ; git commit -m ’add Procfile’ % heroku create --stack=cedar \ --buildpack \ https://github.com/begriffs/heroku-buildpack-ghc.git % git push heroku master
30. Haskell on FP Application Server The only Haskell-centric PaaS (that I know of).
31. Haskell on FP Application Server The only Haskell-centric PaaS (that I know of). So it might be nice. . . ?
32. Haskell on FP Application Server The only Haskell-centric PaaS (that I know of). So it might be nice. . . ? There is no free tier. #sadface
33. Haskell on FP Application Server The only Haskell-centric PaaS (that I know of). So it might be nice. . . ? There is no free tier. #sadface Haven’t tried it. . .
34. Haskell on FP Application Server The only Haskell-centric PaaS (that I know of). So it might be nice. . . ? There is no free tier. #sadface Haven’t tried it. . . but I would love to hear about your experiences if you have/do!
35. Configuring apps for PaaS Most PaaS provide app configuration through env vars.
36. Configuring apps for PaaS Most PaaS provide app configuration through env vars. Differences between providers.
37. Configuring apps for PaaS Most PaaS provide app configuration through env vars. Differences between providers. More services (databases, metrics, etc) = more config.
38. Configuring apps for PaaS Most PaaS provide app configuration through env vars. Differences between providers. More services (databases, metrics, etc) = more config. I’m chipping away on a small library to abstract (some of) this.
39. Configuring apps for PaaS Most PaaS provide app configuration through env vars. Differences between providers. More services (databases, metrics, etc) = more config. I’m chipping away on a small library to abstract (some of) this. Deployment:
40. Configuring apps for PaaS Most PaaS provide app configuration through env vars. Differences between providers. More services (databases, metrics, etc) = more config. I’m chipping away on a small library to abstract (some of) this. Deployment: Some PaaS run your app according to some convention (e.g. OpenShift)
41. Configuring apps for PaaS Most PaaS provide app configuration through env vars. Differences between providers. More services (databases, metrics, etc) = more config. I’m chipping away on a small library to abstract (some of) this. Deployment: Some PaaS run your app according to some convention (e.g. OpenShift) Some PaaS require you to tell it how to run your app (e.g. Heroku, via Procfile)
42. Pain points Cabal hell.
43. Pain points Cabal hell. Low disk space
44. Pain points Cabal hell. Low disk space GHC + Haskell frameworks take up several hundred MB.
45. Pain points Cabal hell. Low disk space GHC + Haskell frameworks take up several hundred MB. I have done some work on OpenShift cartridges to improve the situation.
46. Pain points Cabal hell. Low disk space GHC + Haskell frameworks take up several hundred MB. I have done some work on OpenShift cartridges to improve the situation. I have some more ideas.
47. Pain points Cabal hell. Low disk space GHC + Haskell frameworks take up several hundred MB. I have done some work on OpenShift cartridges to improve the situation. I have some more ideas. Pay $$$ for more disk.
48. Pain points Cabal hell. Low disk space GHC + Haskell frameworks take up several hundred MB. I have done some work on OpenShift cartridges to improve the situation. I have some more ideas. Pay $$$ for more disk. Low memory
49. Pain points Cabal hell. Low disk space GHC + Haskell frameworks take up several hundred MB. I have done some work on OpenShift cartridges to improve the situation. I have some more ideas. Pay $$$ for more disk. Low memory e.g. can’t build haskell-src-exts on small OpenShift gear
50. Pain points Cabal hell. Low disk space GHC + Haskell frameworks take up several hundred MB. I have done some work on OpenShift cartridges to improve the situation. I have some more ideas. Pay $$$ for more disk. Low memory e.g. can’t build haskell-src-exts on small OpenShift gear Solution: ship more cartridge variants with more libs?
51. Pain points Cabal hell. Low disk space GHC + Haskell frameworks take up several hundred MB. I have done some work on OpenShift cartridges to improve the situation. I have some more ideas. Pay $$$ for more disk. Low memory e.g. can’t build haskell-src-exts on small OpenShift gear Solution: ship more cartridge variants with more libs? Pay $$$ for more memory.
52. Future Stackage
53. Future Stackage Infrastructure to create stable builds of complete package sets.
54. Future Stackage Infrastructure to create stable builds of complete package sets. OpenShift cartridges might support Stackage soon.
55. Future Stackage Infrastructure to create stable builds of complete package sets. OpenShift cartridges might support Stackage soon. Docker
56. Future Stackage Infrastructure to create stable builds of complete package sets. OpenShift cartridges might support Stackage soon. Docker Easier to set up container images.
57. Future Stackage Infrastructure to create stable builds of complete package sets. OpenShift cartridges might support Stackage soon. Docker Easier to set up container images. Layered images = shared base images, smaller framework/app images.
58. Future Stackage Infrastructure to create stable builds of complete package sets. OpenShift cartridges might support Stackage soon. Docker Easier to set up container images. Layered images = shared base images, smaller framework/app images. Lots of Docker hosting providers already.
59. Future Stackage Infrastructure to create stable builds of complete package sets. OpenShift cartridges might support Stackage soon. Docker Easier to set up container images. Layered images = shared base images, smaller framework/app images. Lots of Docker hosting providers already. OpenShift v3 is embracing Docker.
60. Future Stackage Infrastructure to create stable builds of complete package sets. OpenShift cartridges might support Stackage soon. Docker Easier to set up container images. Layered images = shared base images, smaller framework/app images. Lots of Docker hosting providers already. OpenShift v3 is embracing Docker. First-class support for Haskell in popular PaaS providers?
61. Future Stackage Infrastructure to create stable builds of complete package sets. OpenShift cartridges might support Stackage soon. Docker Easier to set up container images. Layered images = shared base images, smaller framework/app images. Lots of Docker hosting providers already. OpenShift v3 is embracing Docker. First-class support for Haskell in popular PaaS providers? Hopefully! FP Complete seem to be on their own, for now.
62. Summary PaaS is cool. Go play. Help make Haskell on PaaS a better experience. Talk to me or Katie for ideas.
63. Resources PaaS info on HaskellWiki: http://www.haskell.org/haskellwiki/Web/Cloud OpenShift Online: https://www.openshift.com/ Haskell on OpenShift blog post by Kate Miller: http://is.gd/7eRZDY OpenShift cartridge development: https://github.com/accursoft/Haskell-Cloud Heroku: https://www.heroku.com/ Heroku buildpack development: https://github.com/begriffs/heroku-buildpack-ghc Keter: https://github.com/snoyberg/keter
64. Thanks for listening Copyright 2014 Fraser Tweedale This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/. Slides https://github.com/frasertweedale/talks Email frase@frase.id.au Twitter @hackuador