@dillon_mulroy@Jilles@heymingwei Also previously used DynamoDB. I think there are two ways of approaching it. Either use DO as “collections” or as “sharding” of user data. I used to think of it as a way of multi tenantcy where each have their own DB.
@bleuonbase@Jilles@dillon_mulroy@heymingwei Depends on the work. You could argue that having just simple analytics for a user would be better to have in a DO and then run periodically with alarms. Then they are also easier to clean up.
I’ve also used Analytics Engine for some projects.
@Jilles@dillon_mulroy@heymingwei I have one D1 binding for better auth tables, maybe org/user settings etc. Then have each entity inside a DO.
For me the mental model is; if i need some entity for a user, let’s say “projects” I just fetch them from the DO.
WAH is looking to strengthen our team, and currently have two open positions for a:
- Creative Frontend Developer
(https://t.co/U82EHRX6et)
- Frontend Engineer
(https://t.co/gMiBOvvb3Z).
Both positions are remote ok 🏝
@bruno_simon Honestly, you should do a “part 2” of your existing course focused on web implementation. How to do image scale effects, placement and performance. That’s something there is hard to come by..