Day 2

Hours worked/Total: 3/4

Day Recap

Outcome: QuestDB is installed and connected, but man, ORM headaches are real. 🤦‍♂️ Trying to decide the best stack for quick prototyping and beyond, while minimizing managing database manually.

What I Did

• Installed QuestDB
• Explored ORM options for QuestDB—Python wins for now (SQLAlchemy & Tortoise are decent, but Go? Nada).
• Created a Python project to test SQLAlchemy with QuestDB. Integration works… but it’s messy.
• Couldn’t get async support in SQLAlchemy—sync-only is a letdown

Remarks

ORM struggles hit different...You’re trying to simplify life but end up complicating everything:

• Async not working? Cool, let’s debug
• Debug fails? OK, ditch the whole stack entirely

The more I tinker, the more it’s clear

• Use Go for microservices (fast data ingestion FTW)
• Keep Python for maintenance tasks

But here’s the dilemma:  Do I stick with raw Go services for API calls or introduce a workflow system? 🤷‍♂️

Next Goals

Decide between Lightweight Go microservices OR  full-blown workflow orchestration for better scalability. Then build a Go-based web service for third-party API calls