//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
ProfileReplies









Loading...
Don't jump into using microservices. Let the problems drive that decision. In reality, most of us will rarely justify the use of microservices.
When making changes, always reconstitute the whole aggregate. Even if it's a tiny change. That way you can verify no business constraint is broken. You can always optimize this later on.
Don't wait for long running jobs. Instead, return quickly with a JobHandle object, that can be used to track the progress of the job.