# system-design-project

System design is the practice of specifying a software system's architecture, components, interactions, and functionality.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Fundamentals of Mobile System Design

DevFeed: [Fundamentals of Mobile System Design](<https://devfeed.tech/articles/fundamentals-of-mobile-system-design-141041.md>)

Original publisher: [Read original article](<https://manuelvivo.dev/fundamentals-mobile-system-design>)

Author: Manuel Vivo

Published: 2026-11-18T00:00:00Z

Content type: tutorial

Language: en

Sources: [Manuel Vivo .dev](<https://devfeed.tech/sources/manuel-vivo-dev.md>)

Topics: [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [mobile-app-development](<https://devfeed.tech/topics/mobile-app-development.md>), [mobile-app-performance](<https://devfeed.tech/topics/mobile-app-performance.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [api](<https://devfeed.tech/tags/api.md>), [api-design](<https://devfeed.tech/tags/api-design.md>), [app-size](<https://devfeed.tech/tags/app-size.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [auth](<https://devfeed.tech/tags/auth.md>), [caching](<https://devfeed.tech/tags/caching.md>), [conference](<https://devfeed.tech/tags/conference.md>), [error](<https://devfeed.tech/tags/error.md>), [example](<https://devfeed.tech/tags/example.md>), [feature](<https://devfeed.tech/tags/feature.md>), [framework](<https://devfeed.tech/tags/framework.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [networking](<https://devfeed.tech/tags/networking.md>), [offline](<https://devfeed.tech/tags/offline.md>), [offline-first](<https://devfeed.tech/tags/offline-first.md>), [pagination](<https://devfeed.tech/tags/pagination.md>), [performance](<https://devfeed.tech/tags/performance.md>), [system-design](<https://devfeed.tech/tags/system-design.md>), [talk](<https://devfeed.tech/tags/talk.md>), [talks](<https://devfeed.tech/tags/talks.md>)

### AI overview

The talk presents a four-question framework--scoping, API design, storage, and architecture--for designing mobile features from requirements through rollout, illustrated with a news feed. It covers REST, pagination, authentication, CDNs, push notifications, caching and offline-first design, error handling, optimistic writes, performance, accessibility, security, and app size. The description lists these topics but provides no detailed recommendations or comparison of specific tools.

### Source excerpt

Conference talk

## The AI Delegation Ladder: How Software Development Roles Are Evolving

DevFeed: [The AI Delegation Ladder: How Software Development Roles Are Evolving](<https://devfeed.tech/articles/the-ai-delegation-ladder-how-software-development-roles-are-evolving-128457.md>)

Original publisher: [Read original article](<https://hackernoon.com/the-ai-delegation-ladder-how-software-development-roles-are-evolving?source=rss>)

Author: Sasha Apartsin

Published: 2026-11-11T07:31:11Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Application Development](<https://devfeed.tech/topics/application-development.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [acceptance](<https://devfeed.tech/tags/acceptance.md>), [acceptance-tests](<https://devfeed.tech/tags/acceptance-tests.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-developer-skills](<https://devfeed.tech/tags/ai-developer-skills.md>), [ai-orchestration](<https://devfeed.tech/tags/ai-orchestration.md>), [ai-powered-development](<https://devfeed.tech/tags/ai-powered-development.md>), [ai-workflow-automation](<https://devfeed.tech/tags/ai-workflow-automation.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-tasks](<https://devfeed.tech/tags/coding-tasks.md>), [delegation](<https://devfeed.tech/tags/delegation.md>), [designing](<https://devfeed.tech/tags/designing.md>), [designing-systems](<https://devfeed.tech/tags/designing-systems.md>), [developer-roles](<https://devfeed.tech/tags/developer-roles.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [over](<https://devfeed.tech/tags/over.md>), [roles](<https://devfeed.tech/tags/roles.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [systems](<https://devfeed.tech/tags/systems.md>), [tasks](<https://devfeed.tech/tags/tasks.md>), [vibe-coding](<https://devfeed.tech/tags/vibe-coding.md>)

### AI overview

The excerpt describes a possible shift from implementing AI-assisted code to specifying application behavior and then designing experiences and integrations for AI-run workflows. In Stage 1, developers choose architecture and review generated code, remaining responsible for risks such as incorrect calculations or exposed data. In Stage 2, they define business rules, access policies, and acceptance criteria; ambiguity and tests that miss mistaken interpretations make requirements and assurance central, with detailed code review still needed for critical components. In Stage 3, AI can use authorized data and existing tools to fulfill requests without a dedicated app, while databases, calculations, and access controls still do the underlying work. Developers focus on usable interfaces and reliable integrations with permissions and recovery. The pace may vary: recurring workflows may warrant apps, and critical systems may still need detailed review.

### Source excerpt

As AI takes over coding tasks, developers' roles evolve from designing systems to specifying behavior and designing experiences and integrations.

## How Do You Design a Highly Available Architecture in AWS? A Complete DevOps Engineer's Guide

DevFeed: [How Do You Design a Highly Available Architecture in AWS? A Complete DevOps Engineer's Guide](<https://devfeed.tech/articles/how-do-you-design-a-highly-available-architecture-in-aws-a-complete-devops-engineer-s-guide-127571.md>)

Original publisher: [Read original article](<https://blog.devops.dev/how-do-you-design-a-highly-available-architecture-in-aws-a-complete-devops-engineers-guide-fe49b3cc18d8?source=rss----33f8b2d9a328---4>)

Author: Arvind Verma

Published: 2026-11-10T09:42:59Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [Amazon Route 53](<https://devfeed.tech/topics/amazon-route-53.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [auto-scaling](<https://devfeed.tech/tags/auto-scaling.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloudfront](<https://devfeed.tech/tags/cloudfront.md>), [database](<https://devfeed.tech/tags/database.md>), [design](<https://devfeed.tech/tags/design.md>), [designing](<https://devfeed.tech/tags/designing.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-engineer](<https://devfeed.tech/tags/devops-engineer.md>), [disaster-recovery](<https://devfeed.tech/tags/disaster-recovery.md>), [docker](<https://devfeed.tech/tags/docker.md>), [e-commerce](<https://devfeed.tech/tags/e-commerce.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [high-availability](<https://devfeed.tech/tags/high-availability.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [interview](<https://devfeed.tech/tags/interview.md>), [interview-questions](<https://devfeed.tech/tags/interview-questions.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [load-balancers](<https://devfeed.tech/tags/load-balancers.md>)

### AI overview

A highly available AWS design spreads application components across multiple Availability Zones so a single component or AZ failure does not take down the service. The guide's example uses Route 53 for DNS, WAF for request filtering, an internet facing ALB to route traffic to healthy EC2 targets in private subnets, and an Auto Scaling Group to replace unhealthy instances and adjust capacity. It pairs RDS Multi-AZ failover with application retry and reconnection logic, while noting that a traditional standby is not for read scaling. S3 and CloudFront serve static assets; CloudWatch alarms and SNS notify operators. The guide distinguishes regional high availability from disaster recovery, recommending backups, recovery objectives, cross-Region plans where needed, and tested recovery. It also flags costs, DNS caching delays, NAT Gateway failure dependencies, and the need to test actual failure behavior.

### Source excerpt

From Route 53 and Application Load Balancers to Multi-AZ Auto Scaling, RDS, CloudFront, and Disaster Recovery. Understand how to design AWS infrastructure that survives failures. Imagine you're working as a DevOps Engineer at an e-commerce company. Your application handles thousands of customer requests every minute. Customers are browsing products, placing orders, making payments, and checking delivery status. Everything is working perfectly. Suddenly, one AWS Availability Zone experiences an infrastructure failure. Your EC2 instances become unavailable. Some application requests start failing. Customers cannot access your website. Your engineering manager asks: "How did our entire application become unavailable because one Availability Zone failed?" This is where understanding High Availability (HA) becomes important. A production-ready architecture should not depend on a single EC2 instance, one Availability Zone, one database instance, or one network component. Instead, infrastructure should be designed to tolerate failures, recover automatically, and maintain application availability. In this article, we'll understand how to design a highly available AWS architecture from scratch, including the architecture, AWS services, implementation decisions, production scenarios, and common interview questions. 📘 SECTION 1: UNDERSTANDING HIGH AVAILABILITY AND AWS ARCHITECTURE1. What Is High Availability? High Availability means designing systems that remain accessible and operational even when individual infrastructure components fail. Let's understand with a simple example. Imagine your application runs on one EC2 instance. If that instance crashes, your application becomes unavailable. This is called a Single Point of Failure (SPOF). Now imagine running six EC2 instances across two Availability Zones. Availability Zone A contains three instances. Availability Zone B contains three instances. If Availability Zone A experiences a failure, instances in Availability Zone B

## TimeArch: A Multi-Agent Approach for Software Architecture Design

DevFeed: [TimeArch: A Multi-Agent Approach for Software Architecture Design](<https://devfeed.tech/articles/timearch-a-multi-agent-approach-for-software-architecture-design-120792.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.06921>)

Author: Muhammad Waseem, Mateen Abbasi, Viljami J\\"arvinen, Petrus Lipsanen, Navneet Arora, Kalle Kulonen, Kalle M\\"akel\\"a, Tommi Mikkonen, Pekka Abrahamsson

Published: 2026-11-06T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [Generative AI](<https://devfeed.tech/topics/generative-ai.md>), [system-design-project](<https://devfeed.tech/topics/system-design-project.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-native-software](<https://devfeed.tech/tags/ai-native-software.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [case-studies](<https://devfeed.tech/tags/case-studies.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [governance](<https://devfeed.tech/tags/governance.md>), [multi-agent](<https://devfeed.tech/tags/multi-agent.md>), [prototype](<https://devfeed.tech/tags/prototype.md>), [quality-attributes](<https://devfeed.tech/tags/quality-attributes.md>), [reasoning](<https://devfeed.tech/tags/reasoning.md>), [requirements](<https://devfeed.tech/tags/requirements.md>), [retrieval](<https://devfeed.tech/tags/retrieval.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [traceability](<https://devfeed.tech/tags/traceability.md>)

### AI overview

TimeArch makes the architectural reasoning between requirements and code an explicit, governed lifecycle for GenAI-enabled software development. It combines multi-agent reasoning with retrieval-augmented grounding across requirement definition, architecture design, validation and assurance, and delivery and evolution. The approach aims to capture requirements and architectural drivers, document design decisions, and support traceability. The paper reports a working prototype assessed for feasibility on representative architecture cases from multiple domains with heterogeneous inputs; it gives no detailed results in the supplied text. Comprehensive industrial case studies are identified as future work.

### Source excerpt

arXiv:2611.06921v1 Announce Type: new Abstract: Generative AI is making software implementation faster, but not necessarily better architected. Most current GenAI coding workflows move directly from prompts to code, while the architectural reasoning that should connect requirements, quality attributes, stakeholders, design decisions, and implementation remains weakly supported. Architectural styles, system decomposition, tradeoff analysis, quality-attribute decisions, and stakeholder concerns are often left implicit or handled outside the AI-supported workflow. This creates a missing architectural layer between requirements and code, limiting traceability, validation, and governance in GenAI-enabled software development. This paper presents TimeArch, a multi-agent approach that makes this architectural layer explicit. TimeArch structures software architecture design as a governed lifecycle rather than a one-shot generation task. It combines agent-based reasoning with retrieval-augmented grounding to support requirement definition, architecture design, validation and assurance, and delivery and evolution. The approach supports requirement capture, architectural driver identification, design reasoning, validation, and decision documentation within a traceable process. We demonstrate TimeArch through a working prototype that operationalizes the proposed approach and assess its feasibility using representative software architecture design cases from multiple domains with heterogeneous inputs. As future work, we plan to conduct comprehensive industrial case studies to evaluate the adoption and use of TimeArch in both new and existing software projects. A TimeArch demo is available at: https://sda-assistant.com/. Keywords: AI-native software architecture; requirements-driven software architecture; architectural reasoning; architecture traceability; architecture validation

## Why Magnetic Sensor Selection Has Become a System Architecture Decision

DevFeed: [Why Magnetic Sensor Selection Has Become a System Architecture Decision](<https://devfeed.tech/articles/why-magnetic-sensor-selection-has-become-a-system-architecture-decision-118745.md>)

Original publisher: [Read original article](<https://www.eetimes.com/why-magnetic-sensor-selection-has-become-a-system-architecture-decision/>)

Author: Christopher McGrady

Published: 2026-11-05T09:00:00Z

Content type: article

Language: en

Sources: [EE Times](<https://devfeed.tech/sources/ee-times.md>)

Topics: [system-design-project](<https://devfeed.tech/topics/system-design-project.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [analog](<https://devfeed.tech/tags/analog.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [battery](<https://devfeed.tech/tags/battery.md>), [building](<https://devfeed.tech/tags/building.md>), [business](<https://devfeed.tech/tags/business.md>), [can](<https://devfeed.tech/tags/can.md>), [community](<https://devfeed.tech/tags/community.md>), [designer](<https://devfeed.tech/tags/designer.md>), [designline](<https://devfeed.tech/tags/designline.md>), [digital](<https://devfeed.tech/tags/digital.md>), [education](<https://devfeed.tech/tags/education.md>), [ee-times](<https://devfeed.tech/tags/ee-times.md>), [ee-times-university](<https://devfeed.tech/tags/ee-times-university.md>), [eelife](<https://devfeed.tech/tags/eelife.md>), [eelive-electronic-design](<https://devfeed.tech/tags/eelive-electronic-design.md>), [eet](<https://devfeed.tech/tags/eet.md>), [electrical-engineering](<https://devfeed.tech/tags/electrical-engineering.md>), [electronic-components](<https://devfeed.tech/tags/electronic-components.md>), [electronic-engineering-times](<https://devfeed.tech/tags/electronic-engineering-times.md>), [electronics](<https://devfeed.tech/tags/electronics.md>), [embedded-systems](<https://devfeed.tech/tags/embedded-systems.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [first](<https://devfeed.tech/tags/first.md>), [follow](<https://devfeed.tech/tags/follow.md>), [fundamentals-courses](<https://devfeed.tech/tags/fundamentals-courses.md>), [learning](<https://devfeed.tech/tags/learning.md>), [magnetic](<https://devfeed.tech/tags/magnetic.md>), [mixed-signal](<https://devfeed.tech/tags/mixed-signal.md>), [need](<https://devfeed.tech/tags/need.md>), [news](<https://devfeed.tech/tags/news.md>), [opinion](<https://devfeed.tech/tags/opinion.md>), [part-search](<https://devfeed.tech/tags/part-search.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [product-search](<https://devfeed.tech/tags/product-search.md>), [robot](<https://devfeed.tech/tags/robot.md>), [robotics](<https://devfeed.tech/tags/robotics.md>), [selection](<https://devfeed.tech/tags/selection.md>), [semiconductors](<https://devfeed.tech/tags/semiconductors.md>), [sensing](<https://devfeed.tech/tags/sensing.md>), [sensor](<https://devfeed.tech/tags/sensor.md>), [software](<https://devfeed.tech/tags/software.md>), [solar](<https://devfeed.tech/tags/solar.md>), [sponsored-content](<https://devfeed.tech/tags/sponsored-content.md>), [system](<https://devfeed.tech/tags/system.md>), [system-architecture](<https://devfeed.tech/tags/system-architecture.md>), [tech-papers](<https://devfeed.tech/tags/tech-papers.md>), [technology](<https://devfeed.tech/tags/technology.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

Magnetic sensor choice depends on the whole system's power, accuracy, field strength, interference, mechanical layout, isolation, reliability and cost constraints. The article compares five approaches: Hall is mature, versatile and robust in strong or crowded fields; TMR offers high sensitivity and very low power for weak fields and battery-powered devices; AMR serves low-power switching, angle encoding and wheel-speed sensing; inductive sensing avoids magnets and external-field sensitivity and can improve angular accuracy, at the cost of a custom target and more integration space; fluxgate supports precise current measurement, but performance depends on the customer's complete probe and module. Examples show how architecture shapes implementation: integrated current sensors cover ranges up to ±400 A, while external magnetic structures extend sensing to about 2,000 A; a wide package enables PCB-mounted sensing on 2,000 V platforms. Off-axis encoders address hollow-shaft robot joints, though the highest stated calibration accuracy requires stable constant-speed rotation during assembly. Accuracy over temperature and life also depends on calibration, packaging and production testing,

### Source excerpt

Kiloampere busbars, 2,000 V solar platforms, hollow-shaft robot joints and nanoamp standby budgets are pulling magnetic sensing in directions no single sensing principle can follow. Ask a traction inverter designer, a robotics engineer and someone building a battery-powered water meter what they need from a magnetic sensor, and you will get three answers with very [...] The post Why Magnetic Sensor Selection Has Become a System Architecture Decision appeared first on EE Times.

## Behavioral Questions Are the Biggest Category in Software Engineer Interviews

DevFeed: [Behavioral Questions Are the Biggest Category in Software Engineer Interviews](<https://devfeed.tech/articles/behavioral-questions-are-the-biggest-category-in-software-engineer-interviews-106120.md>)

Original publisher: [Read original article](<https://hackernoon.com/behavioral-questions-are-the-biggest-category-in-software-engineer-interviews?source=rss>)

Author: Amney Mounir

Published: 2026-10-29T07:52:17Z

Content type: news

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [22](<https://devfeed.tech/tags/22.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [adapting](<https://devfeed.tech/tags/adapting.md>), [aggregate](<https://devfeed.tech/tags/aggregate.md>), [ai](<https://devfeed.tech/tags/ai.md>), [behavioral-interview](<https://devfeed.tech/tags/behavioral-interview.md>), [career-advice](<https://devfeed.tech/tags/career-advice.md>), [coding-interview-questions](<https://devfeed.tech/tags/coding-interview-questions.md>), [data](<https://devfeed.tech/tags/data.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [here](<https://devfeed.tech/tags/here.md>), [hiring](<https://devfeed.tech/tags/hiring.md>), [interview](<https://devfeed.tech/tags/interview.md>), [interview-questions](<https://devfeed.tech/tags/interview-questions.md>), [interviews](<https://devfeed.tech/tags/interviews.md>), [job-interview](<https://devfeed.tech/tags/job-interview.md>), [questions](<https://devfeed.tech/tags/questions.md>), [shows](<https://devfeed.tech/tags/shows.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineer](<https://devfeed.tech/tags/software-engineer.md>), [software-engineer-interview](<https://devfeed.tech/tags/software-engineer-interview.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [tech-interviews](<https://devfeed.tech/tags/tech-interviews.md>), [up](<https://devfeed.tech/tags/up.md>)

### AI overview

In Dataford's candidate-submitted Software Engineer reports, behavioral and leadership questions account for about 36% of reported questions (roughly 88,000), compared with about 28% for coding. The article says behavioral questions can appear within technical rounds, helping explain why they are less prominent among guides' headline skills. It recommends preparing six to eight concise work stories, describing each situation, personal actions, outcome, and what could change; using measured results where available; and rehearsing common questions aloud. It suggests spending roughly a third of a four-week preparation period on behavioral practice while continuing coding study. The pattern also appears across other listed tech roles, though their leading categories differ. These figures are approximate: they come from candidate reports, which may not represent all applicants and may recall question types unevenly.

### Source excerpt

Behavioral questions make up about 36% of 245k+ reported Software Engineer interview questions. Here is what the data shows and how to prepare.

## Meta Andromeda: Powering the Next Generation of Ads Retrieval Through Model-System Co-Design

DevFeed: [Meta Andromeda: Powering the Next Generation of Ads Retrieval Through Model-System Co-Design](<https://devfeed.tech/articles/meta-andromeda-powering-the-next-generation-of-ads-retrieval-through-model-system-co-design-105672.md>)

Original publisher: [Read original article](<https://engineering.fb.com/2026/10/28/ml-applications/meta-andromeda-next-gen-ads-retrieval-gpu-co-design/>)

Author: Haiyu Lu; Shuo Gu; Yang Yang (Tony); Jingwen Ren; Tianchen Ji; Qing Zhang; Wentian Guo; Haocheng Wu; Siqi Zeng; Yunchen Pu

Published: 2026-10-28T16:00:01Z

Content type: article

Language: en

Sources: [Engineering at Meta](<https://devfeed.tech/sources/engineering-at-meta.md>), [Meta ML Applications](<https://devfeed.tech/sources/meta-ml-applications.md>)

Topics: [GPU optimization](<https://devfeed.tech/topics/gpu-optimization.md>), [information retrieval](<https://devfeed.tech/topics/information-retrieval.md>), [model architecture](<https://devfeed.tech/topics/model-architecture.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [AI Architecture](<https://devfeed.tech/topics/ai-architecture.md>), [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [Enhancing AI model performance](<https://devfeed.tech/topics/enhancing-ai-model-performance.md>), [quantization](<https://devfeed.tech/topics/quantization.md>)

Tags: [ads](<https://devfeed.tech/tags/ads.md>), [andromeda](<https://devfeed.tech/tags/andromeda.md>), [co-design](<https://devfeed.tech/tags/co-design.md>), [meta](<https://devfeed.tech/tags/meta.md>), [ml-applications](<https://devfeed.tech/tags/ml-applications.md>), [model](<https://devfeed.tech/tags/model.md>), [production-engineering](<https://devfeed.tech/tags/production-engineering.md>), [retrieval](<https://devfeed.tech/tags/retrieval.md>), [system](<https://devfeed.tech/tags/system.md>)

### AI overview

Meta says its Andromeda ads retrieval system combines a mixture-of-experts model with a fused, GPU-based pipeline to score large ad pools efficiently. The model approaches ranking-level performance at roughly 300 times fewer inference FLOPs than the 2024 retrieval model. Fusing model and system operations keeps intermediate data out of high-bandwidth memory; placing targeting-index matching, scoring and top-K selection on one GPU server cuts network traffic by about 100 times. Meta reports production throughput above one billion ads per second per GPU server and a 2.4% increase in Facebook conversions since 2025. In joint Meta-NVIDIA optimization, individual components improved 2-5 times over baseline; INT8 quantization added up to 2 times scoring throughput with accuracy reported on par with 16-bit precision. The post says the full pipeline benchmarks at multiple times current production throughput, while further optimizations and work on Grace Blackwell remain underway.

### Source excerpt

This post describes the next generation of Meta Andromeda, Meta's personalized ads retrieval engine, and how co-designing the model, system, and GPU hardware unlocks a new efficiency frontier for ads retrieval. In production, the system scores every eligible ad with near ranking-level model performance at retrieval scale and surfaces the top candidates at over one [...] Read More... The post Meta Andromeda: Powering the Next Generation of Ads Retrieval Through Model-System Co-Design appeared first on Engineering at Meta.

## System Design in 6 Points, Explained with a Chai Stall That Went Viral

DevFeed: [System Design in 6 Points, Explained with a Chai Stall That Went Viral](<https://devfeed.tech/articles/system-design-in-6-points-explained-with-a-chai-stall-that-went-viral-104372.md>)

Original publisher: [Read original article](<https://ihatereading.in/blogs/system-design-in-6-points-explained-with-a-chai-stall>)

Author: Shrey Vijayvargiya

Published: 2026-10-28T09:00:00Z

Content type: tutorial

Language: en

Sources: [iHateReading](<https://devfeed.tech/sources/ihatereading.md>)

Topics: [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [nginx](<https://devfeed.tech/topics/nginx.md>), [least connections](<https://devfeed.tech/topics/least-connections.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [apache-2-0](<https://devfeed.tech/tags/apache-2-0.md>), [api](<https://devfeed.tech/tags/api.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [backblaze-b2](<https://devfeed.tech/tags/backblaze-b2.md>), [backend](<https://devfeed.tech/tags/backend.md>), [backups](<https://devfeed.tech/tags/backups.md>), [batching](<https://devfeed.tech/tags/batching.md>), [blockchain](<https://devfeed.tech/tags/blockchain.md>), [bsd](<https://devfeed.tech/tags/bsd.md>), [cache](<https://devfeed.tech/tags/cache.md>), [cache-control](<https://devfeed.tech/tags/cache-control.md>), [cache-vs-queue](<https://devfeed.tech/tags/cache-vs-queue.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [coding](<https://devfeed.tech/tags/coding.md>), [development](<https://devfeed.tech/tags/development.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [load-balancer-explained](<https://devfeed.tech/tags/load-balancer-explained.md>), [logs](<https://devfeed.tech/tags/logs.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [object-storage](<https://devfeed.tech/tags/object-storage.md>), [product](<https://devfeed.tech/tags/product.md>), [programming](<https://devfeed.tech/tags/programming.md>), [queue](<https://devfeed.tech/tags/queue.md>), [react](<https://devfeed.tech/tags/react.md>), [read-replicas](<https://devfeed.tech/tags/read-replicas.md>), [read-replicas-explained](<https://devfeed.tech/tags/read-replicas-explained.md>), [retries](<https://devfeed.tech/tags/retries.md>), [retries-with-exponential-backoff-and-jitter](<https://devfeed.tech/tags/retries-with-exponential-backoff-and-jitter.md>), [system-design](<https://devfeed.tech/tags/system-design.md>), [system-design-basics](<https://devfeed.tech/tags/system-design-basics.md>), [system-design-cheat-sheet](<https://devfeed.tech/tags/system-design-cheat-sheet.md>), [system-design-for-beginners](<https://devfeed.tech/tags/system-design-for-beginners.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [web-development](<https://devfeed.tech/tags/web-development.md>)

### AI overview

The article explains six system design patterns through a viral chai stall: cache repeated reads, queue slow background work, balance traffic across healthy app servers, use read replicas for read scaling, store files in object storage behind a CDN, and add timeouts, bounded jittered retries, and structured logs around network calls. It describes key limits: caches can serve stale data and need shared storage across servers; queues defer work and require durable jobs, idempotency, and monitoring; load balancers need shared sessions and can expose database connection limits; asynchronous replicas lag and do not reduce write load; file storage has provider-specific egress costs and private files need signed URLs; retries can duplicate unsafe operations or multiply across layers. Suggested order: logs and timeouts, object storage/CDN, then cache, queue, load balancer, and replicas after query and index fixes.

### Source excerpt

System design basics in six points: cache, queue, load balancer, read replicas, object storage + CDN, and retries with timeouts and logs. One chai stall story,...

## Learn How to Design Software Systems Like a Senior Engineer in Our New Course

DevFeed: [Learn How to Design Software Systems Like a Senior Engineer in Our New Course](<https://devfeed.tech/articles/learn-how-to-design-software-systems-like-a-senior-engineer-in-our-new-course-88818.md>)

Original publisher: [Read original article](<https://www.freecodecamp.org/news/learn-how-to-design-software-systems-like-a-senior-engineer-in-our-new-course/>)

Author: Beau Carnes

Published: 2026-10-16T11:34:26Z

Content type: tutorial

Language: en

Sources: [Free Code Camp](<https://devfeed.tech/sources/freecodecamp-programming-tutorials-python-javascript-git-more.md>)

Topics: [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>)

Tags: [engineer](<https://devfeed.tech/tags/engineer.md>), [framework](<https://devfeed.tech/tags/framework.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [system-design](<https://devfeed.tech/tags/system-design.md>), [youtube](<https://devfeed.tech/tags/youtube.md>)

### AI overview

A free three-hour video course teaches a five-step framework for software system design interviews. It covers clarifying requirements, building high-level architectures using examples such as Spotify and WhatsApp, identifying bottlenecks, estimating storage and traffic, and weighing technical trade-offs.

### Source excerpt

System design is one of the most important skills for software engineers today. Whether you're applying for senior or staff-level positions or just looking to level up your architectural knowledge, un

## How to Create System Design Diagrams using Python

DevFeed: [How to Create System Design Diagrams using Python](<https://devfeed.tech/articles/how-to-create-system-design-diagrams-using-python-77396.md>)

Original publisher: [Read original article](<https://www.freecodecamp.org/news/how-to-create-system-design-diagrams-using-python/>)

Author: Zaira Hira

Published: 2026-10-08T12:13:02Z

Content type: tutorial

Language: en

Sources: [Free Code Camp](<https://devfeed.tech/sources/freecodecamp-programming-tutorials-python-javascript-git-more.md>)

Topics: [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [Python](<https://devfeed.tech/topics/python.md>), [plantuml](<https://devfeed.tech/topics/plantuml.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [backend](<https://devfeed.tech/tags/backend.md>), [cluster-api](<https://devfeed.tech/tags/cluster-api.md>), [database](<https://devfeed.tech/tags/database.md>), [diagram](<https://devfeed.tech/tags/diagram.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [python](<https://devfeed.tech/tags/python.md>), [system-design](<https://devfeed.tech/tags/system-design.md>)

### AI overview

A tutorial on using Python's Diagrams library to create cloud system architecture diagrams as code. It demonstrates creating and connecting nodes, grouping components into clusters, and customizing edges, with examples using AWS resources. The approach supports version control and can generate diagrams in CI/CD or documentation builds.

### Source excerpt

Creating system architecture design diagrams is an important part of technical documentation. As system complexity grows, clarity within teams becomes even more important. But creating diagrams from s

## I Built a LeetCode for Practicing System Design

DevFeed: [I Built a LeetCode for Practicing System Design](<https://devfeed.tech/articles/i-built-a-leetcode-for-practicing-system-design-60550.md>)

Original publisher: [Read original article](<https://blog.algomaster.io/p/practice-system-design>)

Author: Ashish Pratap Singh

Published: 2026-09-27T12:27:25Z

Content type: release

Language: en

Sources: [AlgoMaster Newsletter](<https://devfeed.tech/sources/algomaster-newsletter.md>)

Topics: [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [async](<https://devfeed.tech/topics/async.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [system-design](<https://devfeed.tech/tags/system-design.md>)

### AI overview

AlgoMaster announces practice resources for system design, low-level design, and concurrency, with problems, starter code, test cases, and AI-powered code review. It also describes guided AI mock interviews for system and low-level design.

### Source excerpt

Excited to share new practice resources at algomaster.io to help you go beyond theory and actually implement concepts from system design, low-level design, and concurrency.

## What would the last software engineer still need to do?

DevFeed: [What would the last software engineer still need to do?](<https://devfeed.tech/articles/what-would-the-last-software-engineer-still-need-to-do-79689.md>)

Original publisher: [Read original article](<https://coderabbit.ai/blog/the-last-software-engineer-knows-what-to-build>)

Author: Hendrik Krack

Published: 2026-09-03T00:00:00Z

Content type: article

Language: en

Sources: [CodeRabbit](<https://devfeed.tech/sources/coderabbit.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [human centric design](<https://devfeed.tech/topics/human-centric-design.md>), [Product Management](<https://devfeed.tech/topics/product-management.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-code-review](<https://devfeed.tech/tags/ai-code-review.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [english](<https://devfeed.tech/tags/english.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [ownership](<https://devfeed.tech/tags/ownership.md>), [product](<https://devfeed.tech/tags/product.md>), [system](<https://devfeed.tech/tags/system.md>)

### AI overview

As AI agents take on more coding, Kent C. Dodds argues that engineers' central job is deciding what should be built and owning its effects. That requires understanding user problems and product context alongside the codebase's architecture, data, migrations, and operational limits. He recommends investigating problems directly with users or support before choosing a solution, reviewing system-level decisions and downstream costs rather than syntax alone, and observing results after release. For practice, learn one coding-agent workflow well enough to ship, build deep knowledge of a real system, and avoid overinvesting in workflow techniques that agent platforms may soon absorb.

### Source excerpt

Kent C. Dodds explains why product judgment, system understanding, and ownership become more valuable as AI agents take on more implementation work.

## System Design Interview Framework

DevFeed: [System Design Interview Framework](<https://devfeed.tech/articles/system-design-interview-framework-32316.md>)

Original publisher: [Read original article](<https://evanking1.medium.com/system-design-interview-framework-419b4796e051?source=rss-9736778727ef------2>)

Author: Evan King

Published: 2024-11-19T21:39:41Z

Content type: tutorial

Language: en

Sources: [Evan King](<https://devfeed.tech/sources/evan-king.md>)

Topics: [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [CAP theorem](<https://devfeed.tech/topics/cap-theorem.md>), [X (Twitter)](<https://devfeed.tech/topics/twitter.md>)

Tags: [approach](<https://devfeed.tech/tags/approach.md>), [better](<https://devfeed.tech/tags/better.md>), [cache](<https://devfeed.tech/tags/cache.md>), [client](<https://devfeed.tech/tags/client.md>), [clients](<https://devfeed.tech/tags/clients.md>), [communication](<https://devfeed.tech/tags/communication.md>), [core](<https://devfeed.tech/tags/core.md>), [customer](<https://devfeed.tech/tags/customer.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [design](<https://devfeed.tech/tags/design.md>), [designing](<https://devfeed.tech/tags/designing.md>), [develop](<https://devfeed.tech/tags/develop.md>), [discuss](<https://devfeed.tech/tags/discuss.md>), [ensures](<https://devfeed.tech/tags/ensures.md>), [example](<https://devfeed.tech/tags/example.md>), [framework](<https://devfeed.tech/tags/framework.md>), [interview](<https://devfeed.tech/tags/interview.md>), [system](<https://devfeed.tech/tags/system.md>), [system-design](<https://devfeed.tech/tags/system-design.md>), [system-design-interview](<https://devfeed.tech/tags/system-design-interview.md>)

### AI overview

The framework's central recommendation is to prioritize delivering a working system: use a clear structure to avoid getting stuck. Spend about five minutes clarifying requirements through targeted questions. Identify and prioritize roughly three functional requirements, then choose three to five relevant, contextualized non-functional requirements, quantifying targets where possible. Consider consistency versus availability, environment constraints, scale and traffic patterns, latency, durability, security, fault tolerance, and compliance. The source advises skipping upfront capacity calculations when they would not affect the design, and estimating relevant quantities during design when they could change a choice, such as whether a TopK system needs a sharded data structure. The provided excerpt ends during the functional requirements discussion, while the accompanying source text supplies these later sections.

### Source excerpt

From the co-founder of www.hellointerview.com The easiest way to sabotage your chances of getting an offer in your system design interview is to fail to deliver a working system. This is the most common reason that mid-level candidates fail these interviews. While a firm structure to your approach is important and your interviewer is not trained specifically to assess you on your delivery (often this gets bucketed into "communication"), in practice we've seen many candidates that perform significantly better by following a structure which both keeps them from getting stuck and ensures they deliver a working system. Requirements (~5 minutes) The goal of the requirements section is to get a clear understanding of the system that you are being asked to design. To do this, we suggest you break your requirements into two sections. 1) Functional Requirements Functional requirements are your "Users/Clients should be able to..." statements. These are the core features of your system and should be the first thing you discuss with your interviewer. Oftentimes this is a back and fourth with your interviewer. Ask targeted questions as if you were talking to a client, customer, or product manager ("does the system need to do X?", "what would happen if Y?") to arrive at a prioritized list of core features. For example, if you were designing a system like Twitter, you might have the following functional requirements: Users should be able to post tweets Users should be able to follow other users Users should be able to see tweets from users they follow A cache meanwhile might have requirements like: Clients should be able to insert items Clients should be able to set expirations Clients should be able to read items Keep your requirements targeted! The main objective in the remaining part of the interview is to develop a system that meets the requirements you've identified -- so it's crucial to be strategic in your prioritization. Many of these systems have hundreds of features, but it

## 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](<https://devfeed.tech/articles/ep-2-elevating-software-design-in-go-package-architecture-in-modern-development-22235.md>)

Original publisher: [Read original article](<https://www.ardanlabs.com/blog/2024/05/elevating-software-design-in-go-package-architecture-in-modern-development-ep-2.html>)

Published: 2024-05-21T00:00:00Z

Content type: article

Language: en

Sources: [William Kennedy](<https://devfeed.tech/sources/william-kennedy.md>)

Topics: [Code Modularity](<https://devfeed.tech/topics/code-modularity.md>), [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [code](<https://devfeed.tech/tags/code.md>), [code-modularity](<https://devfeed.tech/tags/code-modularity.md>), [components](<https://devfeed.tech/tags/components.md>), [design](<https://devfeed.tech/tags/design.md>), [designing](<https://devfeed.tech/tags/designing.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [firewalls](<https://devfeed.tech/tags/firewalls.md>), [functionality](<https://devfeed.tech/tags/functionality.md>), [go](<https://devfeed.tech/tags/go.md>), [go-development](<https://devfeed.tech/tags/go-development.md>), [go-projects](<https://devfeed.tech/tags/go-projects.md>), [maintainability](<https://devfeed.tech/tags/maintainability.md>), [modularity](<https://devfeed.tech/tags/modularity.md>), [package](<https://devfeed.tech/tags/package.md>), [package-architecture](<https://devfeed.tech/tags/package-architecture.md>), [package-design](<https://devfeed.tech/tags/package-design.md>), [packages](<https://devfeed.tech/tags/packages.md>), [pitfalls](<https://devfeed.tech/tags/pitfalls.md>), [software](<https://devfeed.tech/tags/software.md>), [software-design](<https://devfeed.tech/tags/software-design.md>)

### AI overview

Bill explains that Go packages create boundaries between program components through encapsulation and modularity, supporting organization and reuse. He recommends packages with focused functionality and warns that generic "Utils" or "Common" packages can weaken code integrity, increase dependencies, and hurt maintainability. The excerpt also introduces a "flipping pyramid" as a caution about monolithic codebases and raises robust type systems as relevant to code integrity and efficiency, without detailing either topic.

### 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.

## Top Meta Software Engineer System Design & Product Architecture Interview Questions 2024

DevFeed: [Top Meta Software Engineer System Design & Product Architecture Interview Questions 2024](<https://devfeed.tech/articles/top-meta-software-engineer-system-design-product-architecture-interview-questions-2024-32317.md>)

Original publisher: [Read original article](<https://evanking1.medium.com/top-meta-software-engineer-system-design-product-architecture-interview-questions-cd0bb56777c0?source=rss-9736778727ef------2>)

Author: Evan King

Published: 2024-05-16T00:34:59Z

Content type: article

Language: en

Sources: [Evan King](<https://devfeed.tech/sources/evan-king.md>)

Topics: [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [Programming](<https://devfeed.tech/topics/programming.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [design](<https://devfeed.tech/tags/design.md>), [interview-questions](<https://devfeed.tech/tags/interview-questions.md>), [interview-tips](<https://devfeed.tech/tags/interview-tips.md>), [meta](<https://devfeed.tech/tags/meta.md>), [software-engineer](<https://devfeed.tech/tags/software-engineer.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [system-design](<https://devfeed.tech/tags/system-design.md>)

### AI overview

A former Meta Staff engineer and interviewer lists design prompts he says are commonly asked in Meta interviews and warns candidates not to memorize answer keys; he recommends using the linked breakdowns to learn concepts and frameworks. The excerpt distinguishes System Design from Product Architecture as interview choices, but only provides a populated System Design list: Ad Click Aggregator, Top K Service, Memcached, FB Live Comments, TAO, Uber, Ticketmaster, and a Distributed Job Scheduler. The full text also shows a Product Architecture list: Ticketmaster, Uber, IG Auction, Dropbox, Newsfeed, Facebook i18n, Newsfeed UX and APIs, Leetcode, and Messenger.

### Source excerpt

I'll cut to the chase, my names Evan, I am a former Meta Staff engineer and interviewer. I've been putting together breakdowns of common problems asked across the top FAANGs. When it comes to the Meta design interview, they let you choose between a System Design interview and a Product Architecture interview. Not sure what the difference is? Checkout this blog post I wrote on the topic. But anyway, I know what you're here for. In my experience, here are the questions that are most commonly asked for each interview type. Read the linked breakdowns, definitely, but these aren't interviews where you can just memorize an answer key, so don't treat them as such. Use them to learn the underlying concepts and frameworks for tackling these types of problems. System Design Design an Ad Click Aggregator Design a Top K Service Design Memcached Design FB Live Comments Design TAO Design Uber Design Ticketmaster Design a Distributed Job Scheduler Product Architecture Design Ticketmaster Design Uber Design IG Auction Design Dropbox Design Newsfeed Design Facebook i18n Design Just the UX and APIs for Newsfeed Design Leetcode Design Messenger

## Ziggurat iOS App Architecture

DevFeed: [Ziggurat iOS App Architecture](<https://devfeed.tech/articles/ziggurat-ios-app-architecture-15968.md>)

Original publisher: [Read original article](<https://developer.squareup.com/blog/ziggurat-ios-app-architecture>)

Author: Square Engineering

Published: 2015-12-18T17:10:00Z

Content type: article

Language: en

Sources: [Square Corner](<https://devfeed.tech/sources/square-corner-blog-medium.md>)

Topics: [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [mvc](<https://devfeed.tech/topics/mvc.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [React Native](<https://devfeed.tech/topics/react-native.md>)

Tags: [animation](<https://devfeed.tech/tags/animation.md>), [app-architecture](<https://devfeed.tech/tags/app-architecture.md>), [architecture-pattern](<https://devfeed.tech/tags/architecture-pattern.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [cognitive-load](<https://devfeed.tech/tags/cognitive-load.md>), [data](<https://devfeed.tech/tags/data.md>), [dependency-injection](<https://devfeed.tech/tags/dependency-injection.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [flow](<https://devfeed.tech/tags/flow.md>), [flux](<https://devfeed.tech/tags/flux.md>), [ios](<https://devfeed.tech/tags/ios.md>)

### AI overview

Ziggurat is a layered Swift app architecture that replaces MVC's loosely defined responsibilities with one-way data flow and immutable view models. A view controller passes user input to a Service, which validates it and is the only layer allowed to mutate state; it signals a Renderer, which asks a Presenter for a view model and sends that model back to the view controllers. The article says this separation can reduce oversized controllers and shared-state bugs, make components easier to test, and support headless operation and portability through dependency injection. Tradeoffs include extra boilerplate, a possible rendering bottleneck, dependency graph complexity, and animation flicker when updates interrupt animations. The author recommends it for apps that use animation sparingly; Flux is described as similar, with React Native addressing animation interruptions.

### Source excerpt

Several steps beyond model view controller

## The properties of crash-only software

DevFeed: [The properties of crash-only software](<https://devfeed.tech/articles/the-properties-of-crash-only-software-12440.md>)

Original publisher: [Read original article](<http://brooker.co.za/blog/2012/01/22/crash-only.html>)

Author: Marc Brooker

Published: 2012-01-22T00:00:00Z

Content type: article

Language: en

Sources: [Marc Brooker's](<https://devfeed.tech/sources/marc-brooker-s-blog.md>)

Topics: [system-design-project](<https://devfeed.tech/topics/system-design-project.md>), [architecture-components](<https://devfeed.tech/topics/architecture-components.md>), [decoupling](<https://devfeed.tech/topics/decoupling.md>), [API](<https://devfeed.tech/topics/api.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [cache](<https://devfeed.tech/tags/cache.md>), [components](<https://devfeed.tech/tags/components.md>), [crash](<https://devfeed.tech/tags/crash.md>), [data](<https://devfeed.tech/tags/data.md>), [design](<https://devfeed.tech/tags/design.md>), [failure](<https://devfeed.tech/tags/failure.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [properties](<https://devfeed.tech/tags/properties.md>), [protocols](<https://devfeed.tech/tags/protocols.md>), [retries](<https://devfeed.tech/tags/retries.md>), [retry](<https://devfeed.tech/tags/retry.md>), [schema](<https://devfeed.tech/tags/schema.md>), [separate](<https://devfeed.tech/tags/separate.md>), [side-channels](<https://devfeed.tech/tags/side-channels.md>), [software](<https://devfeed.tech/tags/software.md>), [state](<https://devfeed.tech/tags/state.md>), [store](<https://devfeed.tech/tags/store.md>), [timeout](<https://devfeed.tech/tags/timeout.md>)

### AI overview

The author presents five crash-only software properties as useful design practices: keep important non-volatile state in dedicated stores; enforce component boundaries through well-defined APIs; put timeouts on calls and limit retries; lease resources instead of allocating them permanently; and make requests self-describing. In the author's interpretation, state should be either explicitly recoverable or clearly disposable, interactions should account for failure rather than wait forever, and requests should carry the context needed to complete them--or rely on a dedicated state store. APIs should also specify idempotency and retry safety.

### Source excerpt

The properties of crash-only software My thoughts about a classic paper Crash-only software by Candea and Fox is a very interesting paper which is well worth your time if you spend any time designing software or services. Re-reading it today, I noticed how useful the section headers of section 3 Properties of Crash-Only Software appear outside the context of the paper. The properties the authors list are: All important non-volatile state is managed by dedicated state stores Components have externally enforced boundaries All interactions between components have a timeout All resources are leased, rather than permanently allocated Requests are entirely self-describing Regardless of what you think of the value of crash-only software, it is difficult to argue with this list of properties. Even outside of the context of the paper, each of these makes sense to me as a good design practice. The way I understand them is like this: All important non-volatile state is managed by dedicated state stores. Either you care about your state or you don't. If you do, store it somewhere safe where it won't get lost and can be recovered quickly in event of failure. If you don't, and your data is either purely volatile or a cache, then be explicit in your design that you don't care about it. Don't half-care about data. Store data explicitly and not implicitly. Components have externally enforced boundaries. Keep logically separate components as separate as possible, ensuring that they don't interact except via a well-defined API. Try to limit implicit side channels. All interactions between components have a timeout. Not only that, but consider the possibility that what you are trying to do will never succeed. All individual calls should have a timeout, and all attempts to retry should be limited. Waiting forever is not a substitute for knowing how to handle failure. All resources are leased, rather than permanently allocated. If you own something, don't give it away to somebody else if