Chilli

Decision at Chilli about Angular 2

Avatar of catwell
Pierre Chapuis ·

We chose Angular 2 (version 7 actually) because our product has a rather complex backend, most of which is visible only to our employees and contractors.

The "full featured" approach of Angular as well as the way it deals with the data model suited this business case well. We also use the Reactive Forms module a lot, as well as Clarity (an Open Source design system by VMWare) for the internal parts of the frontend. We also intend to use Angular's offline features.

6 upvotes·4.1K views

Decision at Chilli about Python, SQLAlchemy, Hug, Flask

Avatar of catwell
Pierre Chapuis ·

Unlike our frontend, we chose Flask, a microframework, for our backend. We use it with Python 3.

One of the reasons was that I have significant experience with this framework. However, it also was a rather straightforward choice given that our backend almost only serves REST APIs, and that most of the work is talking to the database with SQLAlchemy .

We could have gone with something like Hug but it is kind of early. We might revisit that decision for new services later on.

5 upvotes·1 comment·11.1K views

Decision at Chilli about Arch Linux, Amazon EC2, PostgreSQL, Amazon RDS for PostgreSQL

Avatar of catwell
Pierre Chapuis ·

We use AWS mostly because Amazon RDS for PostgreSQL is a very good and cheap solution to get a managed PostgreSQL.

We also use Amazon EC2 for the servers, with the Arch Linux images from Uplink Labs. We chose Arch Linux because of its up-to-date packages, especially for Python. We use Pacman to package and deploy our services.

5 upvotes·2.3K views

Decision at Chilli about TypeScript

Avatar of catwell
Pierre Chapuis ·

We use TypeScript because it is the native language of Angular applications, but also because types helps prevent errors at compile time.

1 upvote·25 views