Dieter Vekeman

We use IntelliJ IDEA because

• Free Community Edition
• Powerful IDE
• Good support for elm through the intellij-elm plugin
• Good support for haskell through the Intellij Haskell Plugin
• Refactoring
• Searching & replace
• Built-in terminal
• Git support (very good diff tool)

We use Git because

• it's the standard
• it's powerful (git reflog saved me already a few times)

We use Bitbucket because

It provided private repositories (at a time where github didn't provide that yet)

On the longer term (if the team size would grow) I would use Confluence / JIRA which integrate well with Bitbucket.

I am currently not using any of the CI capabilities (e.g. pipelines) but I might in the future.

• External user authentication and authorization (roles & groups)
• Our database does not need to store any personal data (name, username, password) which helps for GDPR
• Our system does not need to deal with password security, recovery, ...
• JWT tokens are verified on each api call
• Users are cached internally using redis

Auth0

• Send emails to user (e.g. account creation)
• Send emails to the administrator (e.g. upon certain errors in the system)

Amazon SES

• Fast delivery
• limit content distribution (whitelist of countries): allows us to better control the data being transferred (reducing costs), avoiding unwanted access

Amazon CloudFront

Frontend application Elm

• Typesafe frontend coding
• Easy refactoring (make the changes and fix the compilation errors)
• Quick (re)compilation (v0.19)
• Automatic recompilation in development using npm + webpack
• Production output is small and fast
• Built-in architecture (The Elm Architecture: Model View Update)

Hosting the main relational DB engine

• Scalable
• Accessed by the backend (AWS EC2)
• Automatic minor upgrades
• Automated daily backups

Amazon RDS for PostgreSQL

• Static resources (html, css, js, ...)
• S3 sits behind AWS CloudFront

Amazon S3

Application server hosting the Haskell backend and the redis server

• lightweigt EC2 instance (t2.micro)
• Sits behind the AWS ELB
• Linux Debian system
• Runs a keter container
• Can bring up more instances to scale horizontally

Amazon EC2