If one or more drives are offline at the start of a PutObject or NewMultipartUpload operation the object will have additional data
protection bits added automatically to provide the regular safety for these objects up to 50% of the number of drives.
This will allow normal write operations to take place on systems that exceed the write tolerance.

- **Cross-Language Compatibility:**
Java serialization is inherently Java-centric and does not support cross-language scenarios well.

- **Type Safety:**
Java serialization does not enforce type safety as strictly as some alternatives, potentially leading to runtime errors.

## Decision

We do not use Java serialization.

 * <p>
 * This package contains the data model classes that represent the structure of Maven POM files.
 * These classes are immutable to ensure thread safety and prevent unintended modifications.
 * The root class is {@link org.apache.maven.api.model.Model}, which represents the entire POM.
 * <p>
 * Key components include:
 * <ul>

 * different Maven operations. All implementations must be immutable to ensure thread safety
 * and predictable behavior in concurrent environments.
 *
 * @param <S> the type of ProtoSession associated with this request, allowing for
 *           type-safe session handling in specific request implementations
 *
 * @see ProtoSession
 * @see RequestTrace
 * @see Result
 * @since 4.0.0

import org.apache.maven.model.Model;

/**
 * Describes a tag used by the model builder to access a {@link ModelCache}. This interface basically aggregates a name
 * and a class to provide some type safety when working with the otherwise untyped cache.
 *
 * @param <T> The type of data associated with the tag.
 * @deprecated use {@code org.apache.maven.api.services.ModelBuilder} instead
 */
@Deprecated(since = "4.0.0")

### High availability

A stand-alone MinIO server would go down if the server hosting the drives goes offline. In contrast, a distributed MinIO setup with _m_ servers and _n_ drives will have your data safe as long as _m/2_ servers or _m*n_/2 or more drives are online.

		// We are hitting the timeout too often, so increase the timeout by 25%
		timeout := min(
			// Set upper cap.
			atomic.LoadInt64(&dt.timeout)*125/100, int64(maxDynamicTimeout))
		// Safety, shouldn't happen
		if timeout < dt.minimum {
			timeout = dt.minimum
		}
		atomic.StoreInt64(&dt.timeout, timeout)
	} else if failPct < dynamicTimeoutDecreaseThresholdPct {

 *   <li>Handle project forking states</li>
 * </ul>
 *
 * The service maintains the mutable state of projects as they progress through
 * their build lifecycle, ensuring thread-safety and proper state management.
 * All implementations must be thread-safe as they may be accessed concurrently
 * during parallel builds.
 *
 * @since 4.0.0
 * @see org.apache.maven.api.services.ProjectBuilder
 * @see Project
 */
@Experimental

// system (crypto/rand) is used.
func GenerateKey(extKey []byte, random io.Reader) (key ObjectKey) {
	if random == nil {
		random = rand.Reader
	}
	if len(extKey) != 32 { // safety check
		logger.CriticalIf(context.Background(), errors.New("crypto: invalid key length"))
	}
	var nonce [32]byte
	if _, err := io.ReadFull(random, nonce[:]); err != nil {

            context.terminal = MessageUtils.getTerminal();
            context.closeables.add(MessageUtils::systemUninstall);
            MessageUtils.registerShutdownHook(); // safety belt
        } else {
            doConfigureWithTerminal(context, context.terminal);
        }
    }

    /**
     * Override this method to create Terminal as you want.
     *