pettzi. ES

An independent engineering portfolio

Care, made
considered.

Pettzi began as a place to keep every detail of a pet’s life in one thoughtful record. Today, it’s a public study in how to build software with care—from the data model to the smallest interface detail.

A completed product experiment. Shared as a reference, not a live service.

FIELD RECORD  /  001✳
A GOOD DOG

Miso

4 years
young
✳Health, in contextVisits · vaccines · little wins↗
DESIGNING FOR THE WHOLE STORY01 — 04
DOMAIN-DRIVEN DESIGN✳SERVERLESS BY CHOICE✳CARE THAT COMPOUNDS✳BUILT TO BE UNDERSTOOD✳

01 / THE INTENT

More than a pet profile.
A little continuity.

Care happens in fragments: a vaccine at the clinic, a note from a sitter, a reminder that arrives at just the right time. Pettzi explored what it might feel like to bring those fragments together without making care feel like admin.

The product is no longer operated. The code remains as a portfolio project: a chance to examine the architecture, tradeoffs, and design decisions behind a real full-stack build.

Read the project README
01

One shared story

Health events, reminders, documents, and the people who care for a pet belong together.

02

Boundaries with purpose

Each domain owns a clear part of the system, with contracts that make the seams visible.

03

Careful by default

Permission, data access, and accessible interaction shape the experience from the start.

02 / UNDER THE SURFACE

Small domains.
One connected system.

A modular monolith at the edges, serverless services in the middle, and one carefully modeled table beneath it all.

PETTZI · HIGH-LEVEL SYSTEM MAP NODE.JS 24 / AWS
Pettzi system architectureAngular web client reaches domain APIs through API Gateway. Lambda services connect to DynamoDB, S3, Cognito, SES and EventBridge.CLIENTAngular webapps / webENTRY POINTHTTP APIAPI GatewayBOUNDED CONTEXTSauthpetsownerseventsremindersuploads · catalogsthin handlers · shared domain librariesCOMPUTELambdaNode.jsDDBtableS3filesAWSidentity · eventsDynamoDB single-table designAccess patterns shape keys; bounded contexts share data through explicit domain contracts.EventBridge → reminders → SESScheduled work is isolated from synchronous API traffic.
Angular web↓API Gateway↓Auth · Pets · Owners · Events
Reminders · Uploads · Catalogs
↓Lambda services↓DynamoDB · S3 · Cognito
EventBridge · SES
HTTP request path Scheduled event pathDiagram is illustrative; see the repository for deployment details.
A

Single-table, access-pattern first

Pet, owner, event, and reminder records live in a shared DynamoDB table. Key builders keep query patterns explicit and predictable.

Explore the table design ↗
B

Contracts before coupling

OpenAPI describes the API surface. Domain libraries hold shared models and mapping rules, while handlers stay deliberately small.

Browse the domain libraries ↗

03 / FIELD NOTES

What the build
taught me.

01

Design around how data is read

A single-table model works when its access patterns are clear and treated as part of the domain—not as an afterthought.

↗
02

Modularity is a team sport

Bounded contexts help keep changes understandable, but only when the contracts between them remain visible and boring.

↗
03

Finish is part of function

Accessible contrast, useful empty states, and clear language are infrastructure for trust, especially around care records.

↗

THE MATERIALS

A practical
toolkit.

AngularNxTypeScriptAWS CDKLambdaDynamoDBOpenAPIJest

AN OPEN NOTEBOOK

Good systems make
care easier to give.

The product chapter is complete. The engineering notes are still here for anyone building thoughtful software of their own.

Visit the GitHub repository