Promessas, futuros e operações assíncronas
Explore padrões de programação assíncrona em Clojure para lidar com tarefas longas e E/S não bloqueante.
Promessas, futuros e operações assíncronas é uma aula grátis de Clojure Functional Programming & JVM Backend Development no CoddyKit. Esta é a aula 3 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Clojure Functional Programming & JVM Backend Development, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Clojure Functional Programming & JVM Backend Development inclui 4 aulas no total.
Partes desta aula ainda não foram traduzidas e aparecem em inglês.
Intro to Asynchronous Programming
Welcome! In this lesson, we'll explore asynchronous programming in Clojure. This is key for building responsive applications that don't freeze while waiting for long tasks.
Asynchronous tasks run in the 'background', allowing your main program to continue without interruption. When the background task finishes, it delivers its result.
Blocking vs. Non-Blocking
Imagine fetching data from a slow server. A blocking operation would make your application wait until the data arrives. During this time, nothing else can happen.
A non-blocking operation starts the fetch but immediately returns control to your application. Your app can then do other things, and process the data once it's available.
Clojure's 'future' Macro
Clojure provides the future macro to run a computation on a separate thread. This makes the computation asynchronous and non-blocking from the caller's perspective.
The future immediately returns a 'future' object, which is a placeholder for the eventual result.
Using 'future' for Async Tasks
Let's see future in action. We'll simulate a long-running task using Thread/sleep. Notice how the "Future started" message appears instantly.
(ns my-app.core
(:gen-class))
(defn -main
"Demonstrates a simple future."
[& args]
(println "Main thread: Starting future...")
(let [f (future
(println " Future thread: Working...")
(Thread/sleep 2000) ; Simulate work
(println " Future thread: Done!")
"Result from Future")]
(println "Main thread: Future started, continuing...")
; We'll learn how to get the result next!
(Thread/sleep 1000) ; Let main thread do other work
(println "Main thread: End of main.")))Getting Results from 'future'
To get the actual value from a future, you dereference it. You can use the @ reader macro or the deref function.
If the future's computation isn't finished yet, dereferencing will block the current thread until the result is ready.
(ns my-app.core
(:gen-class))
(defn -main
"Dereferencing a future."
[& args]
(println "Main thread: Starting future...")
(let [f (future
(println " Future thread: Working...")
(Thread/sleep 2000)
"Long Task Complete")]
(println "Main thread: Future launched.")
(println "Main thread: Doing other work...")
(Thread/sleep 500)
(println "Main thread: Now waiting for future result...")
(let [result @f] ; Dereference the future
(println "Main thread: Future result:" result))
(println "Main thread: All done!")))Clojure's 'promise' Function
While future runs a computation, a promise is a placeholder for a value that will be delivered later, usually by another thread or an external event.
Think of it as an empty box that someone else will fill. You can wait for the box to be filled by dereferencing it.
Delivering and Dereferencing a Promise
The deliver function is used to put a value into a promise. Once a promise is delivered, its value cannot be changed.
Dereferencing a promise works just like a future: it will block until a value is delivered.
(ns my-app.core
(:gen-class))
(defn -main
"Delivering and dereferencing a promise."
[& args]
(let [p (promise)]
(println "Main thread: Created a promise.")
(future
(println " Future thread: Doing async work...")
(Thread/sleep 1500)
(let [val "Value from Future!"]
(println " Future thread: Delivering value to promise.")
(deliver p val)))
(println "Main thread: Waiting for promise to be delivered...")
(let [result @p] ; Blocks until 'deliver' is called
(println "Main thread: Promise received:" result))
(println "Main thread: Program finished.")))Future and Promise Together
future and promise often work together. A future might perform a complex calculation, and then deliver its result to a promise, which can then be picked up by another part of your application.
This pattern is useful for coordinating between different asynchronous tasks or threads.
(ns my-app.core
(:gen-class))
(defn long-calculation []
(println " Calculation: Starting...")
(Thread/sleep 2500) ; Simulate heavy work
(println " Calculation: Finished.")
(* 123 456))
(defn -main
"Coordinating with future and promise."
[& args]
(let [calc-promise (promise)]
(println "Main: Kicking off calculation...")
(future ; Run calculation in a separate thread
(let [result (long-calculation)]
(deliver calc-promise result)))
(println "Main: Calculation started. Doing other things...")
(Thread/sleep 1000)
(println "Main: Still doing other things...")
(println "Main: Waiting for calculation result...")
(let [final-result @calc-promise]
(println "Main: Received final result:" final-result))
(println "Main: Done.")))Error Handling with Async Tasks
When an exception occurs inside a future or before a promise is delivered, dereferencing the future/promise will re-throw that exception on the dereferencing thread.
This allows you to handle errors in your main thread, even if they originate from an asynchronous task.
Quick Check: Async Behavior
Consider the following Clojure code snippet:
(let [f (future (Thread/sleep 1000) "Async Result")]
(println "Started")
(Thread/sleep 500)
(println "Waiting...")
(let [result @f]
(println "Got:" result)))
What is the *minimum* total time before "Got: Async Result" is printed?
Recap: Promises, Futures & Async
- Asynchronous programming allows tasks to run without blocking the main program flow.
- Clojure's
futuremacro runs a computation on a separate thread, returning a placeholder immediately. - The
promisefunction creates a placeholder that can bedelivered a value later, often from another thread or external source. - Both
futureandpromiseare dereferenced (using@orderef) to retrieve their values, blocking if the value isn't ready. - Exceptions in async tasks are re-thrown when dereferenced.
Perguntas Frequentes
A aula “Promessas, futuros e operações assíncronas” é grátis?
Sim — o texto completo de “Promessas, futuros e operações assíncronas” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Clojure Functional Programming & JVM Backend Development, atualize para CoddyKit PRO. O curso de Clojure Functional Programming & JVM Backend Development inclui 4 aulas no total.
O que vou aprender em “Promessas, futuros e operações assíncronas”?
Explore padrões de programação assíncrona em Clojure para lidar com tarefas longas e E/S não bloqueante. Você pratica Clojure Functional Programming & JVM Backend Development com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.
Preciso ter experiência prévia para começar Clojure Functional Programming & JVM Backend Development?
Nenhuma experiência prévia é necessária. Clojure Functional Programming & JVM Backend Development no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 3 de 4.
Quanto tempo leva a aula “Promessas, futuros e operações assíncronas”?
A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.
Posso escrever e executar código nesta aula de Clojure Functional Programming & JVM Backend Development?
Sim. Cada aula de Clojure Functional Programming & JVM Backend Development inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.
Todas as aulas deste curso
- Refs, Agents e Atoms para gerenciamento de estado
- Memória transacional de software (STM)
- Promessas, futuros e operações assíncronas
- Channels e Blocos Go de core.async