# modularity Published articles for modularity. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Wasm components enable pluggable tooling through interposition DevFeed: [How Wasm components enable pluggable tooling through interposition]() Original publisher: [Read original article]() Author: Elizabeth Gilbert Published: 2026-05-14T00:00:00Z Content type: article Language: en Sources: [Bytecode Alliance]() Topics: [wasm](), [Architecture & Design](), [Tooling]() Tags: [architecture](), [modularity](), [services](), [tooling](), [wasm](), [wasm-components]() ### AI overview The article explains how WebAssembly components can support pluggable HTTP middleware through component composition, service chaining, and interposition. It describes in-process communication between components whose imports and exports agree, including fan-in service topologies and chains of handlers for cross-cutting request and response processing. ### Source excerpt And how the splicer framework makes it tractable at any interface edge. ## How a Learning Project Became Our Modern Mobile Test Framework DevFeed: [How a Learning Project Became Our Modern Mobile Test Framework]() Original publisher: [Read original article]() Author: Raymond Saba I'm an SDET who enjoys building test automation; Finding Ways Published: 2026-02-18T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Mobile](), [Automation](), [webDriver](), [Concurrency](), [Java]() Tags: [appium](), [automation](), [engineering](), [java](), [migration](), [mobile](), [modularity](), [overhead](), [quality-assurance](), [standards](), [threads](), [webdriver]() ### AI overview This engineering article describes how trivago's aging homegrown mobile automation framework evolved into a shared iOS and Android test framework. It covers the transition from Appium 1 to Appium 2 and later Appium 3, including a rewrite based on W3C WebDriver standards, platform-specific drivers, modularity, and parallel execution with threads in one JVM. ### Source excerpt About six years ago, our mobile automation setup was showing its age. It was a small, homegrown framework that had worked "well enough" for a long time, until we tried to upgrade Java and a few ... ## Creating an Arduino Library for ESP32 DevFeed: [Creating an Arduino Library for ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2025-12-15T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Arduino](), [ESP32](), [Library](), [Development](), [Code](), [C++](), [ide](), [Programming](), [API]() Tags: [arduino](), [arduino-ide](), [beginner](), [blog](), [c-plus-plus](), [class](), [classes](), [code](), [development](), [esp32](), [getting-started](), [guide](), [how-to](), [ide](), [libraries](), [library](), [maintainability](), [modular](), [modularity](), [modules](), [programming](), [structure](), [tutorial]() ### AI overview A step-by-step guide to creating, structuring, and publishing custom Arduino libraries for ESP32. It explains library benefits and structure, prerequisites, and implementation through a minimal "Hello World" example. ### Source excerpt Learn how to create, structure, and publish Arduino libraries for ESP32. This step-by-step guide covers everything from understanding a library structure to submitting your library to the Arduino Library Manager. ## Bevy Entity Component System on ESP32 with Rust no\_std DevFeed: [Bevy Entity Component System on ESP32 with Rust no\_std]() Original publisher: [Read original article]() Author: John Lee Published: 2025-04-09T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Bevy](), [Rust](), [ESP32](), [Development]() Tags: [bevy](), [blog](), [component](), [ecs](), [embedded](), [embedded-systems](), [esp32](), [esp32-c3](), [esp32-s3](), [microcontrollers](), [modular](), [modularity](), [no-std](), [rust](), [wasm]() ### AI overview This tutorial demonstrates how to use Bevy ECS with Rust no_std on ESP32 devices. It explains ECS concepts and shows embedded application examples based on Conway's Game of Life and the Spooky Maze Game, with an emphasis on modular code structure and event-based peripheral integration. ### Source excerpt Introduction# Embedded development in Rust is rapidly evolving, and one of exciting new developments is the introduction of no_std support into the Bevy Entity Component System (ECS). This improvement allows developers to leverage the powerful and modular design of Bevy ECS on resource-constrained devices like the ESP32. ## Vector Sets are part of Redis DevFeed: [Vector Sets are part of Redis]() Original publisher: [Read original article]() Published: 2025-04-03T18:01:20Z Content type: article Language: en Sources: [Antirez]() Topics: [Redis](), [Data structures](), [API](), [Programming]() Tags: [api](), [data-structure](), [design](), [modularity](), [module](), [native](), [redis](), [vector]() ### AI overview The article announces that Vector Sets have been merged into Redis. It describes them as a new Set-like data type that stores vectors, supports vector-similarity queries, and will be available as a native data type in Redis 8 while retaining modular internal boundaries. The feature is still in beta. ### Source excerpt Yesterday we finally merged vector sets into Redis, here you can find the README that explains in detail what you get: https://github.com/redis/redis/blob/unstable/modules/vector-sets/README.md The goal of the new data structure is, in short, to create a new "Set alike" data type, similar to Sorted Sets, where instead of having a scalar as a score, you have a vector, and you can add and remove elements the Redis way, without caring about anything except the properties of the abstract data structure Redis implements, ask for elements similar to a given query vector (or a vector associated to some element already in the set), and so forth. But more about that later, a bit of background, first: From the path of the README itself, you can see the implementation is into "modules", but actually, Vector Sets are not a module, it's a part of the Redis core, the thing is that I started developing them as a module, and later I suggested that the implementation should still use the modules API, in order to promote modularity of the internals of Redis, in order to have both the advantages: every Redis instance starting from Redis 8 will have Vector Sets as a native data type, and there are clear boundaries between the core and the implementation ## The first new main data type of Redis after... some time I think that the latest big data structure of Redis were Streams, also developed by me. I resigned, returned, forks happened in the meantime, and it still it looks like the burden to introduce a new data type in Redis is mine :D I must say: I'm ok with that, because as much as I like programming, I also like design, a lot, and I had a feeling, that vectors, and vector similarity, are conceptually very simple, so they deserved a very simple API. And that was what I tried to do. Vector Sets are still a beta feature but I can tell you something, I can guarantee you can learn the API in 3 minutes. I decided that a fundamental requirement for implementing vector similarity was to also ## Ep. 2: Elevating Software Design in Go: Package Architecture in Modern Development DevFeed: [Ep. 2: Elevating Software Design in Go: Package Architecture in Modern Development]() Original publisher: [Read original article]() Published: 2024-05-21T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Software Engineering](), [Architecture & Design](), [Code]() Tags: [api-design](), [code-modularity](), [dependencies](), [go](), [go-development](), [go-projects](), [integrity](), [modularity](), [package-architecture](), [scalability](), [software-design]() ### AI overview This video episode explains package architecture in Go. It emphasizes clear boundaries between components, focused package functionality, avoiding generic packages such as "Utils" or "Common," and the role of robust type systems in maintainable software. ### Source excerpt Introduction: In this insightful episode, Bill dives deep into the realm of package design, shedding light on its crucial role in software development. Here are three key takeaways for Go developers: Code Modularity: Learn how Go's packaging system creates essential firewalls between program components, enhancing maintainability. Focused Functionality: Discover the importance of designing packages that provide specific functionality, fostering code clarity. Avoiding Pitfalls: Bill warns against common package design mistakes like centralized "common" packages, promoting a layered approach to maintainable code. ## Ethereum Foundation Announces $900K Collaborative Zero-Knowledge Public Goods Grant Round DevFeed: [Ethereum Foundation Announces $900K Collaborative Zero-Knowledge Public Goods Grant Round]() Original publisher: [Read original article]() Author: Rodrigo Vasquez Published: 2024-02-21T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [zero-knowledge]() Tags: [announce](), [applications](), [collective](), [dependencies](), [ethereum](), [funding](), [modularity](), [open](), [project](), [research-development](), [standards](), [zero-knowledge]() ### AI overview The Ethereum Foundation, Aztec, Polygon, Scroll, Taiko, and zkSync launched a collaborative grant round for Zero Knowledge public goods projects. The six co-funders contributed $150,000 each, creating a $900,000 pool, and will participate in funding allocation decisions. Applications close on March 18, 2024. ### Source excerpt The Ethereum Foundation is thrilled to announce a collaborative grant round with Aztec, Polygon, Scroll, Taiko, and zkSync to develop Zero Knowledge public goods projects. Each co-funder of the grant round has contributed 150K USD in funds, bringing the total grant pool to 900K USD. The breadth and complexity... ## TDD: Writing Testable Code DevFeed: [TDD: Writing Testable Code]() Original publisher: [Read original article]() Author: Eric Elliott Published: 2024-01-21T23:50:43Z Content type: tutorial Language: en Sources: [Eric Elliot]() Topics: [Test-driven development](), [Software Engineering](), [coding](), [CI/CD]() Tags: [advice](), [complexity](), [defects](), [javascript](), [modularity](), [react](), [software-engineering](), [tdd](), [technology](), [typescript]() ### AI overview This tutorial explains how to write more testable code through modularity, clarity, separation of concerns, and independence from external systems. It also describes tight coupling as a barrier to testability and maintainability, noting that dependencies can cause changes to cascade into bugs elsewhere. ### Source excerpt Writing testable code is a vital skill in software engineering. Let's explore practical advice, strategies, and tactics for writing more testable code, unlocking the benefits of modularity, reusability, and high quality software in your projects. Embracing testability in your coding practice isn't just about catching bugs; it's about fostering a culture of quality and efficiency in your projects. A good quality process is an essential prerequisite to continuous delivery, which is the ability to ship code to production at any time, allowing you to iterate quickly and respond to user needs and changing expectations. We'll start by exploring the importance of separation of concerns -- a principle that's crucial in achieving testable code. This approach isn't just a technical necessity; it's a mindset that simplifies complexity and enhances the overall quality of your work. Whether you're a seasoned developer or just starting out, this article aims to provide practical advice and strategies that can be immediately applied to your projects. Overview of Testability in Code Testability in code refers to how easily a software system can be tested. Highly testable code allows for more efficient and effective identification of defects, ensuring higher quality and reliability. Key characteristics of testable code include modularity, where the code is organized into discrete units; clarity, meaning the code is understandable and its purpose is clear; and independence, where units of code can be tested in isolation without reliance on external systems or states. Understanding the Problem: Tight Coupling in Code Tight coupling is often a subtle yet significant barrier to achieving highly testable and maintainable code. Coupling is the degree to which a change in one part of the code may impact or break the functionality in another part of the code. Tight coupling occurs when two or more parts of the code are highly dependent on each other, making it difficult to change one part wi ## Managing State in Vue Applications: The Composable Provider Pattern DevFeed: [Managing State in Vue Applications: The Composable Provider Pattern]() Original publisher: [Read original article]() Author: Doximity Published: 2023-07-21T07:23:00Z Content type: article Language: en Sources: [Doximity]() Topics: [Vue.js](), [Front end](), [Scalability](), [Nuxt.js]() Tags: [code-modularity](), [components](), [maintainability](), [modularity](), [reusable-code](), [reuse](), [scalability](), [state-management](), [vue]() ### AI overview This article explains the Composable Provider pattern for state management in Vue applications. The approach combines the Vue Composition API with the Provide/Inject APIs to manage complex, feature-driven state, with benefits including scalability, maintainability, reusability, and reduced code duplication. ### Source excerpt State management is a fundamental concept of front-end application design, and a critical aspect in building robust Vue applications. As Vue applications grow in complexity, managing state becomes an increasingly challenging task, especially when working with a large organization of engineers spread across various product teams. Fortunately, the Vue and Nuxt ecosystem provides a variety of state management solutions, each with its own trade-offs. In this blog post we will explore the Composable Provider pattern, which handles state management by combining the Vue Composition and Provide/Inject APIs, and why its clean and simple implementation is a powerful approach to handling complex, feature-driven state in modern Vue applications. Note: This article was originally intended as a reference for our internal engineering team, but given its potential general use among Vue application developers we are publishing it here. We hope you'll find this pattern helpful when designing your Vue application's state as we have here at Doximity! Why Efficient State Management Matters Efficient state management plays a crucial role in the development of Vue applications. As applications grow in complexity, the ways in which we manage and handle changes to state become increasingly important. Here are a few key reasons why managing state efficiently matters: Scalability: As Vue applications and the teams building them grow in size, the complexity and size of their state grow also. Efficient state management allows for better scalability by providing a structured and organized approach to handling state. It becomes easier to add new features, maintain existing functionality, and reason about the flow of data within the application. Code Maintainability: Well-managed state reduces code complexity and promotes code maintainability. When state is not encapsulated properly, it becomes challenging to understand and modify the application's behavior. By implementing sound state management ## How to Generate Package Private Code with jOOQ's Code Generator DevFeed: [How to Generate Package Private Code with jOOQ's Code Generator]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-06-28T15:54:18Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Code](), [Java](), [Code generation](), [configuration](), [Java 9]() Tags: [code](), [code-generation](), [code-generator](), [compilation](), [configuration](), [how-to](), [java](), [java-9](), [jooq](), [jooq-code-generator](), [jooq-in-use](), [modularity](), [package-private](), [visibility](), [visibility-modifier]() ### AI overview This tutorial explains Java package-private visibility and shows how to configure jOOQ's code generator to generate package-private types. The approach can help keep generated jOOQ implementation details from leaking into client code. ### Source excerpt Java's package private visibility is an underrated feature. When you omit any visibility modifier in Java, then the default (for most objects) is package private, i.e. the object is visible only to types in the same package: In fact, a compilation unit (the .java file) can contain multiple such classes. You don't have to create ... Continue reading How to Generate Package Private Code with jOOQ's Code Generator -> ## The supergraph: a new way to think about GraphQL DevFeed: [The supergraph: a new way to think about GraphQL]() Original publisher: [Read original article]() Author: Matt DeBergalis Published: 2022-05-18T09:00:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [API](), [Architecture & Design](), [Microservices](), [Microservice](), [Kubernetes](), [React]() Tags: [announcement](), [apis](), [apollo](), [apollo-federation](), [architecture](), [bff](), [deployment](), [graphql](), [kubernetes](), [microservices](), [mobile-development](), [modular](), [modularity](), [react](), [updates](), [use-cases]() ### AI overview Apollo announces the general availability of Apollo Router and a cloud-hosted build pipeline, alongside recent releases of Federation 2 and Contracts. The article introduces "supergraph" architecture as a unified, modular approach to composing GraphQL APIs, organizational data, microservices, and digital capabilities. ### Source excerpt We've had a busy month at Apollo. Over the last several weeks we've released some significant updates to the Apollo stack. Last month we shipped Federation 2, a sophisticated and more flexible approach to GraphQL composition. And last week we made Contracts generally available, a way to tailor your graph to specific use cases like mobile development or creating public GraphQL APIs. ## Counting over Range Predicates DevFeed: [Counting over Range Predicates]() Original publisher: [Read original article]() Author: Richard Startin's Blog Published: 2022-03-27T00:00:00Z Content type: tutorial Language: en Sources: [Richard Startin's Blog]() Topics: [Java](), [Streams](), [Sorting](), [Benchmark](), [Code]() Tags: [benchmark](), [effective](), [filter](), [inlining](), [java](), [modularity](), [performance](), [roaring](), [sorting](), [streams]() ### AI overview This post examines counting objects that satisfy range and other filters when no database is available. It compares Java's Stream API with specialized Java code and finds that exploiting data already sorted by time can make filtering and counting more efficient. ### Source excerpt This post follows on from my last post about selecting objects satisfying a range predicate, and instead looks at how to count the objects. If you can select objects, you can count them too, but it's a simpler problem so resources can be saved with a specialised solution. ## Introducing Contracts: serve many audiences with a unified graph DevFeed: [Introducing Contracts: serve many audiences with a unified graph]() Original publisher: [Read original article]() Author: Vivek Ravishankar Published: 2021-11-10T10:45:05Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [Graphs](), [Binance](), [Authorization](), [Front end](), [Back end]() Tags: [access-control](), [announcement](), [apis](), [apollo-federation](), [canonical](), [feature](), [modularity]() ### AI overview Apollo introduces Contracts, a preview feature on its Enterprise plan that creates tailored contract graphs by filtering a single unified graph for different audiences. The feature aims to preserve unified-graph benefits while supporting audience-specific schemas, access levels, and experiences. ### Source excerpt At Apollo, we talk a lot about building a unified graph, and for good reason. A unified graph provides incredible benefits - a single source of truth for all services, faster apps, faster delivery, less maintenance overhead, and more. But unification introduces new challenges, especially at scale; "How do I support different experiences and levels of access for different personas or types of users like customers, employees, suppliers, and partners?" "How do I provide my partners and public API... ## Модуляризация iOS-приложения Badoo: борьба с последствиями DevFeed: [Модуляризация iOS-приложения Badoo: борьба с последствиями]() Original publisher: [Read original article]() Author: nsurl-dev (Badoo) Published: 2021-01-21T17:01:19Z Content type: tutorial Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [iOS](), [ci](), [Swift]() Tags: [apple](), [badoo](), [ci](), [cocoapods](), [ios](), [modularity](), [modules](), [objective-c](), [swift](), [tag-73f5f2c76797](), [tag-a3309a813b61](), [tag-d96e238f1419]() ### AI overview This article describes Badoo's experience expanding iOS app modularization and handling the resulting challenges. It covers dependency-graph complexity, CI load, slower application startup as modules increase, monitoring, and an internal Swift command-line utility for automating dependency-graph analysis and fixing typical linking errors. ### Source excerpt В предыдущей статье я рассказывал о том, как мы выделили модуль чата в нашем приложении. Всё прошло успешно, и мы собирались распространить этот опыт -- начать тотальную модуляризацию в iOS-разработке Badoo. Даже презентовали подход продуктовым командам, командам, занимающимся тестированием и непрерывной интеграцией, и постепенно стали внедрять модуляризацию в наши процессы. Мы сразу понимали что будут проблемы, поэтому не торопились и раскатывали решение поэтапно, что помогло нам вовремя понять проблемы о которых пойдет речь далее. В этой статье я расскажу: -- как мы не потерялись в сложном графе зависимостей; -- как спасли CI от чрезмерной нагрузки; -- что делать, если с каждым новым модулем приложение запускается всё медленнее; -- мониторинг каких показателей стоит предусмотреть и почему это необходимо. Читать далее ## Модуляризация iOS-приложения: зачем и как мы разбиваем Badoo на модули DevFeed: [Модуляризация iOS-приложения: зачем и как мы разбиваем Badoo на модули]() Original publisher: [Read original article]() Author: nsurl-dev (Badoo) Published: 2020-12-03T13:26:03Z Content type: article Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [iOS](), [Expo]() Tags: [apple](), [badoo](), [cocoapods](), [ios](), [modularity](), [modules](), [objective-c](), [swift](), [tag-a3309a813b61]() ### AI overview Badoo describes its experience modularizing iOS applications, including how to define modules, organize dependencies, reduce launch time, monitor the process, automate module creation, and prevent linking errors. The article also discusses modularization as an ongoing process involving specialized, reusable modules. ### Source excerpt В iOS-разработке Badoo мы уже несколько лет занимаемся созданием модулей, и большая часть нового кода разрабатывается вне кодовой базы приложений. Сейчас у нас более 100 модулей для Badoo и Bumble. В этой статье я расскажу о нашем опыте и отвечу на самые популярные вопросы о модуляризации: -- по какому принципу выделять модули; -- как организовать связи между ними; -- достаточно ли для фичи одного фреймворка; -- как сократить время запуска многомодульного приложения; -- зачем в этом процессе мониторинг; -- можно ли автоматизировать создание новых модулей и так далее. Мой коллега, лид команды iOS-разработки и Core-команды Артем Лоенко, в начале года говорил об этом на митапе FunCorp в докладе "Катастрофически полезные последствия модуляризации". Я приведу более подробный разбор процесса модуляризации и некоторых опущенных в его рассказе деталей. Читать далее ## Community Detection in Graphs -- a Casual Tour DevFeed: [Community Detection in Graphs -- a Casual Tour]() Original publisher: [Read original article]() Published: 2014-05-19T10:00:32Z Content type: article Language: en Sources: [Jeremy Kun]() Topics: [Graphs](), [Mathematics](), [Algorithms](), [Algorithms, Complexity]() Tags: [approximation](), [approximation-algorithms](), [cliques](), [clustering](), [community-detection](), [erdos-renyi](), [graph](), [graphs](), [mathematics](), [modularity](), [network](), [newman](), [np-hard](), [power-law-distribution](), [random-graph](), [randomized-algorithm](), [technical](), [walktrap]() ### AI overview This introductory article examines community detection in graphs. It explains the informal idea of a community, why defining one precisely and usefully is difficult, and how the clique-based approach leads to computationally intractable problems, including the NP-hardness of finding the largest clique. ### Source excerpt Graphs are among the most interesting and useful objects in mathematics. Any situation or idea that can be described by objects with connections is a graph, and one of the most prominent examples of a real-world graph that one can come up with is a social network. Recall, if you aren't already familiar with this blog's gentle introduction to graphs, that a graph $ G$ is defined by a set of vertices $ V$, and a set of edges $ E$, each of which connects two vertices. ## Modularity in JavaScript MVC Frameworks DevFeed: [Modularity in JavaScript MVC Frameworks]() Original publisher: [Read original article]() Published: 2013-04-07T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [JavaScript](), [mvc](), [Frameworks](), [Highlight.js](), [Single-page application (SPA)](), [Web Development]() Tags: [architecture](), [communication](), [complexity](), [components](), [extend](), [javascript](), [modularity](), [mvc](), [test]() ### AI overview This article explains how modularity can improve JavaScript MVC applications. It presents widgets as atomic components with clear responsibilities and recommends decomposing complex applications into smaller, reusable, testable, and maintainable parts. It also discusses decoupling component communication through event broadcasting, pub/sub, or the Observer pattern. ### Source excerpt Lorem ipsum dolor sit amet