Have you had experience developing and designing a system following clean architecture principles?

Yes, I have experience developing systems using clean architecture principles in Go. The main idea is to separate the application into layers: Entities, Use Cases, Interface Adapters, and Frameworks & Drivers. This allows isolating business logic from implementation details, making testing and maintenance easier.

For example, in a project, I allocated packages for domain logic, repository interfaces and their implementations, as well as for HTTP handlers. Interaction between layers was through interfaces, which made it easy to replace implementations and write unit tests.

// Example of a repository interface
type UserRepository interface {
    GetUserByID(id string) (*User, error)
}

// Use case that uses the repository
func GetUserProfile(repo UserRepository, id string) (*UserProfile, error) {
    user, err := repo.GetUserByID(id)
    if err != nil {
        return nil, err
    }
    // business logic
    return &UserProfile{Name: user.Name, Email: user.Email}, nil
}

This approach helps keep the code clean and easily extendable.