Learning
Ctrlk
  • Software Engineering Golden Treasury
  • Trail Map
  • Caching
  • Career
  • Computer Science
  • devops
  • General Paradigms
    • CAP theorem
    • designing data-intensive applications summary
    • a-philosophy-of-software-design-notes
    • Aspect oriented Programming (AOP)
    • Best Practice
    • Cargo Cult
    • Clean Code
    • Coding reflections
    • Cognitive Complexity
    • Complexity
    • Conventions
    • Design discussions
    • Design
    • Edge Cases
    • Error Handling Checklist
    • Exceptions
    • Feature Flags/toggle
    • Functional requirements
    • Last Responsible Moment
    • Lock In
    • Named Arguments
    • Naming
    • Performance Fallacy
    • Quality
    • Redesign of a system
    • Resuse vs Decoupling
    • Rules for software designs
    • Sad Paths
    • Scaling Webservices
    • Scientific Method
    • stream-processing
    • Upstream and Downstream
    • Patterns
    • Architecture
    • Design architecture aims
      • back of envelope
      • Design ideas
      • Design mistakes
      • high-volume-design
      • ISO Quality Attributes
      • Non functional requirements
      • “Designing for Performance” by Martin Thompson
      • High Performance
      • Qaulity Attributes
        • Availability
        • System Availability
        • Fault Tolerance
        • interoperability
        • Latency
        • Maintability
        • Modifiability
        • Performance
        • Readability
        • Reliability
        • Scalability vs performance
        • Scalability
        • Scaling
        • statelessness
        • Testability
        • Throughput
      • System Design
      • web-scalability-distributed-arch
    • README
    • Patterns of Enterprise Application Architecture
    • Principles
    • programming-types
    • Projects and Software types
    • State Machines
  • Other
  • Hardware
  • Integration
  • Languages
  • Management & Workflow
  • Networks
  • Operating Systems
  • Other Topics
  • persistance
  • Security
  • Testing, Maintainablity & Debugging
  • Version Control - Git
  • ai
Powered by GitBook
On this page

Was this helpful?

  1. General Paradigms
  2. Design architecture aims
  3. Qaulity Attributes

statelessness

  • https://medium.com/javascript-scene/the-outrageous-cost-of-skipping-tdd-code-reviews-57887064c412

  • https://nordicapis.com/defining-stateful-vs-stateless-web-services/

  • https://stackoverflow.com/questions/5329618/stateless-vs-stateful-i-could-use-some-concrete-information

  • https://www.quora.com/What-is-the-difference-between-Stateful-and-Stateless-Server

  • https://stackoverflow.com/questions/5539823/what-are-the-benefits-of-a-stateless-web-application

  • https://stackoverflow.com/questions/34651801/how-to-make-stateless-web-applications-especially-with-spring-mvc

  • https://softwareengineering.stackexchange.com/questions/346867/how-to-keep-applications-stateless

PreviousScalingNextTestability

Last updated 6 years ago

Was this helpful?