Tag view

#architecture

Cross-subject tag search for related interview cards.

Clear

Results update as you type. Press / to jump straight into search.

Tagged with architecture

13 cards

React Medium Theory

Component communication, sibling communication, and composition vs inheritance in React

Data usually flows down from parent to child, while child-to-parent and sibling communication happen through callbacks, lifted state, or shared providers.

  • Parent-to-child uses props
  • Child-to-parent uses callback props
  • Composition is preferred over inheritance in React

Component communication, sibling communication, and composition vs inheritance in React

React Hard Theory

React architecture: project structure, API calls, auth flow, protected routes, environment variables, and deployment basics

React architecture questions test how you organize real applications rather than isolated component syntax.

  • Folder structure should reflect scale and team needs
  • API calls need clear ownership and state handling
  • Protected routes and auth flows must integrate with navigation and data loading

React architecture: project structure, API calls, auth flow, protected routes, environment variables, and deployment basics

React Hard Theory

React coding-adjacent design questions

Many React interviews ask you to reason about UI architecture problems such as search boxes, large lists, debounced input, reusable forms, caching, modal state, theme switching, and optimistic updates.

  • Think in data flow, state ownership, and rendering costs
  • Reuse logic with hooks or composition
  • Separate server state, UI state, and transient interaction state

React coding-adjacent design questions

React Medium Theory

React components: function, class, pure, smart, dumb, and reusable design

React components are reusable UI units, and interviews often compare function components, class components, pure components, and presentation-focused designs.

  • Function components are the modern default
  • Class components still matter for older codebases
  • Good components stay focused and reusable

React components: function, class, pure, smart, dumb, and reusable design

React Hard Theory

React patterns: compound components, provider pattern, custom hooks, container-presentational, and headless UI

React patterns help organize how behavior, layout, and state are shared across components.

  • Compound components coordinate related pieces
  • Providers expose shared capabilities
  • Headless UI separates behavior from styling

React patterns: compound components, provider pattern, custom hooks, container-presentational, and headless UI

React Medium Theory

State management in React: local state, Context, Redux, Flux, Zustand, Recoil, and single source of truth

State management choices in React depend on scale, coordination needs, debugging requirements, and how widely state must be shared.

  • Local state is often enough
  • Flux-inspired tools centralize updates
  • A single source of truth reduces contradictory copies

State management in React: local state, Context, Redux, Flux, Zustand, Recoil, and single source of truth