The article explains how the Aura framework handles plugin compilation and packaging by managing shared resources through public.xml, assigning unique package IDs, and offering two solutions—modifying AAPT and using the Gradle aura‑plugin—to achieve small, independent Android plugin bundles.
Guardian 5.0 transforms big‑data security by introducing a standalone service, an enhanced ARBAC model, fine‑grained permission and quota management, visual configuration, unified LDAP/Kerberos authentication, and simplified operations, delivering higher flexibility, availability, and efficiency for enterprise data protection.
This article examines the evolution of frontend development from basic library selection through simple build optimization, modularization, and finally to component‑based development and intelligent static resource management, highlighting engineering practices that improve efficiency, scalability, and performance for complex web applications.
This article explains the major challenges tackled by the Aura Android plugin framework—including component representation, class loading, resource handling, host‑plugin interaction, and packaging—and outlines how solving these enables building a generic, scalable plugin architecture for mobile apps.
The article explains how Baidu Waimai’s CMDB adopts Kubernetes APIServer as a core component to model machine resources as objects, manage their five‑stage lifecycle, and leverage the Watch mechanism for efficient, consistent operations such as hostname changes and fault handling.
This article explains why Java developers must manually close resource objects such as streams and database connections, discusses the limitations of garbage collection, and presents best‑practice techniques like finally blocks, try‑with‑resources, and utility libraries for proper resource management.
This guide explains how Android developers can understand APK structure and apply a range of techniques—such as removing unused resources, compressing images, using vector drawables, and optimizing native code—to significantly reduce the size of their application packages and improve download and install performance.
This article describes how a team migrated Spark 1.6.x running on Mesos to a Marathon‑Docker based architecture that provides dynamic executor scaling, resolves configuration and resource‑allocation issues, and improves monitoring, fault‑tolerance, and upgrade processes for large‑scale streaming workloads.
This article introduces the architecture, key modules, and implementation details of the Little Boy platform, a Greenplum optimization and operations system that parses SQL, applies index and distribution‑key tuning, manages resources, and outlines future enhancements for large‑scale data warehouses.
A seemingly safe configuration swap using barriers caused a crash because a shallow copy duplicated resource pointers, leading to premature freeing of the active configuration; the article explains the bug, shows the faulty code, and presents a corrected approach.
Android app internationalization involves extracting hard‑coded strings into language‑specific strings.xml files, using Lint and regex to locate text, annotating resources, formatting placeholders, exporting for translation, updating the Resources configuration at runtime, handling UI refresh via onConfigurationChanged, recreate or activity restart, and adjusting layouts for length, dimensions, and caps to ensure a seamless multilingual experience.
The talk explains how systematic software performance engineering, through six optimization patterns such as Fast Path, Batching, Flex Path, First Things First, Coupling, and Alternate Routes, can identify and resolve database performance bottlenecks without merely adding more hardware resources.
This guide walks through Linux Container (LXC) resource management, explaining how to control CPU, memory, and storage using cgroup commands, configuration files, and monitoring tools, with step‑by‑step examples and practical tips for efficient container operation.
This tutorial introduces Apache Mesos, Zookeeper, and Marathon, explains their core components and coordination mechanisms, and provides detailed, image‑rich step‑by‑step instructions for setting up a pseudo‑cluster, deploying Docker containers, and managing tasks through the Mesos and Marathon web interfaces.
This article explains Flink's core execution‑resource concepts—including operator chaining, task slots, slot‑sharing groups and co‑location groups—detailing their conditions, API controls, internal implementation, and how they together maximize throughput and resource utilization in stream processing.
The article outlines how to boost system performance through algorithmic refinements, hardware and software resource upgrades, interaction optimizations between algorithms and resources, and effective caching techniques, while acknowledging trade‑offs and the need for balanced decisions.
This article details JD.com's journey from physical servers to a massive Docker‑based cloud‑native platform, covering challenges, architecture, elastic scheduling, monitoring, and resource‑driven operations that support tens of thousands of containers across multiple data centers.
Closing database connections promptly is essential for performance and availability, and this guide explains practical rules, connection‑pool benefits, safe coding patterns, exception handling, and how to diagnose lingering connections using MySQL's SHOW PROCESSLIST command.
This article explains how Ctrip’s Android app adopted a plugin‑based, dynamic‑loading framework to overcome method‑limit, improve build speed, enable hot‑deployment, and support modular A/B testing, detailing the underlying principles, compilation changes, runtime resource and class loading, and the trade‑offs involved.
This article details how the e‑commerce company 1号店 selected the Storm framework to create a low‑cost, highly available, and easily scalable distributed stream‑processing system, covering architecture design, resource isolation with CGroup, custom UI improvements, and operational lessons for handling massive traffic spikes.
This article demystifies PHP’s internal architecture, covering its design philosophy, four‑layer system, SAPI interfaces, execution flow with opcodes, the Zend hash table, variable handling via zval, reference counting, and resource management, providing a comprehensive guide for backend developers.
The article shares the author’s experience designing and operating enterprise‑grade cloud platforms, covering resource and application management, the Platform EGO architecture, comparisons with Mesos, Yarn and Kubernetes, and practical insights on scaling, scheduling, security, and architectural evolution.
This article explores how enterprise‑level web teams can move beyond classic Yahoo performance rules by using hash‑based static asset versioning, dependency‑driven templates, and smart bundling to reconcile engineering constraints with front‑end optimization goals.
This article explains how Docker uses Linux namespaces and cgroups to provide isolation, CPU/memory/I/O control, and monitoring, and includes practical scripts and tips for managing container resources effectively.
This article explains Linux cgroups—its subsystems, hierarchical structure, kernel implementation via VFS, mounting and configuration methods, and practical examples—showing how they provide fine‑grained resource control for processes and containers.
An experienced backend engineer shares practical strategies to prevent service failures, covering third‑party distrust, user‑side safeguards, robust API design, traffic limiting, resource management, and architectural best practices such as single‑responsibility and avoiding single points of failure.
Voidbox integrates Docker containers with YARN to simplify distributed application development, improve deployment, boost cluster efficiency, and provide fault‑tolerant, DAG‑based execution modes, enabling seamless resource management for Hadoop‑based big data jobs.
The article outlines a comprehensive approach to performance tuning by first optimizing algorithms, then enhancing hardware and software environments, and finally improving the interaction between code and resources through load balancing, caching, and I/O reduction, while acknowledging trade‑offs such as consistency and operational complexity.
The article outlines how narrowing operational permissions, automating processes, and adopting data‑center operating systems enhance security, scalability, visibility, and fault handling while reducing manual effort and enabling rapid, low‑risk changes across large infrastructures.
The article reviews Google’s Borg paper, highlighting how Borg distinguishes production and non‑production tasks, manages jobs and containers, improves utilization through mixed‑workload scheduling, enforces isolation via overload and over‑commitment controls, and compares Borg’s approach to other cluster managers.
This guide explains how Linux manages CPU scheduling fairness and demonstrates three practical methods—nice, cpulimit, and control groups—to prioritize, limit, or allocate CPU resources for processes, complete with compilation steps, command examples, and performance observations using top.
In a Baidu technical salon, Xu Liqiang detailed the evolution of Baidu’s private‑cloud platform—covering unified resource pooling, performance‑cost balanced resource management, demand‑driven tiered release, and automated elastic services that together support rapid product‑line iteration across services like Tieba, Community, Search, and Mobile Cloud.
