Documenting code, one commit at a time.
The justifai project is a microservice-based application that initially launched with an open API. As the project evolved, it became crucial to implement robust security measures and comprehensive monitoring to ensure data integrity, user authentication, and system reliability.
On the justifai project, our infrastructure as code (IaC) setup, while functional, presented growing challenges. Initially designed as a flat Terraform configuration, it became increasingly complex to manage, understand, and scale as the project evolved. This monolithic approach obscured resource dependencies, hindered reusability, and increased the cognitive load on developers.
Ever been blocked at the final hurdle of deployment by something as seemingly simple as a file upload? For the justifai project, preparing for an end-to-end demo revealed a common, yet critical, oversight: S3 Cross-Origin Resource Sharing (CORS) configurations. This often overlooked detail can halt browser-based uploads dead in their tracks, especially when using presigned URLs, leading to
In the justifai project, a critical aspect of the dashboard functionality involves managing document statuses, specifically through validation and rejection. These operations require sending PATCH requests to the backend API to update document records. However, users were encountering issues where these updates were unexpectedly failing.
PATCH Requests