Skip to content
View jarri-abidi's full-sized avatar
🇵🇸
🇵🇸

Organizations

@careem

Block or report jarri-abidi

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned Loading

  1. tic-tac-go tic-tac-go Public

    A tic-tac-toe game developed using Go and Pixel

    Go 2

  2. todo todo Public

    (over-engineered) Example Go backend for a productivity app

    Go 5 1

  3. Jeffail/tunny Jeffail/tunny Public

    A goroutine pool for Go

    Go 4k 309

  4. Keeping Your Domain Clean: A CQRS-In... Keeping Your Domain Clean: A CQRS-Inspired Query Pattern in Go
    1
    # Keeping Your Domain Clean: A CQRS-Inspired Query Pattern in Go
    2
    
                  
    3
    The repository pattern gets you far. It keeps your persistence logic behind a clean interface, your domain entities free of database concerns, and your application code easy to test. Most services start here and it works well — until you need to fetch data that doesn't map cleanly to a single entity.
    4
    
                  
    5
    A joined query. An aggregate function result. A response that pulls from three tables and returns something none of your domain types actually represent. The temptation at that point is to reach for the repository anyway and invent a new type to hold the result: