This SkillsCast is currently only available to registered attendees of Haskell eXchange 2020
It will be freely available to all Skills Matter members once the Haskell eXchange 2020 early-access window expires on December 04, 2020.
To get good performance for your Haskell microservice on Kubernetes you need the correct deployment, compiler and runtime configuration. Rational thinking is not good enough here, so let us empirically test it out.
Maybe you've got yourself a Kubernetes cluster for your Haskell web servers, are considering getting yourself some Haskell for your Kubernetes cluster, or already have a Kubernetes cluster smashed by shoddy Haskell deployments which were never performance tested?
I would like to take you on an adventure with Haskell on a Minikube to show you some basic facts about interactions among Docker, Kubernetes and Haskell runtimes. I will introduce you to cheap and cheerful performance testing with the apib tool, and show you places you can go by applying and not applying Kubernetes and Haskell best performance practices.
Have you ever wondered whatever Haskell is faster than Node.js? Did you lose sleep over choosing threaded or non-threaded runtime, determining how many threads to give to your Haskell runtime? Would you believe that Docker makes your app faster, occasionally? Does setting up Half a CPU requests and limits on Kubernetes remind you of the Judgment of Solomon?
Let us smash out of doubts pounding Haskell on a Minikube.
YOU MAY ALSO LIKE:
- Docker Fundamentals with Matt Saunders (Online Course on 1st - 4th December 2020)
- Advanced Kubernetes Concepts with Jérôme Petazzoni (Online Course on 22nd - 25th March 2021)
- CloudNative eXchange 2020 (Online Conference on 14th - 15th December 2020)
- Theorems for Free (SkillsCast recorded in November 2020)
- Comparing Strict and Lazy (SkillsCast recorded in November 2020)
Smash you some Haskell on a Minikube
Mateusz Curylo works at Habito, where they write Haskell code for fun and profit. Before doing Haskell, they were hooked up on full-stack development writing Kubernetes microservices in Java and frontends in Typescript. They choose files over databases, books over tweets, empiricism over rationalism, and ultrafinitism over abstract nonsense. Having experienced way too much loading screens, they know for a fact that slow software is a waste of time.