How to generate a UUID v4 in Go using google/uuid?

Use the uuid.New() function, which returns a random UUID v4 compliant with RFC 9562. Import the package and call it directly; it's thread-safe and requires no additional setup.

google/uuid vs github.com/satori/go.uuid – which is better for Go projects?

google/uuid is more actively maintained and follows the latest RFC standards, while satori/go.uuid has had security issues and is less updated. For new projects, google/uuid is generally recommended due to its reliability and Google backing.

What are the main differences between google/uuid and pborman/uuid?

google/uuid uses a 16-byte array for UUIDs, enhancing type safety but losing the ability to represent invalid UUIDs. pborman/uuid uses byte slices, which can model invalid states but are less type-safe. Migration may require code adjustments.

How do I check if a UUID is zero or NIL with this package?

Compare the UUID to uuid.Nil using the == operator. Since UUIDs are value types in Go, this is a straightforward and efficient way to identify uninitialized UUIDs in your code.

Is google/uuid safe for concurrent use in Goroutines?

Yes, the package's functions, such as uuid.New(), are thread-safe and can be called concurrently from multiple Goroutines without additional synchronization, making it suitable for high-performance applications.

Can I use google/uuid for database primary keys in PostgreSQL or MySQL?

Yes, UUIDs generated by this package are standard 16-byte values that can be stored as binary or string types in databases. Ensure your database schema supports UUID columns, and convert to appropriate formats if needed.

uuid — Go UUID Generation Package

What is uuid?

Google's uuid is a Go package that provides a robust implementation for generating and inspecting Universally Unique Identifiers (UUIDs). It ensures compliance with RFC 9562 and DCE 1.1 standards, making it suitable for distributed systems requiring unique identifiers. The package uses a fixed 16-byte array for better type safety and clear handling of NIL UUIDs.

Target Audience

Go developers building distributed systems, microservices, or applications that require reliable, standards-compliant unique identifiers for entities like database records, session tokens, or message IDs.

Value Proposition

Developers choose this package for its strict adherence to the latest UUID standards (RFC 9562 and DCE 1.1) and its type-safe implementation using a 16-byte array, which prevents invalid UUID states while maintaining backward compatibility with earlier go-uuid packages.

Go package for UUIDs based on RFC 4122 and DCE 1.1: Authentication and Security Services.

Use Cases

Best For

Generating RFC 9562-compliant UUIDs in Go applications for distributed systems.
Implementing DCE 1.1 authentication and security services that require standardized UUIDs.
Ensuring type safety in UUID handling by using fixed-size arrays instead of byte slices.
Distinguishing between valid UUIDs and NIL (zero-value) UUIDs in Go code.
Migrating from older go-uuid packages (e.g., github.com/pborman/uuid) with improved, backward-compatible implementations.
Creating unique identifiers for database records, session management, or message queues in Go microservices.

Not Ideal For

Projects requiring UUID generation in programming languages other than Go
Applications that need to explicitly represent or handle syntactically invalid UUID states
Small-scale Go scripts where minimizing third-party dependencies is a priority over type safety
Teams heavily invested in older Go UUID libraries with slice-based APIs who prefer to avoid migration refactoring

Pros & Cons

Pros

RFC 9562 Compliance

Generates UUIDs that adhere to the latest UUID specification standards, ensuring interoperability and reliability in distributed systems.

Type-Safe Implementation

Uses a fixed 16-byte array instead of byte slices, preventing invalid UUID states at compile time and reducing runtime errors.

Clear NIL UUID Handling

Provides a distinct uuid.Nil value for zero-value UUIDs, making it easy to check for uninitialized or placeholder identifiers.

Backward Compatibility

Evolved from earlier go-uuid packages like pborman/uuid with improvements, easing migration while maintaining core functionality.

Cons

Loss of Invalid Representation

The switch to a fixed array means it cannot model UUIDs that are syntactically invalid, which might be needed for certain validation or error-handling scenarios.

Go-Only Solution

Exclusively targets Go applications, making it unsuitable for polyglot projects that require consistent UUID generation across multiple programming languages.

Migration Overhead

Developers moving from slice-based UUID packages may face refactoring challenges due to the array-based API change, as noted in the README's comparison with predecessors.

Frequently Asked Questions

What is uuid?

Target Audience

Value Proposition

Use Cases

Best For

Generating RFC 9562-compliant UUIDs in Go applications for distributed systems.
Implementing DCE 1.1 authentication and security services that require standardized UUIDs.
Ensuring type safety in UUID handling by using fixed-size arrays instead of byte slices.
Distinguishing between valid UUIDs and NIL (zero-value) UUIDs in Go code.
Migrating from older go-uuid packages (e.g., github.com/pborman/uuid) with improved, backward-compatible implementations.
Creating unique identifiers for database records, session management, or message queues in Go microservices.

Not Ideal For

Projects requiring UUID generation in programming languages other than Go
Applications that need to explicitly represent or handle syntactically invalid UUID states
Small-scale Go scripts where minimizing third-party dependencies is a priority over type safety
Teams heavily invested in older Go UUID libraries with slice-based APIs who prefer to avoid migration refactoring

Pros & Cons

Pros

RFC 9562 Compliance

Generates UUIDs that adhere to the latest UUID specification standards, ensuring interoperability and reliability in distributed systems.

Type-Safe Implementation

Uses a fixed 16-byte array instead of byte slices, preventing invalid UUID states at compile time and reducing runtime errors.

Clear NIL UUID Handling

Provides a distinct uuid.Nil value for zero-value UUIDs, making it easy to check for uninitialized or placeholder identifiers.

Backward Compatibility

Evolved from earlier go-uuid packages like pborman/uuid with improvements, easing migration while maintaining core functionality.

Cons

Loss of Invalid Representation

The switch to a fixed array means it cannot model UUIDs that are syntactically invalid, which might be needed for certain validation or error-handling scenarios.

Go-Only Solution

Exclusively targets Go applications, making it unsuitable for polyglot projects that require consistent UUID generation across multiple programming languages.

Migration Overhead

Developers moving from slice-based UUID packages may face refactoring challenges due to the array-based API change, as noted in the README's comparison with predecessors.

Frequently Asked Questions

uuid

What is uuid?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

uuid

What is uuid?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?