Alex Mensák

We are happy to use Terraform to manage our cloud infrastructure in GCP as having multiple microservices is time demanding. It costs time to add new services and even more time to create new environment. With terraform it's supper fast and less error prone.

We have used Auth0 for identity and access management as it completely covers our needs and even overcomes in their profesionality. We don't need to implement same tools for user management, signup/signin again. Also we don't need to follow latest security prectices as Auth0 handles thet for use. Instead we are focusing on delivering more solutions for our business needs.

We are using GitHub due to it's simplicity and popularity. We feel more productive with less tools available. #KeepItSimple

We have decided to go with managed services of GCP as we are small team and DevOps costs of managing our own Kubernetes and message broker infrastructure would costs us significant amount of time which we are able to spend on new features development.

We are building backends on NestJS framework instead of pure ExpressJS. It gives us more productivity in terms of: 1. Easy to use DI 2. Standardized naming and project structure 3. Strong tools ecosystem

Prisma API and CLI tools for migrations are saving us lot of time as they are natural fit for TypeScript standards and rest of our tool stack. It helped us save some time that we have lost when migrating from MongoDB to PostgreSQL. Compared to TypeORM, Prisma is more intuitive and helps hide repetitive tasks of maintaining data relations. But still with fair amount of bugs as is in early development.

We have switched from MongoDB to PostreSQL to gain more control of our data model. With SQL DB We are enjoying stricter data validation, relational model and better migration controls. This means more productivity and less errors in exchange for more time spend maintaining schema.

We used TS NestJS backends over Kotlin Spring boot for multiple reasons: 1. To have single technology over FE and BE 2. To attract open minded people with passion for cutting edge technology 3. To enjoy biggest open source community

We decided to build TypeScript monorepo on pure Yarn 2 with workspaces instead of Lerna. Turns out Yarn 2 workspaces plugins are enough for maintaning BE + FE monorepo.