Technologies
- Cloud Platform - AWS, GCP
- Code Hosting - GitHub
- CDN - CloudFront, Fastly
- Email Services - SES, MailChimp, Mandrill
- Monitoring - Sentry, Datadog, New Relic, CloudWatch
- Task management - Jira, Trello
- Communication - Slack, Zoom, Google Meet
- Core technologies - Python 3.11, Django 4, Celery
- API - mostly GraphQL, sometimes REST
- Favorite template engine - Jinja2
- Storage - Postgres or MySQL, Redis, S3
- Frontend - React.js, TypeScript, Webpack, SASS, CSS modules
- Testing and codestyle - py.test, Selenium + Headless Chrome, Jest, Flake8, ESLint + Airbnb config
- Deployment - Docker images based on Debian (Docker Compose for local environment, EKS or ECS for production), Terraform, CloudFormation, GitHub Actions
- Data processing and analysis: Apache Spark (AWS Glue), Kafka, AWS Kinesis Firehose, AWS Athena
- Data warehouses: Google BigQuery, AWS Redshift, Snowflake
- Graph databases: Neo4j
- Mobile apps: React Native
We recommend against the use of the following technologies in our new or existing projects:
- Styled Components. Use CSS modules instead. Unlike Styled Components, CSS modules don't introduce overhead and are also compatible with CSS linters and SASS.
- Tailwind CSS. Basically, these are fancy inline styles, no matter what framework authors say. This concept goes against the DRY principle and makes the code harder to read, debug, and maintain.
English
Русский