OAuth2 VS Google Persistent Disk

• Delegated access without sharing credentials
  OAuth2 lets users grant third-party applications limited access to their resources without handing over their passwords. Access tokens stand in for credentials, so a compromised client exposes far less than a leaked username and password would.
• Scoped and limited permissions
  Tokens can be restricted to specific scopes, resources, and lifetimes, so applications receive only the access they need. Users and administrators can also revoke tokens at any time without changing the account password.
• Widely adopted industry standard
  OAuth2 is supported by major providers such as Google, Microsoft, GitHub, and Facebook, and by most identity platforms. This broad adoption means mature libraries, SDKs, tooling, and community knowledge are available for nearly every language and framework.
• Flexible grant types for many use cases
  The framework defines multiple flows, including Authorization Code (with PKCE), Client Credentials, and Device Code. These cover web apps, single-page apps, mobile apps, server-to-server communication, and input-constrained devices.
• Enables single sign-on and API ecosystem integration
  Combined with OpenID Connect, OAuth2 supports federated login and single sign-on across services. It also provides a consistent way to secure APIs and let third-party developers integrate with a platform in a controlled manner.

Possible disadvantages

• Complexity and steep learning curve
  OAuth2 involves many concepts, including roles, grant types, scopes, redirect URIs, and token lifecycles. Developers can easily be confused about which flow to use, and misunderstanding the spec often leads to flawed implementations.
• Easy to implement insecurely
  The spec is a framework rather than a strict protocol, leaving many decisions to implementers. Common mistakes include weak redirect URI validation, missing state parameter checks, using the deprecated Implicit flow, and insecure token storage, all of which can lead to vulnerabilities.
• Bearer tokens are vulnerable if stolen
  Standard bearer tokens grant access to whoever holds them, so leaked or intercepted tokens can be replayed by attackers. Mitigations such as short lifetimes, TLS, DPoP, or mTLS add extra implementation effort.
• Not an authentication protocol by itself
  OAuth2 is designed for authorization, not for verifying user identity. Using it for login without an identity layer like OpenID Connect leads to misuse and security gaps, and requires adopting additional standards.
• Fragmented and inconsistent implementations
  Because the specification is loose and has many extensions (OAuth 2.1 drafts, PKCE, DPoP, and others), providers implement it differently. This causes interoperability issues, provider-specific quirks, and extra work when integrating with multiple services.

• High Durability
  Google Persistent Disk offers reliable storage with redundancy across multiple disks, ensuring data durability and reducing the risk of data loss.
• Automatic Backups
  Supports automated snapshots for easy backup and recovery, allowing you to restore data to any point in time.
• Scalability
  Easily scalable to accommodate growing storage needs. You can increase your storage capacity without downtime.
• Integration with Google Cloud
  Seamlessly integrates with other Google Cloud services for efficient management and utilization within the cloud ecosystem.
• Performance
  Provides persistent, high-performance block storage suitable for a wide range of applications, including databases and high-traffic websites.

Possible disadvantages

• Cost
  Pricing can become expensive, especially with large data sets or high IOPS requirements, compared to some other storage options.
• Zonal Availability
  Dependent on the geographical location of the data center and may require particular configurations for applications needing multi-region failover support.
• Complexity
  Managing and configuring persistent disks might be complex for users unfamiliar with Google Cloud's interface and services.
• Performance Limits
  Though performance is generally high, it may have limitations, such as maximum IOPS and throughput, depending on the disk type and size.

Tracking OAuth2 since Oct 2026.

• SSDs Have Become Fast, Except in the Cloud

  This is untrue of Local SSD (https://cloud.google.com/local-ssd) in Google Cloud. Local SSDs are PCIe peripherals. There are also multiple Persistent Disk (https://cloud.google.com/persistent-disk) offerings that are backed by SSDs over... - Source: Hacker News / over 2 years ago

• All your notes are stored in an open, unsecure, and unencryped format on the Remarkable cloud. Just so you know.

  Google uses several layers of encryption to protect customer data at rest. All customer content stored at rest is encrypted, without any action required from the customer, using one or more encryption mechanisms. All data stored in... Source: over 5 years ago