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
    • README
    • Patterns of Enterprise Application Architecture
    • Principles
    • programming-types
      • Coding to Contract/Interface
      • Links
      • Declarative vs Imperative Programming Languages
      • defensive-programming
      • Design by contract
      • Domain Specific Languages (DSL)
      • Event Driven
      • file-transfers
      • Logical Programming
      • Mutability
      • Self Healing
      • Simplicity
      • Type Driven Design
      • Value objects
      • Aspect Oriented Programming
      • Concurrent and Parallel Programming
        • Actor Model
        • Asynchronous and Synchronous Programming
        • Batch processing
        • Concurrency Models
        • SAP
        • Multithreading
        • Non Blocking IO
        • Optimistic vs Pessimistic Concurrency
        • Thread per connection or request model
        • Actor
        • aysnchronous-tasks
        • barriers
        • design
        • Liveness
        • locks
        • Mutual Exclusion
        • performance
        • synchronization
        • Threads and processes
      • Functional Programming
      • oop-design
      • Reactive Programming
    • 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. programming-types
  3. Concurrent and Parallel Programming

Asynchronous and Synchronous Programming

  • https://simplicable.com/new/asynchronous-processing

  • https://stackify.com/when-to-use-asynchronous-programming/

  • https://www.quora.com/What-is-difference-between-asynchronous-and-synchronous-in-Java

  • https://stackoverflow.com/questions/748175/asynchronous-vs-synchronous-execution-what-does-it-really-mean

  • https://stackoverflow.com/questions/36213948/what-is-the-difference-between-asynchronous-calls-and-callbacks

  • https://stackoverflow.com/questions/14541975/difference-between-future-and-promise

  • https://dzone.com/articles/when-to-use-and-not-to-use-asynchronous-programmin

  • https://www.youtube.com/watch?v=lj4LmG686-I

PreviousActor ModelNextBatch processing

Last updated 6 years ago

Was this helpful?