Working on a note-taking app specially for coders using React! Been at it for 10 days now, almost done. Gonna share it with you guys soon! ?

IntroductionRecursion is one of those things that looks like a simple concept on paper but can quickly turn into a labyrinth of confusion ?. Yet, it's one of the most powerful tools in a programmer's toolbox—if you know how to wield it properly ?. In this article, we’ll dissect recursion, talk about its slightly more optimized cousin, tail recursion, and explore how recursion fits like a glove with recursive data structures. Grab your code editor, your thinking cap, and possibly a cup of coffee (or tea, or whatever helps you think ☕), because we’re about to get recursive ?.What Is Recursion? (And Why Does It Keep Calling Itself? ?)At its core, recursion is a function calling itself to solve smaller instances of a problem. It's like a Russian nesting doll—each smaller doll represents a smaller subproblem, and eventually, you hit a base case, which is your smallest doll (or, in the case of recursion, your "base case") ?.How Does It Work?Let’s start with a classic example: factorial. The factorial of a number n (denoted n!) is the product of all integers from 1 to n. So,n! = n * (n - 1) * (n - 2) * ... * 1In recursion, this would look something like:def factorial(n):
if n == 0: # Base case
return 1
else:
return n * factorial(n - 1) # Recursive callIn this example, the function factorial calls itself with a smaller argument (n-1), and keeps going until n becomes 0, where it hits the base case and starts returning the results ?.Base Case and Recursive Case: The Dynamic Duo ?Every recursive function has two key components:
Base Case: The condition that stops the recursion. Without it, you’ll end up with an infinite loop of function calls that end up crashing your program. Not great ?.
Recursive Case: The part where the function calls itself with modified arguments to reduce the problem size. This is where the magic happens ✨.
The Dark Side of Recursion (aka Memory Problems ?)Recursion is amazing, but like a good superhero, it has its weaknesses. One of the main issues with recursion is memory consumption ?. Each recursive call adds a new "layer" to the call stack, and if you recurse too deeply, you’ll get a stack overflow. It’s like trying to put one too many plates in the dishwasher—it'll break ?.Tail Recursion: The Superhero of Recursion ?‍♂️?Now, imagine a world where recursion doesn’t add to the call stack like an overenthusiastic chef stacking dirty dishes ?. Enter tail recursion. This is where recursion becomes super efficient and can be optimized into an iterative process, saving you memory and processing power ?⚡.What Makes Tail Recursion Special? ?In tail recursion, the recursive call is the last thing that happens before the function returns a result. This allows compilers or interpreters to optimize the recursion by "reusing" the current function's stack frame, which makes the recursion behave more like an iteration—faster and less memory-hungry ?.Here’s the factorial function, but optimized with tail recursion:def factorial_tail(n, acc=1):
if n == 0:
return acc
else:
return factorial_tail(n - 1, acc * n)Notice the difference? We’re passing along an accumulator (acc) to keep track of the result as we go. The function calls itself, but there's nothing left to do after the recursive call—this is the tail call. It’s a recursive function with a clear exit strategy! ?Why Is Tail Recursion Better? ?In non-tail recursion, the function needs to remember all the previous calls, which makes the call stack grow ?. Tail recursion allows the compiler or interpreter to optimize the process by reusing the current stack frame, so you can recalculate huge numbers without blowing up your memory ?.In short, tail recursion is like having your cake and eating it too ?. It gives you recursion’s elegance while still being efficient. Delicious, right? ?Recursive Data Structures: The Perfect Match for Recursion ?Now, let’s talk about recursive data structures, because recursion and recursion-friendly data structures are like peanut butter and jelly ?. They go hand in hand. Some data structures are naturally recursive, which means they’re already structured in a way that makes them perfect for recursion ?.
Linked Lists ?
A linked list is a structure where each element (node) contains a reference to the next node. It’s recursive because each list is essentially a "list" of a single element followed by another list. Here’s a simple recursive traversal of a linked list:def traverse_linked_list(node):
if node is None: # Base case: empty list
return
else:
print(node.value) # Process current node
traverse_linked_list(node.next) # Recursive callEach node is like a mini-problem that points to a smaller problem (next node) ?. So, naturally, recursion fits like a glove ?.
Binary Trees ?
Binary trees are another data structure that’s inherently recursive. Each node has two children (left and right), and those children are themselves trees. If you want to traverse or manipulate a tree, recursion is the most natural way to go. Here’s a simple depth-first search (DFS) traversal:def traverse_tree(node):
if node is None:
return
print(node.value) # Process the current node
traverse_tree(node.left) # Recursive call on the left child
traverse_tree(node.right) # Recursive call on the right childEach node's left and right children are smaller instances of the same tree, which makes recursion a perfect fit ?.
Graphs ?
Graphs are a bit more complex, but recursion still shines through ✨. Whether you’re performing depth-first search (DFS) or exploring connected components, recursion can handle traversals like a champ ?. If you know how to handle recursive traversal of trees, graph traversal isn’t far behind ?‍?.Why Are Recursive Data Structures So Recursion-Friendly? ?‍♂️Well, they are recursive by definition. Each element of the structure points to another instance of the same thing, so solving a problem within them naturally involves breaking it down into smaller, similar subproblems. Recursion is the perfect method for that kind of breakdown ?.ConclusionRecursion is a tool that can make your code elegant, clean, and surprisingly powerful ?. But, like all powerful tools, it requires understanding and caution ?. Enter tail recursion, which optimizes the whole process, and you get a supercharged version of recursion that’s both efficient and effective ?. When you add recursive data structures into the mix, recursion becomes the ultimate problem-solving technique ?.So, the next time you’re faced with a problem that seems too complex to solve with a loop, ask yourself: "Can I break this down recursively?" And if the answer is "Yes," then you’re about to enter the wonderful, infinite (but not too infinite) world of recursion—where every call is just another layer of problem-solving goodness ?. Happy coding! ?‍??‍?

Um dos artíficios importantes no momento do desenvolvimento é poder ter tarefas agendadas que executam assíncronamente. Essas tarefas sempre fazem parte de um domínio de negócio que necessitam executar algo periódicamente. A periodicidade é bem diversa, podendo ser algo a cada 5 segundos ou apenas 1 vez no ano. No desenvolvimento com Spring e/ou Spring Boot, as anotações @EnableScheduling e @Scheduled facilitam a vida do programador há anos.Porém, no últimos tempos, com o desenvolvimento sendo voltado muito ao contexto de microserviços, surgiu um ~probleminha~: quando escalar horizontal a tarefa agendada ser executada em cada nova instância da aplicação.Uma das possibilidades para resolver tal problema é separar a lógica da tarefa agendada em uma nova aplicação não escalável horizontalmente. Sendo essa uma abordagem com prós e contras, com contextos que fazem sentido e outros não.Outra possibilidade é utilizar o ShedLock: uma biblioteca Java com integração ao Spring! Ela possui duas anotações básicas @EnableSchedulerLock e @SchedulerLock que aplicam um lock distribuído nas tarefas/métodos com @Scheduled e fazem com que apenas 1 instância das N rodando execute o que foi agendado.Os recursos que podem prover esse lock distribuído são vários: JDBCTemplate com algum database, MongoDB, S3, etc.Segue link no GitHub de um exemplo com Redis: https://github.com/oigorrudel/shedlock-example