Search Results for "ant-design"

Anoma is a next-generation blockchain protocol focused on intent-centric architecture, enabling privacy-preserving, composable transactions across multiple applications and chains. Unlike traditional account-based or UTXO models, Anoma introduces intents as the fundamental units of interaction, allowing participants to express what they want without specifying how it must be achieved. The protocol is designed with privacy, interoperability, and decentralization at its core, and is built...

...Initially compiled via grey literature (blogs, talks, forums), the catalog now includes 23 Elixir-specific smells plus 12 traditional smells adapted to Elixir. Each entry documents the name, category, problem, example, refactoring strategy, and step-by-step treatments. The smells are grouped into two categories: design-related (coarse-grained, harder to detect, affecting architecture/processes) and low-level concerns (fine-grained, often readability and maintainability issues). The catalog evolves with community feedback and contributions, aiming to help developers recognize harmful patterns and apply disciplined refactoring to improve maintainability, testability, and performance in Elixir systems.

Commanded is an Elixir framework for implementing CQRS (Command Query Responsibility Segregation) and Event Sourcing patterns. It provides domain-driven design tools—aggregates, commands, events, and projections—backed by an event store (e.g. PostgreSQL).

...Internally, it uses a vector of vectors layout rather than a single vector to minimize costly reallocations, allowing efficient bucket pointer copying instead of expensive term copying during growth. This design achieves a balance between performance and simplicity, and developers can customize bucket sizes for specific workloads, with a default of 500 offering solid performance across common scenarios. SortedSet extends beyond traditional set semantics by providing indexing, random access, and slice operations thanks to its deterministic ordering.

...By debugging and filling in missing pieces, users gain practical, hands-on experience while reinforcing theoretical knowledge. The project is ideal for both complete beginners and developers transitioning from other languages who want to learn Elixir in a structured, exploratory way. Its design emphasizes discovery, experimentation, and reflection, making it a powerful tool for deepening understanding of Elixir’s unique paradigms.

...It ships with multiple pluggable strategies—such as DNS polling, Kubernetes integration, EC2 metadata/tag discovery, UDP gossip, and EPMD helpers—so you can adapt clustering to your runtime environment. The library supervises a topology process that continually discovers peers and joins or prunes nodes as they become available or disappear. Its design embraces OTP principles: strategies implement a behavior, can be composed, and run under supervision for resilience. libcluster also emits events on nodeup/nodedown, allowing applications to react (for example, rebalance work or update registries) when membership changes. Because it relies on the BEAM’s native distribution, it integrates cleanly with Phoenix PubSub, Horde, Oban, or any other distributed Elixir tooling.

...Each day introduces new material in a concise and practical format, encouraging hands-on experimentation and gradual mastery of the language. The content covers essential topics such as pattern matching, recursion, data structures, processes, and message passing—core principles that define Elixir’s design. This incremental learning format allows developers to build confidence and understanding while maintaining consistent progress. As one of the early and influential resources in the Elixir community, 30-days-of-elixir remains a valuable guide for self-learners and newcomers to the functional programming paradigm.

...It focuses on automatic distribution and rebalancing, so when nodes join or leave, Swarm can move work and hand off state to keep the system stable. The library offers a global name registry, conflict resolution for name ownership, and hooks for reacting to membership changes. Its design embraces OTP principles, using supervised processes and fault-tolerant messaging to keep the registry resilient under failures. Developers can co-locate Swarm with their existing supervision trees to scale workers horizontally without writing custom clustering code. Typical use cases include globally unique workers, sharded consumers, and presence-like coordination where node churn is expected. ...