What are the migration paths between them?

I can only answer questions about lmax-exchange/disruptor or supertokens/supertokens-core.

The two repositories you're asking about—lmax-exchange/disruptor and supertokens/supertokens-core—are independent projects with different purposes:

• lmax-exchange/disruptor is a high-performance inter-thread messaging library for Java.
• supertokens/supertokens-core is an authentication/authorization backend service.

There are no migration paths between them because they serve entirely different functions and domains. One is a low-level messaging library; the other is a complete authentication platform. They could potentially be used together (supertokens-core might use disruptor internally for performance), but that's a dependency relationship, not a migration path.

If you're asking about:

• Migrating data or services between them: Not applicable—they're not alternatives to each other.
• Upgrading within one of them: I can help explain version upgrades, API changes, or configuration migration within either project individually.
• Whether supertokens-core depends on disruptor: I can search for that dependency relationship.

What specific migration scenario were you interested in?

FOLLOW_UPS:

• Does supertokens-core depend on disruptor library?
• What are disruptor's main use cases?
• How does supertokens-core handle data persistence?