2 Matching Annotations
  1. Last 7 days
    1. Environments

      • Dev.. Qc(test) ... Stage(product owner).. Prod

      • only one prod

      • vpc-network/aws Account) per environment is better

      • why org accounts? sometimes env managed by team with iam account, least priveldge policy

      • good design ex? Ex prod has following resources and vpc , prod-vpc and prod-db

      • theoretical ::: same resources per env.

      • non prod env, we destroy other resources /environments -script created destroyed

      Ex destroying lamda fn

      -Qc on/off with lambda fns that open Ec2 etc

      • Ec2 with off service

      Autoscaling in all prod

      Resources in down times, resources to minimum..

  2. May 2026
    1. class-validator and class-transformer are complementary TypeScript libraries used extensively in NestJS to validate and transform incoming request data (such as JSON bodies, query parameters, and path parameters) before it reaches your controllers. class-validator provides decorator-based validation. It checks if property values meet specific constraints (e.g., @IsEmail(), @IsNumber(), @IsNotEmpty()) and returns validation errors if the data is invalid. It does not change the data type; it only ensures the data conforms to the expected rules.