RunWhen is a platform for troubleshooting complex tech stacks. It helps engineers identify when issues they are chasing lie in their app, their cloud-native platform or their vendors by answering the question: “What do I run and when?” With a few minutes of training, the platform scans cloud-native clusters and combines the results with community know-how and the power of generative AI to build Digital Assistants that help app developers and new engineers navigate health metrics and troubleshooting commands before escalating to service owners. With a Stack Overflow style prompt for guidance, it can suggest and run hundreds of commands across a platform and applications. Digital Assistants find issues worthy of deeper attention, building a path forward that the teams involved can review and adjust along the way. With RunWhen, application developers and platform engineers can move quickly from problem identification to problem resolution. Visit runwhen.com/beta to find out more and to sign up for our beta! Don't forget to follow us on Youtube for demos: youtube.com/@whatdoirunwhen

RunWhen

runwhen

FastAPI Got Me an OpenAPI Spec Really... Fast

ফাস্টএপিআই আমাকে একটি ওপেনএপিআই স্পেক দিয়েছে... দ্রুত

FastAPI hat mir wirklich ... schnell eine OpenAPI-Spezifikation besorgt

FastAPI me consiguió una especificación OpenAPI realmente... rápido

FastAPI m'a offert une spécification OpenAPI vraiment... Rapide

FastAPI ने मुझे एक OpenAPI विनिर्देशन वास्तव में... तेजी से दिलाया

FastAPI で OpenAPI 仕様を本当に早く入手できました

FastAPI를 통해 OpenAPI 사양이 정말... 빨라졌습니다.

FastAPI me deu uma especificação OpenAPI muito... rápida

FastAPI дал мне спецификацию OpenAPI действительно... быстро

FastAPI Bana Gerçekten Bir OpenAPI Özelliği Sağladı... Hızlı

FastAPI đã cung cấp cho tôi thông số OpenAPI thực sự... Nhanh

FastAPI 让我快速获得了 OpenAPI 规范

You think that being stuck is a permanent state, and this is the pattern you go through every time: You encounter a new challenge.
Your brain resists it.
It hasn’t been trained to handle discomfort effectively.
You revert to what’s comfortable and familiar.
You shut yourself off from potential growth and enlightenment.
You feel stuck, unfulfilled and unhappy. When you face the challenge of feeling stagnant in your career, in your personal life, nothing seems to help you progress. You feel not just stuck, but regressing. The worst part of it was that in some strange way, it also feels “comfortable” being stuck. I’m sure you have that feeling, because we are wired the same way, and so do I. I wanted to understand why we are so resistant to change, to discomfort. Why is it that it’s easier for us to stay in situations we don’t like while we know damn well it’s not the right path. Why is change hard? Why makes hard things hard? Well, I got some answers while reading a research paper from computational neurobiologist Andrew Gallimore. I finally got a better understanding of how our brain constructs reality, how it cheats us by wanting to save energy, and how we can hack it. 1. Understanding Our Brain: A Reality-Building Machine I won’t bore you with the very technical research paper filled with complicated words and never ending sentences. Here’s a breakdown for you: Central to this process are the cortical columns, functional units within the cerebral cortex that orchestrate your perception of the world. These columns evaluate sensory information against your brain’s existing models, determining “True” or “False” signals to guide your reactions and beliefs. To put this even simpler, They work like little decision-makers in the outer layer of the brain, sorting through what we see and feel. They check this information against what the brain already knows, deciding if it matches (“True”) or doesn’t match (“False”). This helps you figure out how to react and what to believe. Here’s the problem: Your brain and its cortical columns are designed to conserve energy at all costs. This means they’re constantly seeking “True” statements, those that align with what you already know and believe. Why? Because processing familiar information requires less energy than assimilating new data. This is precisely why staying in your comfort zones feels so… comfortable. It’s not just inertia; it’s a battle against a highly efficient computer in your head, always seeking stability over the chaos of change. Your gut might scream for a shift, but you’re up against your brain’s design, which chooses energy conservation over everything else. 2. The Mannequin Misidentification: A Cortex in Action Ok ben, that sounds cool and I get the theory. But how does this actualise, and how is it shaping my reality? Here’s an example: Imagine walking down a street, your eyes catch what appears to be a figure standing in a shop window. Your brain utilizes past data, and quickly categorizes this figure as a man — a “True” response rooted in familiarity. You continue to walk closer, until something happens.. you realize that the figure is not a person, but in fact a mannequin. This unexpected twist sends a “False” signal to your brain, specifically to those cortical columns tasked with visual processing. Faced with this new information, your brain recalibrates, updating your reality from a man to a mannequin. 3. Embracing the Science of Uncomfortability So there we have it. The path to growth is through embracing “False” signals — those challenging, unfamiliar experiences that demand our brain to adjust and grow. This process isn’t just about acquiring new information; it’s about fundamentally reshaping our perception and interaction with the world around us. It’s about changing reality; literally asking your cortex to re-evaluate your current reality, and change it. That’s why it feels so hard. That’s why it feels so weirdly good to stay stuck. So, what are some steps to hack this? 4. Recognizing the State of “Brain Automation” Well, first, you need to understand when you’re stuck in “brain automation”. I’m sure you know this feeling very well. You’re in that state when you go through your daily routines without much thought or variation. You wake up, get dressed, get coffee at the same spot, order the same drink. Tasks and activities feel mundane, and you’re not engaged or stimulated by what you’re doing. You are bored. You wake up every morning saying “ok here we go, another day doing the same thing until I get to go to sleep again. Let’s just get through it with as many distractions as possible.” Nothing seems to make you feel alive. You are just in automation mode. Activities that used to hold your attention don’t mean anything anymore. 5. Breaking Through with Challenging Thoughts Now that you recognize the signs of “brain automation,” the next step isn’t just about what you do; it’s about how you think. Changing your actions without changing your thoughts is like repainting your car when it needs a new engine. Sure, it will look good on the outside, it still won’t run though. So do this: Ask why, and don’t judge. “Why” is such a short but powerful question that can almost always be used successively until the truth is met: “I feel stuck in my career? Why? …Because I don’t like what I do. Why? …Because it doesn’t challenge me or align with my values. Why? …Because I settled into a role that was available rather than pursuing what genuinely interests me. Why? …Because I fear the uncertainty of change and the possibility of failure. Why? …Because past experiences have conditioned me to prioritize security over fulfillment. Why? …Because I internalized the belief that success is defined by stability rather than personal satisfaction and growth.” Take this and keep asking the same question. You’ll get to the root of it soon enough. In this instance, your feeling of being stuck is less about the external circumstances and more about internal barriers — fears, beliefs, and assumptions that keep you tethered to the familiar, however unsatisfying it may be. 6. No, but really.. How do I get unstuck? Listen. True transformation begins when you push beyond the boundaries of what you know and where you’re comfortable. The shift needs to happen in your head, but also physically. You need to consciously and repetitively seek out “False” signals and embrace the discomfort they bring. You need to construct a new reality. In plain, simple terms, you need to: do the uncomfortable thing. Here are a few of the things I have had to do last week alone that finally led me to break out of my cycle: I impulssively bought a plane ticket to Panama, to change my enviroment, create some space for me to:
Sit with my feelings for the first time in years, and finally stop supressing them. I cried. Haven’t done that in years.
I had the uncomfortable conversation with my business partner to tell them I no longer have passion for it and am leaving them the decision to continue or quit.
I made the decision to get a therapist and seek help to access past trauma that I’ve burried deep down.
I replied "I don't know" when asked about something I was unsure of, rather than trying to appear confident. I felt stupid that instant, but I actually learned something and ended up having a meaninful conversation.
I forced myself to talk to strangers every single day. Oh, and talking happened to be in Spanish, for which my vocabulary consisted of a total of 40 words or so. These things were uncomfortable. These things were all dreadful for me. They are supposed to be. They are hard, they are counter-intuitive, and they are painful. But if you don’t do them, you are letting your cortex run on auto-pilot, validating a “true” statement that will feel comfortable. Yes, in the immediate short term, it feels better. But you are reinforcing your mind into shaping the wrong reality. Do that long enough, and you will soon be living in a world that is not yours. You’ll have a job you hate, relationships that don’t support you, a deep lack of purpose, numbing yourself to the world around you until you become nothing more than a ghost, aimlessly drifting through a suffocating and meaningless existence. Waking up to it 10 years later will be very painful. So Wake up. Challenge yourself. Engineer your existence and break free. You think that being stuck is a permanent state, and this is the pattern you go through every time: You encounter a new challenge. Your brain resists it. It hasn’t been trained to handle discomfort effectively. You revert to what’s comfortable and familiar. You shut yourself off from potential growth and enlightenment. You feel stuck, unfulfilled and unhappy. You encounter a new challenge. Your brain resists it. It hasn’t been trained to handle discomfort effectively. You revert to what’s comfortable and familiar. You shut yourself off from potential growth and enlightenment. You feel stuck, unfulfilled and unhappy. When you face the challenge of feeling stagnant in your career, in your personal life, nothing seems to help you progress. You feel not just stuck, but regressing. The worst part of it was that in some strange way, it also feels “comfortable” being stuck. I’m sure you have that feeling, because we are wired the same way, and so do I. I wanted to understand why we are so resistant to change, to discomfort. Why is it that it’s easier for us to stay in situations we don’t like while we know damn well it’s not the right path. Why is change hard? Why makes hard things hard? Well, I got some answers while reading a research paper from computational neurobiologist Andrew Gallimore. I finally got a better understanding of how our brain constructs reality, how it cheats us by wanting to save energy, and how we can hack it. 1. Understanding Our Brain: A Reality-Building Machine I won’t bore you with the very technical research paper filled with complicated words and never ending sentences. Here’s a breakdown for you: Central to this process are the cortical columns, functional units within the cerebral cortex that orchestrate your perception of the world. These columns evaluate sensory information against your brain’s existing models, determining “True” or “False” signals to guide your reactions and beliefs. To put this even simpler, They work like little decision-makers in the outer layer of the brain, sorting through what we see and feel. They check this information against what the brain already knows, deciding if it matches (“True”) or doesn’t match (“False”). This helps you figure out how to react and what to believe. Here’s the problem: Your brain and its cortical columns are designed to conserve energy at all costs. This means they’re constantly seeking “True” statements, those that align with what you already know and believe. Why? Because processing familiar information requires less energy than assimilating new data. This is precisely why staying in your comfort zones feels so… comfortable. It’s not just inertia; it’s a battle against a highly efficient computer in your head, always seeking stability over the chaos of change. Your gut might scream for a shift, but you’re up against your brain’s design, which chooses energy conservation over everything else. 2. The Mannequin Misidentification: A Cortex in Action Ok ben, that sounds cool and I get the theory. But how does this actualise, and how is it shaping my reality? Here’s an example: Imagine walking down a street, your eyes catch what appears to be a figure standing in a shop window. Your brain utilizes past data, and quickly categorizes this figure as a man — a “True” response rooted in familiarity. You continue to walk closer, until something happens.. you realize that the figure is not a person, but in fact a mannequin. This unexpected twist sends a “False” signal to your brain, specifically to those cortical columns tasked with visual processing. Faced with this new information, your brain recalibrates, updating your reality from a man to a mannequin. 3. Embracing the Science of Uncomfortability So there we have it. The path to growth is through embracing “False” signals — those challenging, unfamiliar experiences that demand our brain to adjust and grow. This process isn’t just about acquiring new information; it’s about fundamentally reshaping our perception and interaction with the world around us. It’s about changing reality; literally asking your cortex to re-evaluate your current reality, and change it. That’s why it feels so hard. That’s why it feels so weirdly good to stay stuck. So, what are some steps to hack this? 4. Recognizing the State of “Brain Automation” Well, first, you need to understand when you’re stuck in “brain automation”. I’m sure you know this feeling very well. You’re in that state when you go through your daily routines without much thought or variation. You wake up, get dressed, get coffee at the same spot, order the same drink. Tasks and activities feel mundane, and you’re not engaged or stimulated by what you’re doing. You are bored. You wake up every morning saying “ ok here we go, another day doing the same thing until I get to go to sleep again. Let’s just get through it with as many distractions as possible .” ok here we go, another day doing the same thing until I get to go to sleep again. Let’s just get through it with as many distractions as possible Nothing seems to make you feel alive. You are just in automation mode. Activities that used to hold your attention don’t mean anything anymore. 5. Breaking Through with Challenging Thoughts Now that you recognize the signs of “brain automation,” the next step isn’t just about what you do; it’s about how you think. Changing your actions without changing your thoughts is like repainting your car when it needs a new engine. Sure, it will look good on the outside, it still won’t run though. So do this: Ask why, and don’t judge. “Why” is such a short but powerful question that can almost always be used successively until the truth is met: “I feel stuck in my career? Why? “I feel stuck in my career? Why? …Because I don’t like what I do. Why? …Because I don’t like what I do. Why? …Because it doesn’t challenge me or align with my values. Why? …Because it doesn’t challenge me or align with my values. Why? …Because I settled into a role that was available rather than pursuing what genuinely interests me. Why? …Because I settled into a role that was available rather than pursuing what genuinely interests me. Why? …Because I fear the uncertainty of change and the possibility of failure. Why? …Because I fear the uncertainty of change and the possibility of failure. Why? …Because past experiences have conditioned me to prioritize security over fulfillment. Why? …Because past experiences have conditioned me to prioritize security over fulfillment. Why? …Because I internalized the belief that success is defined by stability rather than personal satisfaction and growth.” …Because I internalized the belief that success is defined by stability rather than personal satisfaction and growth.” Take this and keep asking the same question. You’ll get to the root of it soon enough. In this instance, your feeling of being stuck is less about the external circumstances and more about internal barriers — fears, beliefs, and assumptions that keep you tethered to the familiar, however unsatisfying it may be. 6. No, but really.. How do I get unstuck? Listen. True transformation begins when you push beyond the boundaries of what you know and where you’re comfortable. The shift needs to happen in your head, but also physically. You need to consciously and repetitively seek out “False” signals and embrace the discomfort they bring. You need to construct a new reality. In plain, simple terms, you need to: do the uncomfortable thing . do the uncomfortable thing Here are a few of the things I have had to do last week alone that finally led me to break out of my cycle: I impulssively bought a plane ticket to Panama, to change my enviroment, create some space for me to: Sit with my feelings for the first time in years, and finally stop supressing them. I cried. Haven’t done that in years. I had the uncomfortable conversation with my business partner to tell them I no longer have passion for it and am leaving them the decision to continue or quit. I made the decision to get a therapist and seek help to access past trauma that I’ve burried deep down. I replied "I don't know" when asked about something I was unsure of, rather than trying to appear confident. I felt stupid that instant, but I actually learned something and ended up having a meaninful conversation. I forced myself to talk to strangers every single day. Oh, and talking happened to be in Spanish, for which my vocabulary consisted of a total of 40 words or so. I impulssively bought a plane ticket to Panama, to change my enviroment, create some space for me to: Sit with my feelings for the first time in years, and finally stop supressing them. I cried. Haven’t done that in years. I had the uncomfortable conversation with my business partner to tell them I no longer have passion for it and am leaving them the decision to continue or quit. I made the decision to get a therapist and seek help to access past trauma that I’ve burried deep down. I replied "I don't know" when asked about something I was unsure of, rather than trying to appear confident. I felt stupid that instant, but I actually learned something and ended up having a meaninful conversation. I forced myself to talk to strangers every single day. Oh, and talking happened to be in Spanish, for which my vocabulary consisted of a total of 40 words or so. These things were uncomfortable. These things were all dreadful for me. They are supposed to be. They are hard, they are counter-intuitive, and they are painful. But if you don’t do them, you are letting your cortex run on auto-pilot, validating a “true” statement that will feel comfortable. Yes, in the immediate short term, it feels better. But you are reinforcing your mind into shaping the wrong reality . wrong reality wrong reality Do that long enough, and you will soon be living in a world that is not yours. You’ll have a job you hate, relationships that don’t support you, a deep lack of purpose, numbing yourself to the world around you until you become nothing more than a ghost, aimlessly drifting through a suffocating and meaningless existence. Waking up to it 10 years later will be very painful. So Wake up. Challenge yourself. Engineer your existence and break free.

The Illusion of Being Stuck

আটকে থাকার বিভ্রম

Die Illusion, festzustecken

La ilusión de estar estancado

L'illusion d'être coincé

फँस जाने का भ्रम

行き詰まっているという幻想

갇혀 있다는 환상

A ilusão de estar preso

Иллюзия застревания

Sıkışmış Olma Yanılsaması

Ảo tưởng bị mắc kẹt

陷入困境的错觉

It may not have been the cuts that some speculators had hoped for back in Q4, but the news that the US Federal Reserve were set to cut rates three times throughout 2024 helped to push all three major stock indexes towards new record highs following its March meeting. The prospect of rate cuts will be music to the ears of risk-taking investors, with the prospect of greater confidence levels and stronger liquidity helping to drive markets higher. Riding the wave of good news was the Dow Jones Industrial Average, S&P 500, and the Nasdaq Composite, all of which added posted of between 0.2% and 0.7% as the anticipation of upcoming cuts grew. healthy gains Although the Fed opted to keep rates unchanged in March, new forecasts confirmed plans for three 25-basis-point rate cuts in 2024 in a move that improved optimism throughout Wall Street. Federal Reserve Chair Jerome Powell also hinted that rate cuts will take place provided that the US economy continues to grow as expected, and downplayed the impact of the in inflation that took place in January and February. As a result, markets anticipate a of a rate cut arriving by June. unexpected rises 72% chance The largely optimistic note saw Wall Street’s chip stocks perform exceptionally well, with Nvidia (NASDAQ:NVDA) soaring to yet further highs while the positive sentiment dovetailed for Micron Technology’s (NASDAQ:MT) stock which has now shown Q1 growth of 45% following an report. impressive earnings Provided that the Fed’s anticipation of economic growth meets expectations, it’s likely that higher flows of investor optimism will manifest itself in Wall Street’s tech stocks and various riskier plays that would’ve seemed too hot to handle as recently as 2022. So, is it time for the good times to roll once more? Winning the Battle with Inflation Throughout 2022 and 2023, the economic landscape throughout the US was punctuated by a hawkish monetary policy from the Federal Reserve. Soaring inflation prompted by the post-pandemic recovery and supply chain squeezes throughout industries saw inflation peak at 9.1% in June 2022. By late 2023, optimism began to grow that rate hikes may finally be over, and that cuts may be on the way as soon as Q1 2024. However, January and February of the new year brought more concern. Inflation began to rise unexpectedly, causing more investors to fear that expectations over cuts may be short lived. Despite this, Powell highlighted that recent inflation worries were likely down in part to ‘seasonal effects,’ and although the bank would take the available data seriously, it shouldn’t impact its transition into a more dovish stance. "It certainly hasn't raised anyone's confidence; but I would say that the story is really essentially the same, and that is of inflation coming down gradually toward 2% on a sometimes bumpy path," . explained Powell "We've got nine months of 2.5% inflation now. We've had two months of bumpy inflation; it's going to be a bumpy ride." While the anticipation of cuts has seen investor sentiment become more positive on Wall Street, other investors have sought to move quickly in of advantageous interest rates while they’re still available. taking advantage According to fund tracker EPFR, $22.8 billion has flooded into corporate bond funds in 2024 before anticipated rate cuts impacted yields. The data represents the brightest start to a year since 2019. Big Tech Wins Investor Confidence Wall Street’s brightening outlook saw in the wake of the Fed’s March meeting. US stock futures rally Futures for the Dow Jones Industrial Average advanced 30 points, or 0.1%, the S&P 500 gained 0.2%, and the tech-oriented Nasdaq climbed 0.3% moving into the quieter Easter Weekend period for markets as investors began to bet on clearing skies over US stocks. Crucially, this growing interest in the performance of US markets falls in-line with more bullish revisions of where indexes like the S&P 500 is likely to be by the end of the year. Notably, John Stoltzfus, chief investment strategist at Oppenheimer, has raised expectations for the S&P 500 by 5% to a year ending benchmark of 5,500–representing a strong increase on the initial specified target of 5,200. "All of the above prompts us to increase our year-end price target acknowledging the possibility that we might need to raise the target price again later this year should this economic and market outlook prove us too conservative in our projections," . wrote Stoltzfus Even more bullish is the prediction of a team of Goldman Sachs strategists led by David Kostin who suggested that the S&P 500 could be driven to thanks to big tech rallies in one scenario where megacaps foster growth of 15%. 6,000 this year However, the team also highlighted one prospective scenario that could see the index crash to 4,500. The End of Risk? Although markets have become more optimistic off the back of the Federal Reserve’s March meeting, the performance of inflation between now and June will have a major impact on whether investors retain their confidence in Wall Street’s megacap tech stocks. Another confounding factor may be the continued escalation of geopolitical tensions and a prospective tumultuous presidential election in November, which could be intensified should it become a close-run event. There’s also the danger that markets have already long factored in the inevitability of rate cuts, meaning that there may be less distance to run when the hotly anticipated cuts finally occur. “It is important to realise that the market has changed the paradigm from ‘will there be a rate cut?’ to ‘when?’,” , head of investment research at Freedom Finance Europe. explained Maxim Manturov “In other words, the markets have built into expectations a rate cut soon, and even if it comes later, from a fundamental perspective it won't have much of an impact given the solid Q4 gains for much of the S&P 500 index. And even though expectations for a Fed rate cut have been pushed back to a later date, the threat of a rate hike is off the table for now.” While we’re likely to see the positive sentiment flow back into Wall Street as expectations for rate cuts continue to grow, the impact they’ll have on the risky stocks that have helped to facilitate such a strong end to 2023 may have already been priced in. This means that optimism should be balanced with caution in navigating the Fed’s new dovish stance.

Risk Appetite Floods Back Into Wall Street as Rate Cut Confidence Soars for Investors

ঝুঁকির ক্ষুধা বন্যা ওয়াল স্ট্রিটে ফিরে এসেছে কারণ বিনিয়োগকারীদের জন্য রেট কাটের আস্থা বেড়েছে

Die Risikobereitschaft kehrt an die Wall Street zurück, da das Vertrauen der Anleger in Zinssenkungen steigt

El apetito por el riesgo vuelve a inundar Wall Street a medida que aumenta la confianza de los inversores en el recorte de tipos

L’appétit pour le risque revient à Wall Street alors que la confiance des investisseurs en matière de réduction des taux monte en flèche

निवेशकों के लिए दर में कटौती का विश्वास बढ़ने से वॉल स्ट्रीट में जोखिम की भूख फिर से बढ़ गई है

投資家の利下げに対する信頼感が高まる中、リスク選好がウォール街に再び流入

투자자들의 금리 인하 신뢰도가 높아지면서 위험에 대한 욕구가 다시 월스트리트에 몰려들고 있습니다.

O apetite pelo risco volta a Wall Street à medida que aumenta a confiança dos investidores no corte de taxas

Аппетит к риску возвращается на Уолл-стрит, поскольку уверенность инвесторов в снижении ставок растет

Yatırımcılara Faiz İndirimi Güveni Arttıkça Risk İştahı Wall Street'e Yeniden Taşındı

Sự thèm muốn rủi ro tràn trở lại Phố Wall khi niềm tin cắt giảm lãi suất tăng vọt đối với các nhà đầu tư

投资者对降息信心飙升，风险偏好重回华尔街

PS: This story was written in my indigenous language, Pidgin English, a variant of English. I hope you enjoy it. -All misfortune ends up as stories eventually For the longest time, I wanted to run. When you read this, I hope you understand why I did what I did. And you won’t curse me, too. When I was young, I fell in love with various kinds of food. I hated wastage, so I ate whatever I came across, full or not. They called me a glutton and many unflattering names, but my thick hide remained unruffled. Different foods meant the world to me until I found spaghetti. It’s not what you think, no. It’s beguiling and strips you of common sense. The first time I became addicted to spaghetti, the world tilted on its axis. I was floating. Let’s start at the very day my world came unraveled. “Every time carbohydrate. You go dey chop like baby pig, yet e no dey show for your body. Pankere wọ gown.” Mama said when she walked up to me, a laundry basket under her arms with rolls of fat. “Sorry, mama,” I said, slowing down my food. The apartment is tiny and meant to be stuffy, but Mama makes it work somehow. “My pikin, eat o. But eat a balanced diet, eh? I no wan make you get kwashiorkor. E no look good for body. Na so so head and belle remain. You need fat, even if na small. I go buy milk for you when I come back from the market. That milk, wetin dem dey call am again?” Her memory was sometimes glitchy, and I always came to her aid. “Na Complan.” “Ehn ehn, Complan. Na, im be that. You need am make you add flesh for your body.” But what is a twelve-year-old supposed to know about such? Mama goes to do the laundry, and I sit in front of the television, stomach rumbling. “Open the door, person dey knock,” Mama said from the backyard. Her ears are sharper than the talons of a predator on most days. “Nnena, how are you?” A woman in Mama’s size sizes me up, tying her wrapper correctly. “Fine, ma.” I was courteous even though I’d never seen her before. “Your mama no dey?” She asked, trying to peek inside the house. I hold the door firmly, dissuading her from such an act. “She dey backyard,” I responded, not budging an inch. Mama has told me many times not to let strangers in. No matter how they seem. “Okay, I just say make I greet. Before I forget, you fit to give her this? Tell am say na the new product wey come out.” She handed me a sealed product, and my eyes widened when I spotted the name. It was spaghetti. “Who be that?” Mama comes into the room, drying her hands on her wrapper. “I no know o. She just dropped this thing.” I pointed, and Mama’s eyes relaxed. “Ah, na Mama Nedu na. You no know her? She dey sell spaghetti. She say she go drop by.” I heave a breath of relief, staring at the pack of spaghetti, daring me to move forward. I cooked it the next day. Delicious doesn’t even begin to describe it. It finished a little too fast, and I stared disappointed at my empty plate, licked until it shone like the back of Nnamdi’s head. We all laughed when he came to school with a shaved head, and I never forgot ever since. I cooked it again. I was spending the cash I’d been saving for the festivities of Christmas. It finished—all 3,450 naira of it. The withdrawal symptoms started innocently enough when I hallucinated a plate of spaghetti. I reached for it, but it wasn’t there anymore. I hiss at the eba, not knowing what to do. I ate rice that night. And my life changed forever. I could feel a bubbling sensation in my stomach, as though my entrails were being pulled out of my body, acid searing through my stomach’s lining. “Jesus, wetin? Talk to me! My pikin ooo, make una help me o.” Mama rushed me into her arms, cradling my head with such fondness. I could feel my ribs digging into me. “Wetin happen?” Papa Njedika was the first to answer the call, his wife a few feet behind him. “She just begin to convulse. Her body temperature just dey rise. I no know wetin to do. My God oo, make una come o.” And Mama slips into hysteria again. “Make we carry her go hospital; we go figure out the bills later.” Mama nods, letting Papa Njedika remove me from her grasp. I could see the agony create lines on her face. But I was unconscious. Outside my body, watching me. And fear wears me like a sweater. I was dead. ~~ Being dead didn’t feel terrible, until I touched a lone thread. A thread of white and red was before me, and the non-corporeal world filled up my vision. The chairs were in their first form; a tree stood where all the chairs were, and I found myself standing in a forest. Dense. Silent. Alive. The trees encompass the world, stretching forth into eternity. Whichever way I turned, a forest greeted me. The two threads were on the ground, and I knew I couldn’t touch more than one. It was a choice. I was making a choice. I picked the red. Cliché, but it worked. I was carried into the air as though I weighed less than a feather, and I kept rising until I was above the clouds. And the world was before me. I moved, wondering what would happen if I fell from such a stupendous height. Was there a way to die a second death? I didn’t want to find out. My eyesight had no barriers; I could see the entire world simultaneously. “Child of the Stars, what are you doing here?” I heard a voice from the world, and my eyes almost rolled to the back of my head. “I think I died,” I say, turning 360 to see if I could catch a glimpse of the speaker—no such luck. “Yes, but this isn’t your path to follow. Why did you choose this path?” The voice asked again. I’d already gotten over my fear, and I was feeling irritated instead. “Is there meant to be a tutorial or something? Because I didn’t receive one.” The voice chuckled—light and all-encompassing. “Okay, Child of the Stars. Look no further. Remember who you are.” The voice said with a tone of finality and faded out of existence. Curious. After waiting for a few minutes, I got bored and began to touch the trees around me. They felt like they had a soul, as though the world stole their individuality. “What are you trying to tell me?” I whisper, cradling its bark. A purring sound reverberated around me as though waking the world from its slumber. One by one, the trees made groaning sounds, moving as one. “What’s going on?” I screamed, and they turned to me suddenly. “Child of the Stars, you’ve awoken us from our slumber. We have seen what humans have done, and we rise. No longer playthings, no longer useless. Thank you for waking the Soul of the World. Goodbye, we won’t see you again.” The world faded to black, and I opened my eyes groggily, staring at my mother's worried face. “What happened?” I asked, the mother of all headaches deciding to visit me. “My pikin don wake!” Mama screams, hugging me. Papa Njedika and his wife run into the room, looking at me with worry creasing their foreheads. The hospital waiting room seemed to be full of people. People I didn’t even know. “You’re fine now,” Mama said, but I wondered. Three days after I got home, missiles were launched into China and the US, even though there was a non-aggression pact between the World Powers. “The missiles moved like they had a mind of their own.” The president of the US made that statement, looking stupid on live television. But when Switzerland launched a missile, the world began to listen. A neutral country was calling for war. It was darker than people thought. I needed to get back to the non-corporeal world; I needed to right my wrongs. So, I ate spaghetti until I almost passed out. Nothing. I starved myself for days on end, my body worse than it was before. Nothing still. My body was refusing to die. When I dreamt, I saw the Soul of the World standing before me, eyes filled with malice. It was no longer a giant mass of trees; it was a human with eyes as deep as the universe. No, not a figure of speech. The universe was its eyeballs. “Why do you worry, Child of the Stars? They deserve it.” It says, looking down on me with contempt. “But, I’m part of the world too.” I reasoned, but the look it leveled me with was enough to incinerate. “And?” There was no remorse in its voice. “Stop, please,” I beg. “Why should I? You still use plates: books, wood. You take from us and give nothing in return. No homage, no love. You’re human, too. Born in this age, how can you be anything else? Goodbye. We won’t meet again.” “No. We will.” I stared at the Soul of the World, pleading. It smiled briefly and disappeared. “What have I done?” I asked, feeling the weight settle over my soul. “I don’t know, what have you done?” I heard a cheery voice, the same one from before. “How do I fix this?” I scream at the void, my voice not getting past two feet in front of me. “You can’t. This was your purpose all along. I like the bit with spaghetti, though I found it funny. But now, you must wake. Even stars have to face what it means to fall.” The world shattered, and I woke up with tears in my eyes. My mother was beside me, looking older than I’d ever seen her. She had grey hair. “Mama?” I asked, turning around to be sure I was in the right place. Everything looked so unfamiliar. Mama woke up with a start. She saw me and fainted. People rushed into the room, and they ran out when they saw me awake. “What’s happening?” I didn’t know whether to cry or be worried. Papa Njedika was the only person brave enough to talk to me. He approached me and hesitated but placed his hand on my shoulder. “We’re the last of Nigeria. And this is 2025. The Third World War.” It was my turn to faint. But I didn’t. I’d slept for ten years. And the world had ended. All because of spaghetti.

Spaghetti 

scurries onto the database scene as a resilient and scalable distributed SQL database. Drawing inspiration from the tenacity of its insect namesake, CockroachDB boasts high availability even in the face of hardware failures. Its distributed architecture spans multiple nodes, mirroring the adaptability of its insect counterpart. CockroachDB With strong consistency and ACID transaction support, CockroachDB becomes a reliable choice for applications requiring data accuracy and reliability, thriving in dynamic environments and effortlessly managing the complexities of distributed data. This blog introduces using MinIO as a changefeed sink for CockroachDB. By doing so, you not only benefit from CockroachDB's strengths but also leverage the , , and of MinIO. Use this as a guide to establishing an enterprise-grade CDC strategy. It is inspired by awesome repo. durability scalability performance this What is CDC? CDC is a smart database management technique that tracks and captures changes in a relational database like CockroachDB. It acts like a monitor, detecting CRUD Operations like INSERTS, UPDATES and DELETES in real time. CDC's strength lies in its ability to identify only the altered data, making it more efficient in terms of network bandwidth and expense than traditional methods of replication. This efficiency is crucial for tasks like data integration, real-time analytics, and maintaining consistency across distributed systems. CDC is truly a prerequisite for real-time connected data fabrics and remains a fundamental tool for keeping databases synchronized and maintaining reliability in dynamic data environments. This continuous stream of real-time data updates provides a rich foundation for training and optimizing machine learning models which require huge volumes of up-to-date data for success. Changefeed Sinks with CockroachDB in CockroachDB are like data pipelines that efficiently funnel CRUD operations happening in the database to an external destination. In this instance, MinIO serves as one such destination. When configured as a sink, MinIO becomes the repository for the continuous stream of changes, offering a durable and scalable storage solution for CDC operations. Changefeed sinks One benefit of this approach is that you can use CDC data in your MinIO bucket to replicate your data strategy across clouds. For example, If your CockroachDB is hosted in AWS, but you need your data on-prem for your models to run, you can do that with this approach. This can be an effective way to implement a multi-cloud data strategy. Prerequisites To follow this guide, make sure you have Docker Compose installed. You can install Docker Engine and Docker Compose separately or together using Docker Desktop. The easiest way is to go for Docker Desktop. Check if Docker Compose is installed by running this command: docker-compose --version You will need a self-hosted, Enterprise license of CockroachDB. For this local deployment of CockroachDB, please note that CockroachDB on ARM for MacOS is experimental and is not yet ready for production. Getting Started To get started clone or download the project folder from location. this Open a terminal window, navigate to the project folder and run the following command: docker-compose up -d This command instructs Docker Compose to read the configuration from the `docker-compose.yml` file, create and start the services defined in it, and run them in the background, allowing you to use the terminal for other tasks without being tied to the container's console output. After running the command you should be able to see the containers are up and running. You can access the Cockroach UI at . Verify that your node is live. http://127.0.0.1:8080 You can access the MinIO UI at . Log in with the username and password combination of . http://127.0.0.1:9001 minioadmin:minioadmin Once you log in, you should be able to verify that the mc command in the was executed and a bucket named was automatically created. docker-compose.yml cockroach SQL Commands Once your containers are up and running, you’re now ready to run SQL commands. Run the following command in a terminal window in the same folder where you downloaded the tutorial files and started your containers. This command executes an interactive SQL shell inside the container, connecting to the CockroachDB instance running in that container, and allowing you to enter SQL queries. crdb-1 docker exec -it crdb-1 ./cockroach sql --insecure You should see the following if you executed the shell correctly. #
# Welcome to the CockroachDB SQL shell.
# All statements must be terminated by a semicolon.
# To exit, type: \q.
#
# Server version: CockroachDB CCL v19.2.2 (x86_64-unknown-linux-gnu, built 2019/12/11 01:33:43, go1.12.12) (same version as client)
# Cluster ID: 0a668a2d-056d-4203-a996-217ca6169f80
#
# Enter \? for a brief introduction.
# As noted in the prerequisites, you need an Enterprise CockroachDB account to set up CDC. Use the same terminal window to enter the next commands. SET CLUSTER SETTING cluster.organization = '<organization name>';

SET CLUSTER SETTING enterprise.license = '<secret>';

SET CLUSTER SETTING kv.rangefeed.enabled = true; Crushing CDC You can now build your database and tables. The SQL below creates a new database named , switches the current database context to , creates a table named to store information about machine learning models, and inserts two rows of data into this table representing the performance metrics of specific models. Execute these commands in the same terminal. ml_data ml_data model_performance CREATE DATABASE ml_data;

SET DATABASE = ml_data;

CREATE TABLE model_performance (
     model_id INT PRIMARY KEY,
     model_name STRING,
     accuracy FLOAT,
     training_time INT);

INSERT INTO model_performance VALUES
   (1, 'NeuralNetworkV1', 0.85, 120),
   (2, 'RandomForestV2', 0.92, 150); Next, run the following command to create a changefeed for the table in CockroachDB and configure it to stream updates to MinIO. model_performance CREATE CHANGEFEED FOR TABLE model_performance INTO 'experimental-s3://cockroach?AWS_ACCESS_KEY_ID=minioadmin&AWS_SECRET_ACCESS_KEY=minioadmin&AWS_ENDPOINT=http://minio:9000&AWS_REGION=us-east-1' with updated, resolved='10s'; Navigate to the Cockroach UI at to verify that your changefeed has been successfully created and a high-water timestamp has been established. http://127.0.0.1:8080 Make a change to your data to see the changefeed in action. UPDATE model_performance SET model_name = 'ResNet50' WHERE model_id = 1; Run the following command to make sure the command was executed. SELECT * FROM model_performance ;
  model_id |   model_name   | accuracy | training_time  
+----------+----------------+----------+---------------+
         1 | ResNet50       |     0.88 |           130  
         2 | RandomForestV2 |     0.92 |           150 In a production environment, your transactions would populate MinIO without the need for this step. Navigate back to the MinIO UI at‘ to see your changefeed in action. http://127.0.0.1:9001 End of the Line In this tutorial, you’ve gone through the process of creating a changefeed sink with MinIO to enable a CDC strategy for your enterprise-licensed CockroachDB. This CDC strategy sets the stage for a and continuously synchronized data fabric for your most critical data. When you absolutely need to have a perfect replica of your data for data exploration, analytics or AI applications the combination of CockroachDB and MinIO is your winning strategy. resilient Evolve what has been outlined here and you will continue to support better decision-making, facilitating AI/ML endeavors, and maintaining the reliability of your dynamic data environment. MinIO today for all your cockroach-related needs. MinIO - CockroachDBs check-in, but they don't check out. Reach out to us if you have any questions or trouble with bugs at or on . Download hello@min.io Slack I want to thank the folks at CockroachDB – big shoutout to John Billingsley – for helping us with this post.

Never the One to Die: Persistent Data with a CDC MinIO Sink for CockroachDB

If you need to run operations before completing a Git commit, you can rely on Git Hooks. Git hooks are scripts that run automatically whenever a particular event occurs in a Git repository. They let you customize Git’s internal behaviour and trigger customizable actions at key points in the development life cycle. Extending Git hooks allows you to plug in to the regular Git flow, such as Git , , etc. custom functionalities message validation code formatting I’ve already described how to use , but here I’m gonna use , the version of Husky created for .NET-based applications. Husky with NPM Husky.NET Git hooks: a way to extend Git operations As we said, Git hooks are actions that run during specific phases of Git operations. Git hooks fall into : 4 categories : they execute when you run on your local repository; client-side hooks related to the committing workflow git commit : they are executed when running , which is a command that allows you to integrate mails and Git repositories (I’ve never used it. If you are interested in this functionality, ); client-side hooks related to the email workflow git am here’s the official documentation : these hooks run on your local repository when performing operations like ; client-side hooks related to other operations git rebase : they run after a commit is received on the remote repository, and they can reject a operation. server-side hooks git push Let’s focus on the client-side hooks that run when you commit changes using . git commit How to install Husky.NET and its dependencies in a .NET Application Husky.NET must be installed in the of the solution. root folder You first have to by running: create a file in the root folder tool-manifest dotnet new tool-manifest This command creates a file named under the folder: here, you can see the list of external tools used by dotnet. dotnet-tools.json .config After running the command, you will see that the file contains this element: dotnet-tools.json {
  "version": 1,
  "isRoot": true,
  "tools": {}
} Now you can by running: add Husky as a dotnet tool dotnet tool install Husky After running the command, the file will contain something like this: {
  "version": 1,
  "isRoot": true,
  "tools": {
    "husky": {
      "version": "0.6.2",
      "commands": ["husky"]
    }
  }
} Now that we have added it to our dependencies, we can by running: add Husky to an existing .NET application dotnet husky install If you open the root folder, you should be able to see these 3 folders: , which contains the info about the Git repository; .git that contains the description of the tools, such as ; .config dotnet-tools that contains the files we are going to use to define our Git hooks. .husky Finally, you can by running, for example, add a new hook dotnet husky add pre-commit -c "echo 'Hello world!'"
git add .husky/pre-commit This command creates a new file, (without file extension), under the folder. By default, it appears like this: pre-commit .husky #!/bin/sh
. "$(dirname "$0")/_/husky.sh"

## husky task runner examples -------------------
## Note : for local installation use 'dotnet' prefix. e.g. 'dotnet husky'

## run all tasks
#husky run

### run all tasks with group: 'group-name'
#husky run --group group-name

## run task with name: 'task-name'
#husky run --name task-name

## pass hook arguments to task
#husky run --args "$1" "$2"

## or put your custom commands -------------------
#echo 'Husky.Net is awesome!'

echo 'Hello world!' The default content is pretty useless; it’s time to customize that hook. Notice that the latest command has also generated a file; we will use it later. task-runner.json Your first pre-commit hook To customize the script, . open the file located at .husky/pre-commit Here, you can add whatever you want. In the example below, I run commands that compile the code, format the text (using with the rules defined in the .editorconfig file), and then run all the tests. dotnet format #!/bin/sh
. "$(dirname "$0")/_/husky.sh"

echo 'Building code'
dotnet build

echo 'Formatting code'
dotnet format

echo 'Running tests'
dotnet test Then, add it to Git, and you are ready to go. 🚀 But wait… 3 ways to manage dotnet format with Husky.NET There is a problem with the approach in the example above. Let’s simulate a usage flow: you modify a C# class; you run ; git commit -m "message" the pre-commit hook runs ; dotnet build the pre-commit hook runs ; dotnet format the pre-commit hook runs ; dotnet test after the hooks, the commit is created. What is the final result? Since modifies the source files, and given that the snapshot has already been created before executing the hook, all ! dotnet format the modified files will not be part of the final commit Also, executes linting on every file in the solution, not only those that are part of the current snapshot. The operation might then take a lot of time, depending on the size of the repository, and most of the time, it will not update any file (because you’ve already formatted everything in a previous run). dotnet format We have to work out a way to fix this issue. I’ll suggest three approaches. Include all the changes using Git add The first approach is quite simple: after . run git add . dotnet format So, the flow becomes: you modify a C# class; you run ; git commit -m "message" the pre-commit hook runs ; dotnet build the pre-commit hook runs ; dotnet format the pre-commit hook runs ; git add . the pre-commit hook runs ; dotnet test Git creates the commit. This is the most straightforward approach, but it has some downsides: is executed on every file in the solution. The more your project grows, the slower your commits become; dotnet format adds to the current snapshot all the files modified, even those you did not add to this commit on purpose (maybe because you have updated many files and want to create two distinct commits). git add . So, it works, but we can do better. Execute a dry run of dotnet-format You can to the command: this flag returns an error if at least one file needs to be updated because of a formatting rule. add the --verify-no-changes dotnet format Let’s see how the flow changes if one file needs to be formatted. you modify a C# class; you run ; git commit -m "message" the pre-commit hook runs ; dotnet build the pre-commit hook runs ; dotnet format --verify-no-changes the pre-commit hook returns an error and aborts the operation; run on the whole solution to fix all the formatting issues; you dotnet format you run ; git add . you run ; git commit -m "message" the pre-commit hook runs ; dotnet build the pre-commit hook runs . Now, there is nothing to format, and we can proceed; dotnet format --verify-no-changes the pre-commit hook runs ; dotnet test Git creates the commit. Notice that, this way, if there is something to format, the whole commit is aborted. You will then have to run on the entire solution, fix the errors, add the changes to the snapshot, and restart the flow. dotnet format It’s a longer process, but it allows you to have complete control over the formatted files. Also, you won’t risk including in the snapshot the files you want to keep staged in order to add them to a subsequent commit. Run dotnet-format only on the staged files using Husky.NET Task Runner The third approach is the most complex but with the best result. If you recall, during the initialization, Husky added two files in the folder: and . .husky pre-commit task-runner.json The key to this solution is the file. This file allows you to . task-runner.json create custom scripts with a name, a group, the command to be executed, and its related parameters By default, you will see this content: {
  "tasks": [
    {
      "name": "welcome-message-example",
      "command": "bash",
      "args": ["-c", "echo Husky.Net is awesome!"],
      "windows": {
        "command": "cmd",
        "args": ["/c", "echo Husky.Net is awesome!"]
      }
    }
  ]
} To make sure that runs only on the staged files, you must like this: dotnet format create a new task {
  "name": "dotnet-format-staged-files",
  "group": "pre-commit-operations",
  "command": "dotnet",
  "args": ["format", "--include", "${staged}"],
  "include": ["**/*.cs"]
} Here, we have specified a name, , the command to run, , with some parameters listed in the array. Notice that parameter, which is populated by Husky.NET. dotnet-format-staged-files dotnet args we can filter the list of files to be formatted by using the ${staged} We have also added this task to a named that we can use to reference a list of tasks to be executed together. group pre-commit-operations If you want to run a specific task, you can use . In our example, the command would be . dotnet husky run --name taskname dotnet husky run --name dotnet-format-staged-files If you want to run a set of tasks belonging to the same group, you can run . In our example, the command would be . dotnet husky run --group groupname dotnet husky run --group pre-commit-operations The last step is to call these tasks from within our file. So, replace the old command with one of the above commands. pre-commit dotnet format Final result and optimizations of the pre-commit hook Now that everything is in place, we can improve the script to make it faster. Let’s see which parts we can optimize. The first step is the . For sure, we have to run to see if the project builds correctly. You can consider adding the flag to skip the step before building. build phase dotnet build --no-restore restore Then we have the : we can avoid formatting every file using one of the steps defined before. I’ll replace the plain with the execution of the script defined in the Task Runner (it’s the third approach we saw). format phase dotnet format Then, we have the . We can add both the and the flag to the command since we have already built everything before. ! The format phase updated the content of our files, so we still have to build the whole solution. Unless we swap the and the phases. test phase --no-restore --no-build But wait build format So, here we have the final file: pre-commit #!/bin/sh
. "$(dirname "$0")/_/husky.sh"

echo 'Ready to commit changes!'

echo 'Format'

dotnet husky run --name dotnet-format-staged-files

echo 'Build'

dotnet build --no-restore

echo 'Test'

dotnet test --no-restore

echo 'Completed pre-commit changes' Yes, I know that when you run the command, you also build the solution, but I prefer having two separate steps just for clarity! dotnet test Ah, and at the beginning of the script! don’t remove the #!/bin/sh How to skip Git hooks To trigger the hook, just run . completing the commit, the hook will run all the commands. . git commit -m "message" Before If one of them fails, the whole commit operation is aborted There are cases when you have to . For example, if you have integration tests that rely on an external source currently offline. In that case, some tests will fail, and you will be able to commit your code only once the external system gets working again. skip the validation You can skip the commit validation by adding the flag: --no-verify git commit -m "my message" --no-verify Further readings Husky.NET is a porting of the Husky tool we already used in a previous article, using it as an NPM dependency. In that article, we also learned how to customize Conventional Commits using Git hooks. 🔗 How to customize Conventional Commits in a .NET application using GitHooks | Code4IT As we learned, there are many more Git hooks that we can use. You can see the complete list on the Git documentation: 🔗 Customizing Git - Git Hooks | Git docs Of course, if you want to get the best out of Husky.NET, I suggest you have a look at the official documentation: 🔗 Husky.Net documentation One last thing: we installed Husky.NET using dotnet tools. If you want to learn more about this topic, I found an excellent article online that you might want to read: 🔗 Using dotnet tools | Gustav Ehrenborg Wrapping up In this article, we learned how to create a Git hook and validate all our changes before committing them to our Git repository. pre-commit We also focused on the formatting of our code: how can we format only the files we have changed without impacting the whole solution? I hope you enjoyed this article! Let’s keep in touch on or ! 🤜🤛 Twitter LinkedIn Happy coding! 🐧 Also published . here

Optimizing .NET Development Workflow with Git Hooks and Husky.NET

Carbon Aware Computing: Next Green Breakthrough or New Greenwashing?

কার্বন সচেতন কম্পিউটিং: পরবর্তী গ্রিন ব্রেকথ্রু বা নতুন গ্রিনওয়াশিং?

CO2-bewusstes Computing: Nächster grüner Durchbruch oder neues Greenwashing?

Computación consciente del carbono: ¿próximo avance ecológico o nuevo lavado verde?

Informatique respectueuse du carbone : prochaine percée verte ou nouveau greenwashing ?

कार्बन अवेयर कंप्यूटिंग: अगला ग्रीन ब्रेकथ्रू या नया ग्रीनवाशिंग?

カーボン アウェア コンピューティング: 次のグリーン ブレークスルーか、それとも新たなグリーンウォッシングか?

탄소 인식 컴퓨팅: 차세대 친환경 혁신인가 아니면 새로운 Greenwashing인가?

Computação Consciente do Carbono: Próximo Avanço Verde ou Nova Lavagem Verde?

Вычисления с учетом выбросов углерода: следующий «зеленый прорыв» или новое «зеленое отмывание»?

Karbon Farkında Bilgi İşlem: Bir Sonraki Yeşil Atılım mı, Yeni Bir Yeşil Yıkama mı?

Máy tính nhận biết carbon: Đột phá xanh tiếp theo hay tẩy xanh mới?

碳感知计算：下一个绿色突破还是新的绿色清洗？

React is a component-based library, so you can build interactive apps one component at a time. Components are separate pieces of UI, but still interconnected. Props is a React feature that allows components to receive and pass data, similar to how you’d pass an argument to a function. This allows us to build complex apps with React. In this article, we’ll explore how to use props to pass a function from parent to child components. If you enjoy learning about React, my blog has 50+ . React tutorials Pass a Function via Props in React Let’s see how to do this in 3 simple steps. Define the function First, we need to create a function in the parent component. Most of the time, we pass down functions to handle events in child components, so let’s create a simple event handler. onClick const handleClick = console.log("you just clicked a button") When a user clicks a button, our event handler will simply log a message to the console. Pass the function via props The syntax for setting props is similar to setting an attribute. You can think of props as custom attributes for components in React. To pass a function, you can simply reference the name of the variable that stores the function. In this case, that would be variable. handleClick <childComponent handler={handleClick} /> In this case, the name of the prop (the custom attribute) is . Curly braces are necessary to set its value to a JavaScript expression ( variable holds the function). handler handleClick Do not call the function when you pass it via props. Only pass a reference to a function. Otherwise, the function will run when you don’t want it to (every time the component is rendered). Important: Call the function in the child component Now, let’s call the function passed to the child component via props. Functional components must accept props as an argument. Props is an object where properties and values correspond to props and values passed to the component. In this case, the object has one property - and its value will be the function. props handler You can call the function using dot notation - or you can use new syntax and destructure props object. props.handler() Why Should You Pass a Function via Props? Keeping track of changes in the state and props is very important in React. Storing user data in one component makes your app more consistent and error-free. Usually, this component needs to be at (or near) the top of the component tree, so it can store child components’ internal data. This concept is often called the ‘Single Source of Truth.’ It’s also common to store user inputs in the state. Input elements are usually in child components, and logic is handled in the parent component. You need some way to get data from input elements to the parent component. Props are strictly uni-dimensional - parent components can pass data (or, like in this case, a function) to child components, but the latter can not pass data up to parent components. React developers often pass event handlers to child components, which pass arguments to event handlers that update the state of the parent component.

How to Pass A Function via Props in React

Hi there! This is a continuation of my for stress testing your services. The documentation mentions that the main engine for load is Phantom, but it can be replaced with Pandora if you need to create unique test scenarios or work with other types of requests (such as grpc or any other binaries). In this article, we will explore how to integrate Yandex Pandora for two cases: first article on how to use Yandex Tank GRPC flatbuffer (over http) As I mentioned before, our main goal is to use a simple tool with straightforward documentation that doesn’t require hiring a bunch of people to set up the test. Pandora, like Tank, has very simple and understandable documentation, does exactly what we need, and has a low entry threshold. In my case, the primary stack is Golang, and I choose solutions around it. https://hackernoon.com/turbocharge-load-testing-yandextank-ghz-combo-for-lightning-fast-code-checks?embedable=true Let’s start by referring to the documentation and see what Pandora is all about. “Pandora is a high-performance load generator in the Go language. It has built-in HTTP(S) and HTTP/2 support, and you can write your own load scenarios in Go, compiling them just before your test.” Since we are interested in scenarios, let’s take a look at the documentation: https://yandex.github.io/pandora/eng/custom.html?source=post_page-----12c250f2bff2--------------------------------&embedable=true As we can see from the documentation, there is an excellent example of how to write our “gun” to create our load engine. Great, let’s take this example and copy-paste it into our repository. Next, let’s look at our service contracts: syntax = "proto3";

option go_package = "/docs";

service DocumentService {
 rpc GetAllByLimitAndOffset(GetAllRequest) returns (GetAllResponse) {}
 rpc Save(SaveRequest) returns (SaveResponse) {}
 rpc Validate(ValidateRequest) returns (ValidateResponse) {}
} Our task involves covering two methods ( ): yes, we’ll skip save method for current case Save Validate Create a Yandex-tank folder, create a GRPC folder inside it, move our PROTO file there, and generate contracts with the command: protoc - go_out=./docs - go_opt=paths=source_relative \
 - go-grpc_out=./docs - go-grpc_opt=paths=source_relative docs.proto After that, we will get files as shown in the screenshot. And now, let’s start to write our own gun. We have to add a huge number of imports and create a struct for Custom params: package main

import (
 "context"
 "log"
 "strconv"
 "time"

 _ "github.com/golang/protobuf/ptypes/timestamp"
 "github.com/spf13/afero"
 "google.golang.org/grpc"
 pb "grpc-gun/docs"

 "github.com/yandex/pandora/cli"
 "github.com/yandex/pandora/components/phttp/import"
 "github.com/yandex/pandora/core"
 "github.com/yandex/pandora/core/aggregator/netsample"
 "github.com/yandex/pandora/core/import"
 "github.com/yandex/pandora/core/register"
)

type Ammo struct {
 Tag    string
 Param1 string
 Param2 string
 Param3 string
} Now, we should add and where we can add our grpc client (just copy and paste from official docs) GunConfig Gun, type GunConfig struct {
 Target string `validate:"required"` // Configuration will fail, without target defined
}

type Gun struct {
 // Configured on construction.
 client grpc.ClientConn
 conf   GunConfig
 // Configured on Bind, before shooting
 aggr core.Aggregator // Maybe your custom Aggregator.
 core.GunDeps
} And add new func for Gun, almost done! func NewGun(conf GunConfig) *Gun {
   return &Gun{conf: conf}
} We can see, that we should add a little bit more for running: – Bind method. We just bind our client and args: – override Shoot method func (g *Gun) Bind(aggr core.Aggregator, deps core.GunDeps) error {
 // create gRPC stub at gun initialization
 conn, err := grpc.Dial(
  g.conf.Target,
  grpc.WithInsecure(),
  grpc.WithTimeout(time.Second),
  grpc.WithUserAgent("load test, pandora custom shooter"))
 if err != nil {
  log.Fatalf("FATAL: %s", err)
 }
 g.client = *conn
 g.aggr = aggr
 g.GunDeps = deps
 return nil
}

func (g *Gun) Shoot(ammo core.Ammo) {
 customAmmo := ammo.(*Ammo)
 g.shoot(customAmmo)
} It’s time to add switch method for SaveCase and ValidateCase requests and to add methods, as example for ValidateCase: func (g *Gun) caseValidate(client pb.DocumentServiceClient, ammo *Ammo) int {
 code := 0
 docName := ammo.Param1

 out, err := client.Validate(
  context.TODO(), &pb.ValidateRequest{Document: createDoc(docName)},
 )

 if err != nil {
  log.Printf("FATAL: %s", err)
  code = 500
 }

 if out != nil {
  code = 200
 }
 return code
} Full code here: https://github.com/IliaEre/serialisation-contest/tree/main/common/loadtest/yandex-tank/grpc?source=post_page-----12c250f2bff2--------------------------------&embedable=true Alright, pay close attention! func main() {
     // Standard imports.
     fs := afero.NewOsFs()
     coreimport.Import(fs)
     // May not be imported, if you don't need http guns, etc.
     phttp.Import(fs)
    // Custom imports. Integrate your custom types into configuration system.
     coreimport.RegisterCustomJSONProvider("grpc_provider", func() core.Ammo { return &Ammo{} })
    register.Gun("grpc_gun", NewGun, func() GunConfig {
     return GunConfig{
     Target: "localhost:84",
     }
     })
    cli.Run()
} When creating our gun, we must specify everything to compile and run it. We create a provider, specifying the name “grpc_provider” We create a gun and specify the name “grpc_gun” In the target, we specify**“localhost:84”** the location where our service is accessible. Okay, let’s continue. We have successfully copied and adjusted the code for the gun. Now, how do we run it, and what do we need? First, let’s create ammo again. This time, we’ll simply describe them like this: {"tag": "/ValidateCase", "Param1": "validate_doc_grpc_pandora"} This is necessary so that, in the method, we can retrieve the parameters needed for the test. In our case, we will retrieve the document name specified in Param1. Our code will automatically pass this parameter to the ValidateCase method, and we’ll be able to retrieve it. Great, the ammo is ready. Now, let’s configure the test itself: pools:
  - id: HTTP pool
    gun:
      type: grpc_gun   # custom gun name (specified at `register.Gun("my_custom_gun_name", ...`)
      target: "localhost:84"
    ammo:
      type: grpc_provider
      source:
        type: file
        path: validate-json.ammo
    result:
      type: phout
      destination: ./phout.log
    rps: { duration: 60s, type: const, ops: 1000 }
    startup:
      type: once
      times: 10 Here, we specify our ammo as “validate-json.ammo” Their type is “grpc_provider” Our gun is “grpc_gun” The load is 1000 rps for 60 seconds: rps: { duration: 60s, type: const, ops: 1000 } And the output goes to the file “./phout.log” — Yandex Tank understands this. The finishing straight — let’s now perform three simple actions: Build our gun. Assemble a new configurator for the tank. Run tests and check the results. Building it is very straightforward — just like a simple Go application: GOOS=linux GOARCH=amd64 go build It’s important to specify `GOOS=linux GOARCH=amd64`; otherwise, you might encounter errors when launching the tank. That’s it; the binary file is ready. Let’s update another configurator: phantom:
  enabled: false
pandora:
  enabled: true
  package: yandextank.plugins.Pandora
  pandora_cmd: ./grpc-gun # Pandora executable path
  config_file: ./validate-load.yml # Pandora config path
overload:
  enabled: true
  package: yandextank.plugins.DataUploader
  job_name: "grpc validate report"
  token_file: "env/token.txt"
telegraf:
  enabled: false
autostop:
  autostop:
    - time(1s,10s) # if request average > 1s
    - http(5xx,100%,1s) # if 500 errors > 1s
    - http(4xx,25%,10s) # if 400 > 25%
    - net(xx,25,10) # if amount of non-zero net-codes in every second of last 10s period is more than 25 Specify where our gun and its settings are located. Leave everything else as before and run it all with this script: echo "run tank"
docker run \
 -v $(pwd):/var/loadtest \
 - net="host" \
 -it direvius/yandex-tank -c validate-tank-load.yml After that, we will see our results. Special gun for flatbuffer! For flatbuffer, the story repeats. All you need to do is adjust your client code from grpc to http. Here’s an example: type Gun struct {
   // Configured on construction.
   client http.Client
   conf GunConfig
   // Configured on Bind, before shooting.
   aggr core.Aggregator // Maybe your custom Aggregator.
   core.GunDeps
   files [][]byte
}

func NewGun(conf GunConfig) *Gun {
   return &Gun{conf: conf}
}

func (g *Gun) Bind(aggr core.Aggregator, deps core.GunDeps) error {
   c := http.Client{Timeout: time.Duration(1) * time.Second}
   g.client = c
   g.GunDeps = deps
   g.aggr = aggr
} And then create similar methods and describe their behavior: func (g *Gun) caseValidate(client *http.Client) int {
  host := g.conf.Target
  response, err := client.Post(host+"/report/validate", "application/octet-stream", bytes.NewBuffer(g.files[2]))
  if err != nil {
   log.Printf("FATAL: %s", err)
   return 500
  }
  return response.StatusCode
} That’s it! In conclusion We’ve explored a new tool for performance testing called Yandex Pandora. You can run it as a standalone load engine if you don’t need fancy metrics. Alternatively, you can run it based on Yandex Tank, and in this case, you’ll get beautiful graphs and all the features of this cool tool! That’s all, I hope it was helpful! Thank you. Full code here: https://github.com/IliaEre/serialisation-contest/tree/main/common/loadtest/yandex-tank?embedable=true Also published . here

Leveraging Yandex Pandora: Stress Testing GRPC and Flatbuffer Services

Scientific American, Vol. XXXVII.—No. 2. [New Series.], July 14, 1877 by Various, is part of the HackerNoon Books Series. You can jump to any chapter in this book . SETTING LOCOMOTIVE SLIDE VALVES. here SETTING LOCOMOTIVE SLIDE VALVES. BY JOSHUA ROSE. E. G. asks: "How can I set the slide valves of a locomotive when she is on the road?" J. H. S. asks: "What is the method of setting locomotive slide valves from marks on the slide spindle?" And F. O. asks: "How are the valves of inside cylinder locomotives set, since the back ports are out of sight and you cannot measure the lead?" Our correspondent will find these questions answered in full below. It is presumed that the lengths of the eccentric rod, reverse rod, and other parts are correct, and they are properly connected and oiled so as to be in working order. The first thing to do is to place the reverse lever in the forward full-gear notch of the quadrants, or sectors, as they are sometimes called. The next procedure is to place the crank on its forward dead center as near as can be ascertained by the eye, and loosening the set screw of the forward eccentric, that is to say, the eccentric which connects with the upper end of the link, move that eccentric round on the shaft until the valve leaves the port at the front end of the cylinder open to the amount of whatever lead it is desired to give the valve. In moving the eccentric round on the shaft, it is necessary to move it in the direction in which it will turn when in operation. This is done in order to take up any lost motion there may be in the eccentric straps, in the eccentric rod eyebolts, or other working parts or joints between the eccentric and the slide valve rod or spindle. If the eccentric was turned backward instead of forward, all the lost motion would operate to vitiate the set of the valve, because, when the eccentric begins to move, its motion will have no effect in moving the slide valve spindle, until all the lost motion in the various parts is taken up by the eccentric movement. In considering this part of the operation, we must bear in mind that, to set the valve, we must move the wheels of the engine, it being impracticable to move the piston itself. Now, in moving the wheels, we are confronted with the fact that the crank pin is pulling the connecting rod; hence, if there is any lost motion in the brasses at either end of the connecting rod, the piston will not be at the end of its stroke when the crank is on its dead center. Suppose, for instance, that we have moved the driving wheel forward until the crank stands upright at a right angle to the bore of the cylinder, the resistance to motion of the piston and crosshead has caused the crank pin to bed against the half-brass nearest to the cylinder, all the play or lost motion is then between the other half-brass and the crank pin. When, however, the engine is at work and the piston is driving the crank pin, instead of being driven by it, the lost motion will exist between the crank pin and the half-brass nearest to the cylinder, and the contact will exist between the crank pin and the other brass. The difference in the position of the piston, caused by this lost motion, may be ascertained by moving the piston back and forth until the crank pin contacts with first one and then the other half-brass. It is sometimes attempted to remedy the defect due to this lost motion by moving the crank pin past the dead center and then moving it back to the dead center, so that while on that center the play or lost motion in the connecting rod is taken up. This is all very well so far as the connecting rod and piston is concerned, and will cause them both to stand on their respective dead centers with the lost motion taken up; but, in moving the wheel back to the dead center, we have given full liberty to all the lost motion in the various parts of the valve motion or gear, as already explained, in reference to moving the eccentric upon the shaft. As there are so many more parts in the valve gear, in which lost motion may occur, it is manifestly preferable to take up that play by moving the driving wheel in a continuous direction, rather than to move the latter back to accommodate any play there may be in the connecting rod. The crank being placed by the eye upon its forward dead center, and the eccentric connected to the top of the link being moved round on the axle (in the direction in which the wheels will run when the engine is going forward) until the steam port at the front end of the cylinder is open to the amount of the lead, we fasten the eccentric to hold in that position. We then throw the reverse lever over into the last notch at the other end of the sector, lifting the link up so that the eccentric connected to the lower end of the link may be approximately adjusted, which is done by moving the eccentric round upon the axle (in the direction in which the axle will revolve when the engine is running backward) until the crank stands upon the same dead center, and the front port is open to the amount of the lead. This being done, we have the eccentrics approximately adjusted and may proceed to the final adjustment, in which the first thing to do is to find the exact dead centers of the crank. It is obvious that a line drawn through the center of the crank pin and the center of the wheel axle, will stand horizontally true and level when the crank is on either of the dead centers, but the presence of the crank pin makes it impracticable to draw such a line. We can therefore draw one which will be parallel to those centers; and to do this we draw a circle upon the end of the wheel axle (and from its center) of the same diameter as that of the crank pin, and then resting a straight-edge upon the bearing of the crank pin (taking care to avoid the round corner upon the pin, if there is one), we place the other end of the straight-edge even with the top of the circle drawn upon the axle; and then, using the straight-edge as a guide, we draw a line across the end of the axle and the wheel face. When this line is level the crank will be upon its dead center. This plan is sometimes employed, but is not a very accurate one, because the length of the line is very short as compared to the circumference of the driving wheel; hence, an error of the thickness of the line becomes one equal to several thicknesses of the line when carried out to the wheel circumference. Furthermore, if the line of the cylinder does not stand horizontally level, as is sometimes the case, the result of the whole proceeding will be inaccurate. Again, the connecting rod end and the coupling rod is in the way, rendering it awkward to both draw and level the line. A better and more accurate method to find the dead centers is as follows: Place the reverse lever into the end notch of the sector at the forward end, and then move the driving wheel forward until the guide block is within about a quarter of an inch of the end of its travel, then place a straight-edge against the end of the guide block, and draw, on the outside face of the guide bar, a line even with the end of the guide block. Bend a piece of wire (pointed at both ends) to a right angle, make a center punch mark either in the rail, under the driving wheel, or in some stationary, solid part contiguous to the wheel, or at such distance from it that when one end of the bent wire is placed in the center punch mark, the operator with the other end will be able to draw a line across the rim of the driving wheel. Here, however, arises another consideration, that it is better to set the valves with the wheel axle in its proper position in the pedestal shoes, and in order to do this the wheel should rest upon the rail with its proper proportion of the weight of the engine resting upon it. The springs will then be deflected to their proper amount, and the axle box will have passed its proper distance up the pedestals. It is obvious that if the engine is blocked up so that the driving wheels clear the rails (which is done in order to avoid having the weight of the engine to move while setting the valve), the axle boxes will drop in the pedestal and the valve will be set incorrectly, as the wheels are in a wrong position. To avoid this, and at the same time to avoid having to move the whole engine while setting the valve, the engine is blocked up from the rails, and the axle boxes of the driving wheels are wedged up so as to be lifted up into their proper position. In this case there is no very accurate means of ascertaining what is the exact proper height, save it be by first marking upon the outside faces of the shoes or pedestal a line even with the top of the axle box when the load is upon the wheels, and then, after blocking up the engine from the rails, wedging up the axle boxes till the face again comes even with the line. Whatever plan is pursued, one end of the piece of wire is rested in the fixed center punch mark, and with the other a line is drawn across the outside face of the wheel rim. The driving wheel is then revolved forward until the guide block returns, having passed to the end of its travel. When its end again stands exactly even with the mark made upon the guide bar, the piece of wire is again brought into requisition, one end being rested in the fixed center punch mark as before, and with the other end another line is drawn across the outside rim of the wheel. It is obvious that by taking a pair of compasses and finding a point exactly equidistant between the two lines thus marked upon the wheel rim, and then marking that point with a center punch mark, the crank will be upon its exact dead center, when one end of the piece of bent wire rests in the fixed center punch mark, the other end rests in the center punch mark upon the wheel rim. To find the other dead center, the wheel must be moved about halfway round and the process repeated with the motion block at the other end of the guide bars. Thus, whenever the piece of wire will stand with one end resting in the fixed center punch mark and the other end in either of the center punch marks upon the wheel run, the crank is upon a dead center. Having thus placed the crank upon either dead center, we measure the valve lead, and if in temporarily fixing our eccentrics we gave it too much lead, we mark where it stands upon the shaft by means of a line drawn on the axle and carried up on the side face of the eccentric; then move the eccentric back some little distance more than is necessary to make the adjustment, and then move it forward again a little at a time, noting when the valve has the proper amount of lead, and thus fasten the eccentric upon the axle by means of the set screw. The object of moving the eccentric too far back and then moving it forward is to make the adjustment so that the latter may be made with the lost motion of the valve gear all taken up. The next proceeding is to move the driving wheel halfway round and try the lead at that end of the stroke. If the lead at the two ends is not equal, it shows that either the slide valve spindle or the eccentric rods are not of the proper length and must be rectified; this being done, the crank must be again placed upon first one and then the other dead center, the valve lead being measured at each end. When the lead is equal at each end, the rods are of correct length, and the amount of the lead must be regulated by moving the eccentrics as already directed. If the link block does not come opposite the end of the eccentric rod when the reverse lever is in the end notch of the sector, the length of the reverse rod is wrong and should be corrected. If the link block comes right, under the above conditions, for the forward but not for the backward eccentric rod, the notches in the sector are not cut in their proper positions, or the link hanger is not of the proper length. In either case the error may be remedied by altering the length of the latter. But, as doing this would alter the amount of the valve lead, it is well, if there is any prospect of such errors, to correct them before setting the valves. Instead of measuring the lead of the valve with a rule, or by a wedge, the following plan is very often adopted: After the valve and spindle are in position, the valve is placed with the proper amount of lead upon the front port. A center punch mark is then made upon the face of the steam chest. A piece of quarter inch iron wire is then bent at right angles and each end filed to a point. One end of this wire is placed in the fixed center punch mark in the steam chest, and with the other a mark is made upon the slide spindle. Upon this latter mark a center punch mark is also made sufficiently deep to be very plainly visible when the burr raised by center punching is filed off, which is necessary to prevent this burr from cutting the packing. It follows that whenever the bent piece of wire will rest with one end in the center punch mark in the steam chest, and the other end in the center punch mark in the slide spindle, the valve is in its proper position when the crank is on the corresponding dead center. This plan is a very old one and possesses the advantage that the valve may be set without seeing it, that is to say, with the steam chest cover on. If the length of the piece of wire measured direct from point to point is known, the valve may be set when the engine is upon the road without taking off the steam chest cover. The center punch mark upon the steam chest should, however, always be placed in about the same spot, so as to avoid mistakes in case of there being other similar marks upon the chest. It should always be made deep, so as not to get filled up with paint and be difficult to find. In course of time the mark upon the slide valve spindle is apt to disappear from the wear of the spindle, hence the center punch with which it is made should have a long conical point. To mark the position of the eccentric upon the axle, it is an excellent plan, after the eccentrics are finally adjusted, to take a chisel with the cutting end ground to the form of a fiddle drill, one cutting edge being at a right angle to the other. The chisel must be held so that while one edge rests upon the axle, the other edge will bear against the radial face of the eccentric. A sharp blow with a hammer upon the chisel-head will make a clean indented cut upon the axle and the eccentric, the two cuts exactly meeting at their junction and denoting the position of the eccentrics. In setting the valves of inside cylinder locomotives, the back ports being out of sight, the amount of lead is ascertained by making a wooden wedge about three inches long, a thirty-second of an inch thick at one end and three eighths of an inch thick at the other end. The faces of this wedge are chalked, and the lead is measured by inserting it between the edge of the valve and the edge of the port until its thickness just fills the space, and then moving it edgeways so that the valve and port edges will just mark it. By measuring the thickness of the wedge at the mark, the amount of lead is ascertained. After the valves are set, it is still desirable to mark the position by center punch marks upon the outside of the steam chests and upon the valve spindles, as already described. If an eccentric should slip when the engine is upon the road, and there are no marks whereby to readjust them, it may be done approximately as follows: Put the reverse lever in the end notch of the forward gear, then place the crank as nearly on a dead center as the eye will direct, and open both the cylinder cocks, then disconnect the slide valve spindle from the rocker arm, and move the valve spindle until the opening of the port corresponding to the dead center on which the crank stands will be shown by steam blowing through the cylinder cock, the throttle valve being opened a trifle. The position of the valve being thus determined, the eccentric must be moved upon the shaft until the valve spindle will connect with the rocker arm without being moved at all. The throttle valve should be very slightly opened, otherwise so much steam will be admitted into the cylinder that it will pass through any leak in the piston and blow through both cylinder cocks before there is time to ascertain which cock gives first exit to the steam. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Various (2012). Scientific American, Vol. XXXVII. —No. 2. [New Series.], July 14, 1877. Urbana, Illinois: Project Gutenberg. Retrieved https://www.gutenberg.org/cache/epub/38481/pg38481-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at , located at . www.gutenberg.org https://www.gutenberg.org/policy/license.html

SETTING LOCOMOTIVE SLIDE VALVES

I have always maintained that DeFi is in its experimental phase. Thus, when DeFi fanatics try to compare finance with TradFi, it translates as outright ignorance to me. Essentially, the purpose of my preamble is to highlight the inherent risks present in the ecosystem, pointing to the long and tortuous journey ahead of us if we must get things right, much less engage in comparisons. blockchain Because two truths can co-exist, DeFi has come a long way. Since my arrival here, I have witnessed the highs and lows of the growing industry. While my participation was limited, my first watershed moment coincided with the 2021 bull run, when meme coins went crazy, by the first dog-themed token, Dogecoin. And the heartbreaking moments reflected in periods I lost money trading futures and, particularly, losing four figures during the Nomad cross-chain bridge . Every other exploit and hack the industry has witnessed, I either observed on the streets of Crypto Twitter (now Crypto X) or crypto media platforms like CoinTelegraph, but not as a victim. led exploit Yet, it leaves me no choice (then and now) but to acknowledge that security is a missing catalyst to DeFi's 100x adoption. Hence, this piece focuses on the ZkOracle primitive and its key role in securing DeFi and restoring its declining goodwill. What are ZkOracles? TLDR: ZkOracles are blockchain oracles that leverage zkSNARKs and Zkproofs to trustlessly transmit data on-chain while ensuring privacy, security,, and cost-efficiency. ZkOracles, known as zero-knowledge oracles, are an offshoot of blockchain oracles. Blockchain networks rely on oracles to access and import data from the real world. Such data could range from asset prices and weather information for insurance claims to IoT sensors for tracking goods in the supply chain and events in prediction markets. In relation to DeFi, oracles have been most useful in the lending realm. Smart contracts play a key role in automating operations within lending protocols. However, smart contracts operate as a siloed and deterministic entity and are unable to integrate external or off-chain data by themselves, especially when this is important to executing instructions they are embedded with. For example, in prediction markets, smart contracts could not determine the winner of a prediction based on an event without leveraging an oracle that reports the outcome. But how do Zkoracles work? Zkoracles improve on the inefficiencies of traditional blockchain oracles— some of which have affected DeFi in its entirety, contributing to an adoption blight. But one inefficiency that resonates more among these is security. According to , most exploits across the DeFi ecosystem have resulted from oracle manipulation risks, pointing to the vulnerabilities inherent in traditional oracles. Chainalysis In 2022, oracle manipulation exploits for over $400 million in stolen cryptocurrencies. The Mango Market in late 2022 perfectly describes how traditional oracles could be manipulated by hackers for personal gain. Avraham Eisenberg, the black hat hacker, had manipulated the price of $MNGO, the native token of the Solana-based DEX and lending protocol, using his profit (from the short-lived inflated Mango price) as a collateral to obtain a loan valued at $116 million. accounted exploit While the oracles Mango Market ($MNGO's price was transmitted to the protocol using the moving average of centralized exchange price feeds) functioned accurately, they were easily manipulable due to their centralized status. $MNGO's low liquidity equally contributed to enabling the manipulation as a relatively minimal amount was used to inflate its price. Although some lending protocols avoid listing assets with low liquidity, this is contrary to the essence of decentralized lending— part of which aims to enable the collateralization of long-tail assets. How ZkOracles Work in DeFi Lending Lending protocols rely on oracles to calculate collateral value, borrowing limits, interest rates, etc— all of which are important for the proper functioning of the lending process. As such, a miscalculation across any of these hallmarks could spell doom for a protocol, particularly lenders— a lender could be arbitrarily liquidated if an oracle misreports mjprice or his collateral value. Yet, while decentralized oracle networks like Chainlink attempt to circumvent this challenge through multiple data sources for accurate reportage, the cost of doing so is high, this means that the more nodes that query data sources and supply the prices to lending dApps, the more the transaction to update the data on-chain becomes. expensive The reason for this is because each validator (node) has to sign a cryptographic message stating the price they queried, (i.e. ETH/ USD) for reporting into the Oracle to update on-chain. The more signed messages, the higher the cost of the Oracle transaction is because it contains more data (more signatures) Usually, a few Oracle service providers try to avoid this by limiting the number of nodes (validators) on the Oracle network. But this also comes at a cost— security tradeoff, thus increasing the potential for manipulation. Meanwhile, ZkOracles sidesteps all of these challenges without the need for tradeoffs— neither on security nor decentralization. ZkOracles data privacy, security, and cost-efficiency. For lending protocols, ZkOracles consult multiple off-chain data sources for asset prices or any other relevant data (wallet balances, transaction activity, collateral value, interest rates), performing as many off-chain queries as possible without incurring costs, unlike traditional oracles. prioritize ZkOracles transmits the off-chain computation and ZkProof for it (which it generates with the help of zk-SNARKS) on-chain to the smart contracts on the protocol. The data is transmitted trustlessly and privately such that bad actors are unable to frontrun and manipulate. Despite the private transmission, a lending protocol's smart contracts can verify that the data is accurate using the Zkproof generated. Securing DeFi with ZkOracles ZkOracles belong to the category of decentralized fair oracles, which have been touted for their advantages, such as minimized manipulation risks as data obtained is tamper-proof. Moreover, they also create the window of opportunity for long-tail assets such as liquid staking derivatives (LSD) outside the dominating LSTs— Lido's stETH and Rocketpool's rETH to attain a collateralization status (users could deposit them as collateral to obtain loans). Examples of the less popular LSDs include ankrETH, frxETH, cbETH, swETH, and metaLSD, UnshETH. Vitalik Buterin had concerns regarding the threats stETH and rETH domination pose to Ethereum's decentralization, suggesting that stakers should begin staking ETH with other protocols. And regarding collateralization, most (stemming from the concept that LSTs could attain other use cases such as lending and restaking) protocols (Lybra, Prisma, Gravita, etc.) prefer to onboard the dominant LSDs. In the same vein, major oracle providers require a $100 million and above TVL for any LSD to integrate their price oracle, shutting the door on the less-patronized LSTs. expressed LSDFi However, the mechanism behind ZkOracles suggests that less dominant LSTs could aggregate prices in DeFi lending without depending on a centralized entity or meeting steep requirements such as having huge TVL or incentivizing liquidity. This precludes the possibility of manipulation, thereby reducing the likelihood of another high-impact exploit since Zkoracles cull data through different APIs with a Zkproof that shows that the prices fed to protocols are trustless and verifiable. Final Thoughts While oracles are one of DeFi's most important infra, they have also proven to be the industry's Achilles heel, given the number of exploits that have occurred from the attack vector in the past year. Although one may likely argue that the industry is still standing in spite of the exploits, I'm compelled to take a cue from Dan Elitzer's article, where he noted that Thus, that argument crumbles if we (DeFi folks) have our eyes set on mainstream adoption as a goal. "Why DeFi is Broken" "the frequency and severity of exploits are at least two orders of magnitude above what might be considered acceptable levels for mainstream adoption." But mainstream adoption aside, ZkOracles preserve the ethos of decentralization that Lido's dominance appears to be threatening as regards Ethereum by enabling the less-dominant LSTs to gain market share and enjoy more utility on LSDfi protocols. Interestingly, as Dan Elitzer also suggested, I imagine that individuals and institutions could deploy ZkOracles for personal use on lending protocols, barring the need to depend on a general oracle and reducing the scope of damage in the event of an exploit (if the oracle of a user is compromised, any damage is limited to the user). I'd like to think of the integration of zkOracles into DeFi lending as killing three birds with a stone— privacy, decentralization, and security. Abbreviations ZKSNARKs - Zero-Knowledge Succinct Non-Interactive Arguments of Knowledge CDP - Collateralized Debt Positions. LSDfi - LSD Finance DeFi - Decentralized Finance TradFi - Traditional Finance LST - Liquid Staking Tokens LSD- Liquid Staking Derivatives Long-tail assets - Assets with low volume or liquidity ankrETH - Ankr staked ETH frxETH - Frax ETH cbETH - Coinbase ETH swETH - Swell ETH stETH - Lido’s staked ETH

Securing DeFi: The Case for ZkOracles

Daytona, a pioneering development environment management (DEM) platform offering secure and scalable hybrid development environments, just closed a $2 million pre-seed funding round. I've spoken with CEO and co-founder to learn more about the investment, Daytona's traction, and future plans. Ivan Burazin How much money did you raise in this round? We raised $2 million, which exceeded our initial target. There was tremendous interest from leading dev tools investors who recognized the potential of our solution. Who participated in the round? When we structured our Pre-Seed round, we intentionally sought support from experienced founders and key players in the developer tool industry, individuals whose reputations are linked to the tools you probably use daily. We received backing from angel investors like Abhinav Asthana (Founder of ), Prashanth Chandrasekar (CEO of ), Charity Majors (Co-Founder of ), Paul Copplestone (Co-Founder of ), Luke Kanies (Founder of ) and many others. Their domain expertise will help us refine our product and scale efficiently. Postman StackOverflow Honeycomb Supabase Puppet To bolster our capacity to meet growing demand, we also teamed up with Emerging Europe, a firm managing $2.7 billion in assets and an investor in over 35 billion-dollar enterprises such as GitLab, Twilio, Algolia, among others. Additionally, we're excited to reveal involvement from , , and , all of whom have supported top-tier companies, including Anthropic, Stripe, and OpenAI. 500 Tiny.vc Silicon Gardens Firestreak Ventures One of our angels, Christian Bach from , was impressed by our dedication to improving developer environments. He believes in our mission to make building more straightforward, a mission that's in line with the larger aim of boosting developer efficiency. Netlify standardized, secure developer environments What is your company’s current valuation? The round was done on an SAFE, reflecting the immense market potential for secure, self-hosted development environments tailored to enterprise needs. Our early traction with large Fortune 500 customers validates the strong demand. uncapped What does Daytona offer today? Daytona provides a self-hosted that gives enterprises an enterprise-grade alternative to GitHub Codespaces. Developers can spin up secure, compliant coding environments matching production infrastructure with a simple CLI command or click in the Daytona dashboard. development environment management platform Daytona eliminates complex configuration and security challenges while empowering developers with flexible, instantly available workspaces. We aim to be the industry standard for dev environments served through internal developer platforms. How do you differentiate from competitors? Unlike other development environment managers, Daytona is designed for self-managed deployment on internal infrastructure, whether cloud or local data center. This enables complete data control, security, and policy enforcement for regulated industries. Who are the founders and key team members? My co-founders, (CTO) and (Chief Architect), and I lead an experienced team of cloud dev tools veterans. We have pioneered the cloud IDE space with and have over 15 years of experience understanding developer needs. Building on this experience, Daytona offers unmatched flexibility, security, and simplicity. Vedran Jukic Goran Draganic Codeanywhere Our technical leadership designed Daytona's architecture leveraging Kubernetes, Kata Containers, and other leading orchestration technologies. We're a product-obsessed team focused on delivering exceptional solutions. How will you invest the funding? The funding will help us accelerate hiring across engineering, sales, and marketing to keep pace with customer demand. We'll also be refining our product capabilities, exploring strategic partnerships, and ramping up sales and marketing efforts. What’s exciting about your traction? We already have large enterprise customers in industries like aerospace, banking, and telecommunications. Our early success in securing Fortune 500 customers indicates the immense market appetite for enterprise-tailored development environments. What are your revenue goals? As this is an early stage, we are focused on product-market fit and scaling our customer base. In the forthcoming period, our goal is to double our revenue. Our vision is ambitious but achievable based on the enthusiasm we're seeing. What's your favorite pitch deck slide? My favorite slide captures the all-too-familiar pre-coding routine developers endure. It illustrates the steps before actual coding can begin, such as switching git branches, refreshing local environments, downloading libraries, installing tools, enduring build times, updating dependencies, compiling the project, and waiting for tests to run. When scaled across multiple projects and teams, this sequence of tasks significantly amplifies the inefficiency and frustration. This slide resonates deeply with our audience because it highlights the universal pain points in the development process, and it sets the stage for Daytona to present our compelling solution. It effectively underscores the necessity for a system like ours, which streamlines these cumbersome processes, allowing developers to focus on what they do best—coding. What problem does Daytona solve? Daytona addresses the challenges enterprises face in building secure, compliant development environments cost-effectively. We eliminate the need for expensive in-house platforms by providing an off-the-shelf solution purpose-built for regulated industries. The rise of infrastructure-as-code and integrated IDEs created the perfect timing for our standardized environment approach. We make robust dev environments accessible. What are the biggest risks? There is always execution risk with bringing a new product to market. However, our experience, technical expertise, customer validation, and exceptional investor support give us confidence. Our biggest challenge is keeping up with surging enterprise demand. We'll be smart about scaling sustainably. Why will Daytona grow exponentially? Every software team needs standardized environments to eliminate configuration drift and boost velocity. We have a track record as founders who helped pioneer cloud-based dev tools. With tailored enterprise capabilities, incredible support, and perfect timing, Daytona is poised for tremendous growth. The market pain points are clear, the solution works, and customers are validating the value. We enable enterprises to deliver better software faster through Daytona's simplicity and security. It's a very exciting time!

Interview with Daytona CEO Ivan Burazin on $2M Pre-Seed Round

When purchasing storage, the emphasis is usually on media, but it may be even more important to consider access methods too. You will need to take storage protocols into account when designing and procuring infrastructure, especially when you leave legacy storage behind in order to migrate to cloud-native object storage. However, object storage relies on the S3 API for communications, while legacy workloads rely on POSIX, the Portable Operating System Interface that provides a set of standards developed in the 1980s to allow applications to be portable between Unix OSs. Chances are that most enterprises have had applications in service for decades that were developed to run on POSIX. Chances are also that engineers are already aware of POSIX’s poor performance. That being said, when you have legacy systems that can only ingest data in a certain format or from a certain source, your options might be limited and you may have no choice but to implement an outdated protocol or rewrite your code. For example, if you can only ingest from a local disk with a filesystem and not with RESTful APIs accessed over network, then you must first make that data available on disk before your application can use it. However, using an object store as a filesystem has a number of serious negative implications when it comes to performance, compatibility, data integrity and security. Let’s demonstrate  this with some real world testing using a small utility called . This utility allows you to mount an S3 bucket as a local filesystem. It stands for S3 (Simple Storage Service) File System - FUSE (Filesystem in Userspace). It's an open-source project that leverages the FUSE (Filesystem in Userspace) interface to present a filesystem-like interface to S3. s3fs-fuse Once an S3 bucket is mounted using , you can interact with the bucket as if it were a local filesystem. This means you can use regular file operations (like read, write, move, etc.) on files in your bucket. This sounds amazingly convenient and we can argue it simplifies application development. But inherently object storage and file systems have fundamental differences that will affect the s3 bucket mounted as a filesystem. s3fs-fuse Let’s take a moment to step back from the utility to discuss the real reasons why treating object storage as a filesystem is far from optimal. The problem is much bigger than and includes other utilities such as Rust based , a file client that translates local file system API calls to S3 object API calls. The first reason is that all of these utilities rely on POSIX for filesystem operations. POSIX is inefficient and it was never intended for working with very large files over-the-network. s3fs-fuse s3fs-fuse Mountpoint for Amazon S3 The speed of POSIX based systems decreases as the demand, especially concurrent demand, on them increases. When large organizations need to store and access oceans of data for deep learning, AI, and other data intensive use cases, POSIX does not have the ability or scalability to meet these demands. While all-Flash arrays have kept POSIX in the game, scalability and RESTful APIs (the hallmarks of the cloud) are like kryptonite. Because of this, running POSIX on top of an object store is suboptimal. Let’s take a look at some of the reasons why: POSIX FS interface is inherently IOPS centric. They are chatty, expensive and hard to scale. RESTful S3 API addresses this by transforming IOPS into a throughput problem. Throughput is easier and cheaper to scale. This is why object storage is high-performance at a massive scale. Layering POSIX over S3 will not scale because POSIX is too chatty to be performed over an HTTP RESTful interface. Performance: Because object operations are atomic and immutable, there is no way to guarantee consistency correctness. This means you can lose the uncommitted data in case of a crash or run into corruption issues in case of shared mounts. Semantics: : Writes or any mutations to a file won't appear in the namespace until it is committed. This means concurrent access across shared mounts will not see the modifications. It is not useful for shared access. Data Integrity POSIX permissions and ACLs are primitive and incompatible with the S3 API’s way of handling identity and access management policies. It is not possible to safely implement POSIX access management on top S3 APIs. Access Control: POSIX also lacks most of the functionality that developers love about S3, such as  object level encryption, versioning, immutability – these simply have no equivalent in the POSIX world and nothing is able to translate them. POSIX Pain Points These examples illustrate the issue and its implications. To get started, we will use CSV file which is approximately 10GB and has 112 rows. this Note: We will assume the is already installed and you have mounted one of the buckets from the object storage into your filesystem. If not, follow the instructions . s3fs-fuse here In these examples, we will assume the bucket name is test-bucket and the file name is taxi-data.csv is in /home/user/ directory and is mounted at /home/user/test-bucket/ s3fs-fuse bucket Copy Operation We’ll try something simple first and try to copy the CSV file to our test-bucket using mc commands and record the time taken time mc cp /home/user/taxi-data.csv minio/test-bucket/taxi-data.csv This shouldn't take a lot of time and the file should be copied to our bucket. Now let’s try to do the same with s3fs-fuse time cp /home/user/taxi-data.csv /home/user/test-bucket/taxi-data.csv Time it took during the testing real	1m36.056s
user	0m14.507s
sys	0m31.891s In my case I was only able to copy the file partially to the bucket and the operation failed with the following error cp: error writing '/home/user/test-bucket/taxi-data.csv': Input/output error
cp: failed to close '/home/user/test-bucket/taxi-data.csv': Input/output error After multiple tries it succeeded real	5m3.661s
user	0m0.053s
sys	2m35.234s As you can see, because of the amount of API calls the utility needs to make and the general overhead of the operations, the utility becomes unstable and most of the operations do not even finish. Pandas Example We’ve shown you a simple example, which may or may not have been convincing, because let's face it, you might think is quite rudimentary. cp time cp So for the folks who need more empirical evidence let's write a Python snippet to test this. We’ll do a simple Pandas example with both and the package, and see the performance impact s3fs-fuse python s3fs import timeit
import os
import fsspec
import s3fs
import pandas as pd

# Write a dummy CSV file to test-bucket
df = pd.DataFrame({"column1": ["new_value1"], "column2": ["new_value2"]})
df.to_csv("s3://test-bucket/data/test-data.csv", index=False)


def process_s3():
    # add fsspec for pandas to use `s3://` path style and access S3 buckets directly
    fsspec.config.conf = {
      "s3":
      {
        "key": os.getenv("AWS_ACCESS_KEY_ID", "minioadmin"),
        "secret": os.getenv("AWS_SECRET_ACCESS_KEY", "minioadmin"),
        "client_kwargs": {
          "endpoint_url": os.getenv("S3_ENDPOINT", "https://play.min.io")
        }
      }
    }
    s3 = s3fs.S3FileSystem()
    for i in range(100):
        # Read the existing data
        print(i)
        df = pd.read_csv('s3://test-bucket/data/test-data.csv')
        # Append a new row
        new_df = pd.concat([df, pd.DataFrame([{"column1": f"value{i}", "column2": f"value{i}"}])], ignore_index=True)
        # Write the data back to the file
        new_df.to_csv('s3://test-bucket/data/test-data.csv', index=False)


execution_time = timeit.timeit(process_s3, number=1)
print(f"Execution time: {execution_time:.2f} seconds") Time taken during the testing Execution time: 8.54 seconds Now let's try the same for s3fs-fuse import timeit
import pandas as pd

# Write a dummy CSV file to test-bucket
df = pd.DataFrame({"column1": ["new_value1"], "column2": ["new_value2"]})
df.to_csv("s3://test-bucket/data/test-data.csv", index=False)


def process_s3fs():
    for i in range(100):
        # Read the existing data
        print(i)
        df = pd.read_csv('/home/user/test-bucket/data/test-data.csv')
        # Append a new row
        new_df = pd.concat([df, pd.DataFrame([{"column1": f"value{i}", "column2": f"value{i}"}])], ignore_index=True)
        # Write the data back to the file
        new_df.to_csv('/home/user/test-bucket/data/test-data.csv', index=False)


execution_time = timeit.timeit(process_s3fs, number=1)
print(f"Execution time: {execution_time:.2f} seconds") Time taken during the testing Execution time: 9.59 seconds These examples demonstrate constant reads and writes to S3 files. Imagine this performed concurrently by multiple clients – the latency grows dramatically. Remove the Overhead! As you can see, the difference between using POSIX translation to treat objects as files and using the direct API to work with objects is night and day. There is simply no comparison when it comes to security, performance, data integrity and compatibility. MinIO has to integrate with almost any popular programming language, and it can run on almost any platform such as Kubernetes, bare metal Linux, Docker containers – and much more. SDKs MinIO with encryption at rest and in-transit, combined with PBAC to regulate access and to protect data integrity. You will achieve the best performance possible, regardless of where you run MinIO, because it takes advantage of underlying hardware (see ) to deliver the greatest possible performance. We’ve MinIO at 325 GiB/s (349 GB/s) on GETs and 165 GiB/s (177 GB/s) on PUTs with just 32 nodes of off-the-shelf NVMe SSDs. secures objects erasure coding Selecting the Best Hardware for Your MinIO Deployment benchmarked There is simply no need for a filesystem utility in the middle of MinIO and your application! Any advantage legacy apps might receive will be offset by the pain of POSIX. If you have any questions about using POSIX translation for your application, be sure to reach out to us on ! Slack Also published . here

Why You Shouldn't Put a Filesystem on Top of an Object Store

কেন আপনি একটি অবজেক্ট স্টোরের উপরে একটি ফাইল সিস্টেম রাখা উচিত নয়

Warum Sie ein Dateisystem nicht über einen Objektspeicher legen sollten

Por qué no deberías poner un sistema de archivos encima de un almacén de objetos

Pourquoi vous ne devriez pas placer un système de fichiers au-dessus d'un magasin d'objets

आपको किसी ऑब्जेक्ट स्टोर के शीर्ष पर फ़ाइल सिस्टम क्यों नहीं रखना चाहिए?

ファイルシステムをオブジェクトストアの上に置くべきではない理由

객체 저장소 위에 파일 시스템을 배치하면 안되는 이유

Por que você não deve colocar um sistema de arquivos em cima de um armazenamento de objetos

Почему не следует размещать файловую систему поверх хранилища объектов

Neden Nesne Deposunun Üstüne Dosya Sistemi Koymamalısınız?

Tại sao bạn không nên đặt hệ thống tập tin lên trên kho lưu trữ đối tượng

为什么不应该将文件系统放在对象存储之上

Customers bring MinIO into their environments to gain high-performance S3-compatible object storage that runs on any physical or virtual hardware and Kubernetes. Our demonstrate that MinIO is the fastest object storage available, but it can only run as fast as the hardware and network you give it.  Performance is a big focus for our team, so we do everything we can to help administrators get the most out of MinIO. In order to verify that underlying infrastructure can support MinIO optimally, we provide two methods to assess performance and identify potential bottlenecks: WARP and Speedtest. published benchmarks Modern applications such as AI/ML, advanced analytics and databases require high-performance object storage. MinIO’s combination of scalability and high-performance puts every workload, no matter how demanding, within reach. When performance is critical, you need to know that you’re achieving the best performance possible. Results from WARP and Speedtest can be used to track performance over time and proactively pinpoint potential problems before they grow into serious issues. WARP is an open-source full-featured S3 performance assessment software built to conduct tests between WARP clients and object storage hosts. WARP measures GET and PUT performance from multiple clients against a MinIO cluster. WARP has many options, configured by command line or environmental variables, allowing you to create tests that align with your workloads. Remember - it’s absolutely critical to assess performance in a meaningful way and test using data and a workload that represents the real world conditions in which your object storage operates. In contrast, Speedtest is an easy-to-use automated performance test that provides a streamlined experience and concise results. We in November to provide MinIO administrators with the ability to run a distributed performance assessment of their MinIO clusters with a single command. Speedtest runs PUTS, then GETS, incrementally increasing load to pinpoint maximum aggregate throughput. Tests can take anywhere from a few seconds to several minutes to execute depending on your MinIO cluster. introduced Speedtest There are some important differences between WARP and Speedtest. WARP is a complete tool that tests performance of your MinIO cluster via operations conducted by WARP clients. Client machines are conducting PUTS and GETS of objects across the network to your distributed MinIO cluster. This makes WARP an excellent mechanism for testing anticipated client-server performance. In contrast, Speedtest runs on MinIO instances to conduct PUTS and GETS of objects to other MinIO instances in the same cluster. As such, Speedtest tells you what the server side of the performance equation is capable of. WARP contains just about every test (GET, PUT, DELETE, LIST, STAT, RETENTION) you might want to run against object storage, and test runs can include a custom mix of object sizes to match your workloads. Speedtest runs through set test parameters to pinpoint maximum throughput quickly. While WARP requires additional software, Speedtest is included with MinIO and can be run from the mc interface or MinIO Console. To aid in troubleshooting, customers can share Speedtest results with MinIO engineers with a single click. WARP: A Complete Object Storage Benchmarking Tool First, let’s take a look at WARP.  WARP is a tool that allows you to thoroughly benchmark MinIO, or any S3-compatible object storage, performance under a variety of conditions.  By default, WARP will perform a mixed test of read and write over all disks utilized by MinIO running in distributed mode. For this demo. we’re going to be running WARP to test MinIO running on AWS in distributed mode. We’ve been doing this pretty often lately, so we can advise potential and current customers of the highest-performing configurations we have found by testing them. WARP is located in a , where you will also find detailed documentation. GitHub repository We’re going to start by deploying MinIO in . You can and install it in your environment by yourself, or you can follow this . distributed mode download MinIO tutorial to install MinIO on AWS EC2 Either way, we are going to start with a distributed MinIO deployment: Once MinIO is up and running you will be able to measure performance with WARP, so let’s get started. Step 0: Create 4 instances (also known as nodes) with Distributed MinIO. For all Amazon UI or AWS CLI, please follow steps from the to deploy instances, but do not configure additional storage. The instances running WARP must be powerful enough to quickly generate objects and measure PUT and GET operations, but do not require the storage volume needed by a MinIO node. previous blog post Step 2: Add hosts in /etc/hosts file at WARP clients. Get the IP Addresses of the MinIO instances Get the IP Addresses of the WARP clients Add those address in the /etc/hosts file: 172.31.23.237 host1
172.31.26.78  host2
172.31.26.90  host3
172.31.19.110 host4
172.31.27.18  warp1
172.31.23.81  warp2
172.31.19.28  warp3
172.31.19.7   warp4 This simplifies launching WARP from the command line and makes it easier to locate each WARP client and MinIO host. Notice that we recommend listing and working with hosts in consecutive order. Step 3: Install WARP on the clients and run it. [root@ip-172-31-19-7 ec2-user]# wget https://github.com/minio/warp/releases/download/v0.5.5/warp_0.5.5_Linux_arm64.tar.gz
2022-02-08 20:06:04 (66.3 MB/s) - 'warp_0.5.5_Linux_arm64.tar.gz' saved [3943887/3943887]

[root@ip-172-31-19-7 ec2-user]# tar -xzvf warp_0.5.5_Linux_arm64.tar.gz
LICENSE
README.md
warp_logo.png
warp
[root@ip-172-31-19-7 ec2-user]# ./warp client
warp: Listening on :7761 Notice that each WARP client is listening on port 7761 Step 4: Run WARP and launch a mixed benchmark. [root@ip-172-31-27-18 ec2-user]# WARP_ACCESS_KEY=minioadmin WARP_SECRET_KEY=minioadmin ./warp mixed --warp-client warp{1...4}:7761 --host host{1...4}:9000 --duration 120s --obj.size 64M --concurrent 64
warp: Benchmark data written to "warp-remote-2022-02-08[201339]-qymu.csv.zst"                                                                                                                                                                        
Mixed operations.
Operation: DELETE, 10%, Concurrency: 256, Ran 1m54s.
 * Throughput: 39.90 obj/s

Operation: GET, 45%, Concurrency: 256, Ran 1m54s.
 * Throughput: 10903.28 MiB/s, 178.64 obj/s

Operation: PUT, 15%, Concurrency: 256, Ran 1m54s.
 * Throughput: 3628.27 MiB/s, 59.45 obj/s

Operation: STAT, 30%, Concurrency: 256, Ran 1m54s.
 * Throughput: 119.98 obj/s

Cluster Total: 14501.38 MiB/s, 397.44 obj/s over 1m55s.
warp: Cleanup done.                                                                                                                                                                                                                                  
[root@ip-172-31-27-18 ec2-user]# You’ve completed a basic mixed-mode performance test using WARP. While we used a mixed-mode test to demonstrate WARP, you will typically obtain better results that are more aligned to real-world usage) by breaking out individual operations (GET, PUT, LIST) into their own test runs instead of running a mixed-mode test. We encourage you to refer to the to learn about executing more test scenarios. For example, you can enable TLS and server-side encryption to measure their impact in your environment. You can stress infrastructure more by increasing the number of concurrent tests. You can use a random mix of object sizes, or specify an object size that matches your current environment and workload. You can configure tests to run for a defined period of time or to auto-terminate as we did above. documentation WARP results are shown on-screen and saved to a local CSV file compressed using zstandard. Speedtest for a Quick and Easy Performance Assessment In the event that you don’t want the full flexibility of WARP, we’ve built a quick and easy way to measure MinIO performance using Speedtest. Speedtest is most commonly run in autotune mode, incrementally increasing load to pinpoint maximum aggregate throughput. You can use mc to run Speedtest: $ mc support perf object <alias> [root@ip-172-31-77-115 ec2-user]# ./mc support perf object myminio

   	THROUGHPUT	IOPS      
PUT	2.4 GiB/s 	38 objs/s	
GET	4.6 GiB/s 	73 objs/s	

Speedtest: MinIO 2022-02-01T18:00:14Z, 4 servers, 16 drives, 64 MiB objects, 72 threads Or, you can run Speedtest from MinIO Console, the browser-based GUI for configuring, managing and reporting on MinIO clusters. Simply navigate to the Support menu and click Performance, then click on the start button. The performance test will run. When it is complete, aggregate GET and PUT performance as well as performance of individual nodes is displayed. For more details and examples for Speedtest, please see this . tutorial Warp Speed Ahead! Get started by today. Join our and exchange ideas with other MinIO users. If you have any specific questions about using WARP, please reach out to us on our Slack channel (Matt Sarrel and Cesar Celis) or send us an email at hello@minio.io. downloading MinIO Slack community Also published . here

Benchmarking MinIO with WARP and Speedtest

WARP এবং Speedtest সহ বেঞ্চমার্কিং MinIO

Benchmarking von MinIO mit WARP und Speedtest

Evaluación comparativa de MinIO con WARP y Speedtest

Analyse comparative de MinIO avec WARP et Speedtest

WARP और स्पीडटेस्ट के साथ मिनियो को बेंचमार्क करना

WARP と Speedtest を使用した MinIO のベンチマーク

WARP 및 속도 테스트를 사용한 MinIO 벤치마킹

Comparando MinIO com WARP e Speedtest

Бенчмаркинг MinIO с помощью WARP и Speedtest

MinIO'yu WARP ve Speedtest ile kıyaslama

Đo điểm chuẩn MinIO với WARP và Speedtest

使用 WARP 和 Speedtest 对 MinIO 进行基准测试

Dedicated to Waterstone's, the national UK bookselling chain

Management was tough for me in the beginning—too many things to learn and too little time to put everything into practice. I kind of assumed that to be an effective manager; I needed to master all the skills and be great at everything. Trying to do it all and be the best at everything took a toll—I was left feeling tired and exhausted. I was running behind and thought working harder would help me catch up to the demands and expectations of the job. But the harder I tried, the tougher it got. It took a bit of experience and some painful stories to realize that good does not require being a superhuman with extraordinary skills. It only requires practicing these 3 important skills. management 3 Skills to Master as a Manager Give your people a voice Managers think that their job is to give advice, tell people what to do, make suggestions, come up with new ideas, and determine what needs to be done. But in doing so, they sometimes fail to stop and listen. to get work done, but effective communication isn’t one-sided. It’s a two-way street. Communication is important \When employees don’t feel heard, they also refuse to listen. Not being able to say what they need to say leads to feelings of isolation, resentment, and rejection, which also impacts their productivity and performance. When you listen more and speak less: Team members feel heard and respected to voice their opinions. Real problems are addressed instead of wasting time on inconsequential problems or issues that don’t deserve your time and attention. Such conversations are deeper, more productive, and have a higher likelihood of building better relationships in the long run. To give your people a voice, encourage them to speak up. Show that you care about their thoughts. Don’t just say that you respect their viewpoint; actually show it in your actions. Others are not fools. They can clearly see the difference between fake talk and a genuine desire to listen. Listen with curiosity. Speak with honesty. Act with integrity. The greatest problem with communication is we don’t listen to understand. We listen to reply. When we listen with curiosity, we don’t listen with the intent to reply. We listen for what’s behind the words — Roy T. Bennett Lead with questions, not answers A manager who acts as a know-it-all may assume they’re helping their people by answering their questions and giving them solutions, but leading with answers solves temporary problems while creating bigger problems in the long run. When on their own, they become dependent on their manager to do their thinking for them. Managers feel happy—they assume they’re doing their team a favor by unblocking them. In reality, they take away their freedom to think and execute independently. employees don’t learn to think and solve problems When you lead with questions: You encourage your team to exercise their brain muscles. Instead of executioners, it builds owners. They develop critical thinking skills necessary to do well and succeed. Asking open-ended questions with a tone of curiosity and inquiry is a great way to encourage your team to think creatively, find solutions to problems, and turn obstacles into opportunities. \Creativity requires asking questions for which an answer is not already known. The truth is that innovation is rarely the product of pure inspiration, that “Eureka!” moment when some genius comes up with a wholly new idea. Rather, innovation happens when people see things differently. It starts with a questioning culture that helps people gain new perspective and see things differently. Innovation is generated by great questions in an environment that encourages questions — Michael J. Marquardt Care personally, challenge directly Many managers either lean towards caring for their people so much that it negatively impacts their team’s growth and performance, or they’re so focused on driving business outcomes that they forget what it takes to be human. Caring personally for each individual on your team is important, but equally important is to speak your truth without twisting your words to make them feel better or avoid hurting their emotions. Let them sulk, be mad at you, or even feel angry. Facing the reality of their situation will make them stronger, while avoiding it will only hurt their performance. When you care personally but also challenge directly, your team members: . Knowing that you have good intentions at heart makes them focus on learning and improving as opposed to proving. Don’t take criticism personally They learn to embrace conflicts rather than avoid them. Makes them more open to admitting when they’re wrong and fixing mistakes. They feel accountable for delivering on their promise and driving outcomes for the organization. A great way to do this is to give a damn—shift from being strictly professional to making it personal. Tell them that they need to hear not only when they’re doing well but also when they aren’t. Don’t settle for less or keep low expectations. Raise the bar; expect nothing but excellence. Radical Candor is what happens when you put “Care Personally” and “Challenge Directly” together. When Radical Candor is encouraged and supported by the boss, communication flows, resentments that have festered come to the surface and get resolved, and people begin to love not just their work but whom they work with and where they work. When people love their job, the whole team is more successful. The resulting happiness is the success beyond success — Kim Scott Becoming a manager that your people trust and respect is not hard once you create a safe space for employees to voice their opinions, help them build creative thinking skills by leading with questions, and strike the right balance between challenging and personally caring for them. Summary To be an effective manager, master these 3 most important skills. Encourage your people to speak up and share their thoughts. When your team feels safe to voice their opinion, they feel heard and respected and do not shy away from addressing real problems that need time and attention. Help them solve problems on their own by asking questions and not spoon-feeding them solutions. Care for them personally but at the same time act tough when they don’t meet expectations. Also published . here

If You Want To Be An Effective Manager You Have To Master These 3 Skills

is a that offers robust solutions for simplifying and enhancing the security and compliance aspects of software applications. Aptible streamlines the complex process of achieving and maintaining industry-standard certifications such as HIPAA, SOC 2, and GDPR. Aptible No Infrastructure Platform Sounds interesting, isn’t it? Like many of you I love to try new things. gives one month of a free trial which is just perfect to poke around. Aptible Let’s assume you have an existing app hosted somewhere (in my case it’s DigitalOcean) and you really want to try out Aptible. I took from my about . There we had a decent yet simple CI/CD pipeline based on Github Action. So let’s go ahead and make it work with Aptible. almost-one-line-spring-boot-app previous article Release Driver Development Aptible provides a nice way to deploy the code right from Git. We will take a closer look down below. Prerequisite Make sure you did next things before moving forward: Add Aptible’s username and password to Github Action’s secrets under and variables accordingly APTIBLE_USERNAME APTIBLE_PASSWORD Make sure to create a new App manually (go to Aptible’s Dashboard → choose your environment → button). The same as DigitialOcean, Aptible doesn’t automatically create an app on the first run. Create App Changing existing pipeline To be able to deploy to Aptible we need to add a new step to our existing Github Actions pipeline. I don’t want to get rid of DigitalOcean step, so let’s add a switcher to the section together with Aptible-related params: env env:
  # Where to deploy. Options are 'digitalocean' or 'aptible'
  DEPLOY_TARGET: 'aptible'
  
  # Aptible deploy params
  APTIBLE_ENVIRONMENT: 'google-aeb'
  APTIBLE_APP: 'deployinator' For the deployment step we are using . It is pretty self explanatory, you just need to specify credentials, what, and where you are deploying. Deploy to Aptible Github Action The step looks like: - name: Deploy to Aptible
  if: ${{ env.DEPLOY_TARGET == 'aptible' }}
  uses: aptible/aptible-deploy-action@v1
  with:
    username: ${{ secrets.APTIBLE_USERNAME }}
    password: ${{ secrets.APTIBLE_PASSWORD }}
    environment: ${{ env.APTIBLE_ENVIRONMENT }}
    app: ${{ env.APTIBLE_APP }}
    docker_img: ${{ secrets.DOCKERHUB_USERNAME }}/deployinator:${{env.RELEASE_VERSION}} Before the actual deployment, the step pulls the image from Dockerhub and pushes into Aptible’s Docker registry. Perfect, let’s try it out. Committing the changes, pushing to master and … this is what we see on the Aptible Dashboard: Troubleshooting (unplanned section) I know, I promised it to be seamless. It will! We just need to figure out a root cause for the failure. I wasn’t able to find any kind of logs neither on the dashboard nor in the Github’s build - it was green. Nothing I could find by googling the error, says: official doc If endpoint provisioning fails, restart your app using the aptible restart command. You will see a prompt asking you to do so. Note this failure is most likely due to an app health check failure. We have troubleshooting instructions here: My deploy failed with HTTP health checks failed The only way to check what exactly has happened is to install and restart the app. Aptible CLI Frankly speaking, installing CLI to get logs is not the friendliest way to understand what’s wrong with the deployment. It would be great if Aptible could provide more insights on the dashboard. > brew install --cask aptible

# be ready to provide login/password
> aptible login 

> aptible restart --app deployinator Among other output logs we can find next errors: ...
ERROR -- : Your Docker image must EXPOSE a port to provision an Endpoint, add an EXPOSE directive in your Dockerfile.
ERROR -- : FAILED: Wait up to 180s for containers in service cmd to respond to HTTP health checks
... We have to add to the Dockerfile to let Aptible know how to configure the endpoint and do the heath checks. We also need to change Spring Boot server’s port accordingly by adding to file. You can take a look at the full code at branch. EXPOSE 80 server.port=80 application.properties deploy-aptible On the second attempt we can see app’s Endpoint automatically created That’s way better. The only thing our app can do is to show the version under endpoint. So, copy the hostname from the endpoint and try it. /version Perfect, it works. Deploy on Git Push Another option I mentioned in the beginning is to deploy by Git Push. To make it work you have to press the button on the Dashboard and go through a pretty straightforward which includes providing your public ssh key and adding Aptible’s Git repo as a remote for your existing repo. The idea here is by pushing into Aptible’s Git remote you trigger (re-)deployment. It’s completely fine to to work with your existing Git repo (named ) as before, but when you need a deploy, just run something like: Deploy Code setup process origin git push aptible main Aptible will find Dockerfile in your repo, build an image based on it, and deploy as a container. Pretty cool, huh? As a small additional bonus, you can see deployment logs right in your console. Seems like we don’t need the Github Actions pipeline anymore. Aptible deploys your app based on what you have in a Git repo. Which is absolutely nice! But it’s only from the first sight. This automated approach works good only for small apps, while having drawbacks working with a bigger one. Think about: How to manage versions as you no longer have CI/CD pipeline? What if you need additional steps (run integration tests, publish artifacts, etc) before deployment? Dockerfile becomes overloaded by extras like because it’s the only thing between you and Aptible. gradlew build Let’s try this out and see how far it will bring us. First of all, we have to make Dockerfile self-sufficient by moving everything inside. By ‘everything‘ I literally mean everything that we had in the pipeline. Take a look at the result and I will explain it down below: # Temp container to run gradle build
FROM gradle:latest AS BUILD
COPY --chown=gradle:gradle . .
USER gradle

# Tag current commit with commit's sha for versioning purposes
RUN git tag $(git rev-parse --short HEAD)
RUN gradle build

# Main stage
FROM eclipse-temurin:17
EXPOSE 80
COPY --from=BUILD /home/gradle/build/libs/deployinator-*.jar /app/deployinator.jar
ENTRYPOINT java -jar /app/deployinator.jar We are using a build. First phase is to build a jar file. To make it happen we start with temporary image, copy all the files inside and run . There is also one trick in here. As we copied the source files, we also have folder inside the image (it is temporary, no worries about extra files). The reasoning behind this is to let access Git tags and provide version info for Gradle. multi-stage gradle:latest gradle build all .git gradle-git-plugin So, the overall deployment flow looks like: You push a branch into Aptible’s Git repo Aptible starts a deployment by doing a of the repo shallow clone Aptible finds Dockerfile and kicks off docker build ... Docker goes over instructions in a Dockerfile and copies everything from a cloned repo inside a container, including a folder .git Command tags current commit with commit hash git tag $(git rev-parse --short HEAD) During gradle-git-plugin fetches last tag and makes it a project version gradle build As build finishes, Aptible triggers and exposes our app to the world on a port defined in the statement. docker run ... EXPOSE Commit hash is not the best option for a project’s version. SemVer or simply buildNumber + gitHash is slightly better (a bit more info about it in a ). previous article However, I couldn’t find a way to access anything similar to buildNumber. Aptible doesn’t seem to add as to docker build command APTIBLE_PROCESS_INDEX metadata variable --build-arg file is not accessible from the container’s root Configuration variable .aptible.env If you were able to find a way to get a sequential build number (or any other config var which might be helpful) from within Dockerfile - let me know in the comments. All the code is available under branch. Now let’s make it deployed by running: deploy-aptible-on-git-push # Check current hash
> git rev-parse --short HEAD 
703496a

# Kick-off deployment
> git push aptible deploy-aptible-on-git-push:main Waiting for a little bit and… Perfect, commit hash is the same. We have a dirty flag here which means that Aptible changed (probably added) something after git clone and introduced an unstashed change. It’s worth mentioning that Aptible provides additional configs for Releases, you can take a closer look . here Conclusion Moving a simple app from DigitalOcean to Aptible having a Github Actions pipeline is a pretty easy. You just have to change the deployment step with almost no changes to the code (except explicitly adding http port if necessary). When you have things clearly separated and independent from each other, interchangeability works perfectly. Another way could be setting up deployment on Git Push. It's a very straightforward and nice-looking approach. However, I’m still skeptical about the fact that it’s pretty limited and forces you to concentrate CI/CD actions in a Dockerfile. Which is not something that leads you toward a clear . separation of concerns

Seamless Deployment to Aptible: Choosing the Right Approach

Docker’s New Business Model and the Era of Image Visualization

ডকারের নতুন ব্যবসায়িক মডেল এবং ইমেজ ভিজ্যুয়ালাইজেশনের যুগ

Dockers neues Geschäftsmodell und die Ära der Bildvisualisierung

El nuevo modelo de negocio de Docker y la era de la visualización de imágenes

Le nouveau modèle économique de Docker et l'ère de la visualisation d'images

डॉकर का नया बिजनेस मॉडल और इमेज विज़ुअलाइज़ेशन का युग

Docker の新しいビジネスモデルとイメージ可視化の時代

Docker의 새로운 비즈니스 모델과 이미지 시각화 시대

O novo modelo de negócios do Docker e a era da visualização de imagens

Docker'ın Yeni İş Modeli ve Görüntü Görselleştirme Çağı

Mô hình kinh doanh mới của Docker và Kỷ nguyên trực quan hóa hình ảnh

Docker的新商业模式与图像可视化时代

Stories, News & Mentions about RUNWHEN

Runwhen’s Stories on HackerNoon