Changes

** Python is widely adopted (one of the main languages taught at school).

** Python is widely adopted (one of the main languages taught at school).

** It scales well.

** It scales well.

** Part of the team knows Python.

** Part of the team is already using Python.

* Building an API from scratch would have been too long, so choose the FastAPI framework which integrates interesting benefits:

* Building an API from scratch would have been too long, so choose the FastAPI framework which integrates interesting benefits:

** [https://www.tutlinks.com/fastapi-with-postgresql-crud-async/ Building an API with FastAPI is very easy]: it's possible to build a simple API with its generated dynamic documentation in a few hours.

**[https://www.tutlinks.com/fastapi-with-postgresql-crud-async/ Building an API with FastAPI is very easy]: it's possible to build a simple API with its self generated documentation (openapi standard).

** Said to be fast: https://www.techempower.com/ benchmarks are showing it is ~3 times faster than very popular Python framework such as Django or Flask.

** Said to be fast: https://www.techempower.com/ benchmarks are showing it is ~3 times faster than very popular Python framework such as Django or Flask.

** FastAPI can be run with or without a web server.

** FastAPI can be run with or without a web server.

==== Database ====

==== Database ====

* It could lead to 10 times more records as the total number of products gathered by Open Food Facts.

* It could lead to 10 times more records as the total number of products gathered by Open Food Facts.

The data model simplicity lead us to choose a classical RDBMS known for its scalability: PostGRESQL. Postgre has also interesting advantages and features which can be useful for Folksonomy Engine (fully open source, transactions, stored procedures, triggers, JSON...).

The data model simplicity lead us to choose a classical RDBMS known for its scalability: PostgreSQL. PostgreSQL has also interesting advantages and features which can be useful for Folksonomy Engine (fully open source, transactions, stored procedures, triggers, JSON...).

==== Data model ====

==== Data model ====

For performance concerns, we separated the data model implementation into two tables:

For performance concerns, we separated the data model implementation into two parts :

* one small table deals with the live data

* one small table deals with the live data (current record versions)

* the other one stores all the past versions of the records.

* the other one stores all the past versions of the records.

=== Frontend ===

=== Frontend ===