Technologies

Infrastructure

• Cloud Platform - AWS
• Code Hosting - Github
• CDN - MaxCDN, CloudFront
• Email Services - SES, MailChimp, Mandrill
• Monitoring - Sentry, Datadog, CloudWatch
• Task management - JIRA, Trello
• Communication - Slack, Zoom

Web Projects on Python

• Core technologies - Python 3.8, Django 3.0, and Celery
• API - GraphQL or REST
• Favorite template engine - Jinja2
• Storage - Postgres or MySQL (in production - RDS or Aurora), Redis (in production - ElastiCache), S3
• Frontend - React.js, Babel (ES2019), Webpack, SASS, CSS modules
• Testing and codestyle - py.test, Selenium + Headless Chrome, Mocha, Flake8, ESLint + Airbnb config
• Deployment - Docker images based on Debian or Alpine (Docker Compose for local environment, AWS and ECS for production), CloudFormation, uWSGI, Fluentd, Datadog, Jenkins

Supported Browsers

• Chrome
• FireFox
• Safari
• Edge
• IE11+ (for IE11 and below, a warning message is displayed if an upgrade is required)
• Mobile Safari
• Android Browser, supporting only >= 4.4

Data lake for data collection and analysis

• Data warehouses: S3 (in Apache Parquet format), Redshift
• Data processing and analysis: AWS Kinesis Firehose, AWS Glue, AWS Athena

Mobile applications

• Framework - React Native
• CI/CD - Jenkins
• Error Monitoring - Sentry

Not recommended

These technologies are not recommended to be used in our new or existing projects:

• Typescript. We think that Typescript slows down development significantly, and at the same time only helps to prevent a small percentage of bugs in real code. There are studies on this topic that demonstrate that static typing helps to prevent less than 3% of bugs. It doesn't mean though that we're strictly opposed to the idea of explicit types declaration. It can be helpful sometimes, we just don't think that it should be mandatory and enforced;
• Styled Components. Use CSS modules instead. Unlike Styled Components, CSS modules don't introduce overhead and are also compatible with CSS linters and SASS.