Resilio

resilio

This article is part 2 of the Blockchain train journal, start reading here: . Catching the Blockchain Train Some reading material to get started A couple of articles that I found useful when learning about decentralized storage: Decentralized Storage: The Backbone of the Third Web HTTP is obsolete. It’s time for the distributed, permanent web What is the difference between Swarm and IPFS? Comparing decentralized storage systems Our decentralized blog pages are in need of some sort of decentralized hosting. To build that from scratch seems like a lot of work and will probably result in a blockchain train crash. So let’s see what is already out there we could use for our project. I searched a bit and came up with: Storj SIA MaidSafe IPFS ZeroNet Ethereum Swarm BigchainDB did I forget a serious contender? Please . let me know I’m not yet qualified to compare these technologies (still trying to catch the train!), but I’ll add some observations for each: Storj From the home page: Blockchain-based, end-to-end encrypted, distributed object storage, where only you have access to your data. That doesn’t sound like something that is handy for a blog, where we want content to be public. Storj looks like a great product though, it is a bit like , but with a blockchain added to create a marketplace for buying or renting out disk space on the network. Resilio Sync SIA SIA is another Dropbox killer, more or less the same as Storj. MaidSafe Where Storj and SIA pitch their service as a faster and cheaper way to store your data, Maidsafe promotes their SAFE network by scaring you. Cloud providers, government, and hackers can not be trusted is the message in their video. Apart from the funny name, it is very similar to the two services above. IPFS Now, this is a different beast. The first three services are , which means they have their own cryptocurrency to support their marketplace. IPFS also has such a thing, , but it is neatly split from IPFS which is more like a decentralized storage protocol. incentive platforms FileCoin IPFS stands for , but they hide the original name from their homepage. Too funny for a serious business! interplanetary file system On the home page it says: IPFS is the Distributed Web A peer-to-peer hypermedia protocol to make the web faster, safer, and more open. IPFS seems like an great option for our project. ZeroNet ZeroNet doesn’t have a cheesy video on their home page, so I had to actually . However, their awesome presentation is 100x better than the four videos from the others combined: . read ZeroNet preso They also seem to operate a lot less like a serious business compared to the others, showing more of the idealistic open source spirit. On the home page: Open, free and uncensorable websites, using Bitcoin cryptography and BitTorrent network Oh, oh, that is what are trying to do here! A competitor! Nah, let’s just keep an eye on the code, maybe we can learn a thing or two. we Ethereum Swarm On our trip to become blockchain developers, we have no other choice than to dive into Ethereum. We will address that in a future episode. But their decentralized file storage system, named Swarm, must be considered here. It took me a while to find the source code for this project, but ! here it is From the : documentation Swarm is a distributed storage platform and content distribution service, a native base layer service of the ethereum web 3 stack. The primary objective of Swarm is to provide a sufficiently decentralized and redundant store of Ethereum’s public record, in particular to store and distribute dapp code and data as well as block chain data. It seems that Swarm is an incentive platform enforced with Ethereum smart contracts, so not the best choice for our purpose. We gotta stay hands-on here. We want to add a coin later ourselves! BigchainDB From their site: BigchainDB is complementary to decentralized storage, processing and communication building blocks. It can be used side by side with higher-level decentralized computing platforms and applications, and protocols for identity, financial assets, intellectual property and sidechains. BigchainDB fills a gap in the decentralized stack. This is a brilliant solution, almost too good to be true. It is not just decentralized storage, but a full blown database. It is built on top of MongoDB and decentralized, so data is immutable, and there is no central authority. For our current project it might be a bit overkill, but let’s keep an eye on it. The winning decentralized storage system OK, I’ll be honest, I already picked one before I did this quick research what is around :-) The winner is IPFS! Yay! The runner-up we might have a look at at a later stage: BigchainDB! Even in retrospect, IPFS seems like a good choice: all competitors have their “flaws” in the context of this project. By applying “selection by deduction”, only IPFS remains. After this very scientific approach in picking IPFS, let’s hope it is indeed useful for us. Let’s move on to part 3: Getting to know IPFS Originally published at decentralized.blog .

Picking a Decentralized Storage System

Penetration Testers’ Guide to Windows 10 Privacy & Security

Guía de los probadores de penetración para la privacidad y seguridad de Windows 10

From Resistance to Resilience: Change Management for First-timers in Digital Transformation

Optionals in Swift are one of the language's most convenient and powerful tools, allowing you to handle missing values safely and prevent crashes. Using Optionals is an essential part of iOS development, especially when dealing with data from users or external sources. In this article, we’ll dive into both basic and advanced methods for working with Optionals, showing how to use them in real-world scenarios to improve code reliability. What Are Optionals and Why Do We Need Them? Optionals in Swift allow a variable to hold a value or be empty (nil). This is particularly useful when data comes from unstable sources, like user input, databases, or servers, where data presence isn’t always guaranteed. Key Benefits of Optionals: Safety: Missing data doesn’t lead to app crashes.


Clarity: Using ? indicates that a value may be absent. Simple Example: var userName: String? = "Alice"
userName = nil  // Now the variable can have no value In this example, userName can either be a string or nil. If the value is missing, Swift allows you to handle it smoothly, making the app more resilient. Working with Optionals in Swift Method

When to Use

Example Code



Forced Unwrapping

If you’re sure the value isn’t nil.

let unwrappedName = userName!



Optional Binding (if let)

For safely unwrapping and handling missing data.

if let unwrappedName = userName { ... } else { print("No name provided") }



guard let

Checks value and exits function if data is nil.

guard let unwrappedName = userName else { return }



Nil-Coalescing (??)

To set a default value if the variable is nil.

let providedName = userName ?? "Unknown"



Optional Chaining

For safe access to nested values.

let userNameLength = user?.profile?.name?.count Example 1(Simple): Forced Unwrapping Forced unwrapping is used when you’re certain the value won’t be nil. This method can cause a crash if the variable is empty, so it’s best avoided unless you’re confident in the value’s presence. let unwrappedName = userName!
print("User Name: \(unwrappedName)") Forced unwrapping is useful when data is hard-coded or validated by logic. Optional Binding (if let): Safely Extracting Values Optional Binding with if let checks for the presence of a value and only uses it if it exists, avoiding errors. if let unwrappedName = userName {
    print("User Name: \(unwrappedName)")
} else {
    print("No name provided")
} This method is particularly handy when working with data from the network or databases, where information may be missing, such as when loading a user profile from an API. Nil-Coalescing (??): A Default Value for Empty Variables The Nil-Coalescing operator (??) assigns a default value if the variable is nil, making code simpler and more readable. let providedName = userName ?? "Guest"
print("User Name: \(providedName)") Nil-Coalescing is useful when you want to avoid empty values and need a standard default. Example 2 (Advanced): Error Control and Protection Let’s move on to advanced examples that demonstrate how Optionals help manage nested data and protect against unpredictable errors. guard let: Reliable Value Checking guard let checks the value and exits the function if the data is nil, which is useful for mandatory data. func greetUser(_ name: String?) {
    guard let unwrappedName = name else {
        print("No name provided")
        return
    }
    print("Hello, \(unwrappedName)!")
} In real work, guard let is convenient for mandatory data checks, like validating form fields. If the value is empty, you can immediately exit the function. Optional Chaining: Safe Access to Nested Values Optional Chaining (?.) allows you to access nested data without the risk of a crash. If any object in the chain is nil, the entire result will be nil. let userNameLength = user?.profile?.name?.count Optional Chaining is particularly useful when working with JSON data and complex structures. For example, if you’re loading a user profile from an API, Optional Chaining simplifies checking each field. Practical Applications of Optionals in iOS Projects Example 1: Retrieving User Profile Data from an API API responses may contain empty fields, and Optionals help handle these situations gracefully without causing crashes. struct UserProfile {
    var name: String?
    var age: Int?
}

func displayUserProfile(user: UserProfile) {
    let displayName = user.name ?? "Guest"
    print("User Profile: \(displayName)")
} Here, if the user’s name isn’t specified, a default value—“Guest”—will be used. Example 2: Registration Form Validation Optionals and guard let allow for proper handling of required and optional form fields. For example, checking if an email address is provided during registration. struct RegistrationForm {
    var username: String
    var email: String?
}

func registerUser(with form: RegistrationForm) {
    guard let email = form.email else {
        print("Email not provided")
        return
    }
    print("Registering user with email \(email)")
} Conclusion: Why Optionals Are Essential for Professionals Optionals are a critical part of writing reliable code in Swift. Using Optional Binding, guard let, Nil-Coalescing, and Optional Chaining shows a commitment to building robust and secure applications. In my iOS development experience, I consistently use these techniques to write resilient code that withstands unpredictable conditions and missing data. Optionals in Swift are one of the language's most convenient and powerful tools, allowing you to handle missing values safely and prevent crashes. Using Optionals is an essential part of iOS development, especially when dealing with data from users or external sources. In this article, we’ll dive into both basic and advanced methods for working with Optionals, showing how to use them in real-world scenarios to improve code reliability. What Are Optionals and Why Do We Need Them? What Are Optionals and Why Do We Need Them? Optionals in Swift allow a variable to hold a value or be empty (nil). This is particularly useful when data comes from unstable sources, like user input, databases, or servers, where data presence isn’t always guaranteed. Key Benefits of Optionals: Safety: Missing data doesn’t lead to app crashes. Clarity: Using ? indicates that a value may be absent. Safety: Missing data doesn’t lead to app crashes. Safety: Missing data doesn’t lead to app crashes. Safety: Clarity: Using ? indicates that a value may be absent. Clarity: Using ? indicates that a value may be absent. Clarity: ? Simple Example: Simple Example: var userName: String? = "Alice"
userName = nil  // Now the variable can have no value var userName: String? = "Alice"
userName = nil  // Now the variable can have no value In this example, userName can either be a string or nil. If the value is missing, Swift allows you to handle it smoothly, making the app more resilient. userName Working with Optionals in Swift Working with Optionals in Swift Method

When to Use

Example Code



Forced Unwrapping

If you’re sure the value isn’t nil.

let unwrappedName = userName!



Optional Binding (if let)

For safely unwrapping and handling missing data.

if let unwrappedName = userName { ... } else { print("No name provided") }



guard let

Checks value and exits function if data is nil.

guard let unwrappedName = userName else { return }



Nil-Coalescing (??)

To set a default value if the variable is nil.

let providedName = userName ?? "Unknown"



Optional Chaining

For safe access to nested values.

let userNameLength = user?.profile?.name?.count Method

When to Use

Example Code Forced Unwrapping

If you’re sure the value isn’t nil.

let unwrappedName = userName! Optional Binding (if let)

For safely unwrapping and handling missing data.

if let unwrappedName = userName { ... } else { print("No name provided") } guard let

Checks value and exits function if data is nil.

guard let unwrappedName = userName else { return } Nil-Coalescing (??)

To set a default value if the variable is nil.

let providedName = userName ?? "Unknown" Optional Chaining

For safe access to nested values.

let userNameLength = user?.profile?.name?.count Method When to Use Example Code Method Method When to Use When to Use Example Code Example Code Forced Unwrapping If you’re sure the value isn’t nil. let unwrappedName = userName! Forced Unwrapping Forced Unwrapping Forced Unwrapping If you’re sure the value isn’t nil. If you’re sure the value isn’t nil. If you’re sure the value isn’t nil. let unwrappedName = userName! let unwrappedName = userName! let unwrappedName = userName! Optional Binding (if let) For safely unwrapping and handling missing data. if let unwrappedName = userName { ... } else { print("No name provided") } Optional Binding (if let) Optional Binding (if let) Optional Binding (if let) For safely unwrapping and handling missing data. For safely unwrapping and handling missing data. For safely unwrapping and handling missing data. if let unwrappedName = userName { ... } else { print("No name provided") } if let unwrappedName = userName { ... } else { print("No name provided") } if let unwrappedName = userName { ... } else { print("No name provided") } guard let Checks value and exits function if data is nil. guard let unwrappedName = userName else { return } guard let guard let guard let Checks value and exits function if data is nil. Checks value and exits function if data is nil. Checks value and exits function if data is nil. guard let unwrappedName = userName else { return } guard let unwrappedName = userName else { return } guard let unwrappedName = userName else { return } Nil-Coalescing (??) To set a default value if the variable is nil. let providedName = userName ?? "Unknown" Nil-Coalescing (??) Nil-Coalescing (??) Nil-Coalescing (??) To set a default value if the variable is nil. To set a default value if the variable is nil. To set a default value if the variable is nil. let providedName = userName ?? "Unknown" let providedName = userName ?? "Unknown" let providedName = userName ?? "Unknown" Optional Chaining For safe access to nested values. let userNameLength = user?.profile?.name?.count Optional Chaining Optional Chaining Optional Chaining For safe access to nested values. For safe access to nested values. For safe access to nested values. let userNameLength = user?.profile?.name?.count let userNameLength = user?.profile?.name?.count let userNameLength = user?.profile?.name?.count Example 1(Simple): Forced Unwrapping Forced unwrapping is used when you’re certain the value won’t be nil. This method can cause a crash if the variable is empty, so it’s best avoided unless you’re confident in the value’s presence. let unwrappedName = userName!
print("User Name: \(unwrappedName)") let unwrappedName = userName!
print("User Name: \(unwrappedName)") Forced unwrapping is useful when data is hard-coded or validated by logic. Optional Binding (if let): Safely Extracting Values Optional Binding with if let checks for the presence of a value and only uses it if it exists, avoiding errors. if let if let unwrappedName = userName {
    print("User Name: \(unwrappedName)")
} else {
    print("No name provided")
} if let unwrappedName = userName {
    print("User Name: \(unwrappedName)")
} else {
    print("No name provided")
} This method is particularly handy when working with data from the network or databases, where information may be missing, such as when loading a user profile from an API. Nil-Coalescing (??): A Default Value for Empty Variables The Nil-Coalescing operator ( ?? ) assigns a default value if the variable is nil, making code simpler and more readable. ?? let providedName = userName ?? "Guest"
print("User Name: \(providedName)") let providedName = userName ?? "Guest"
print("User Name: \(providedName)") Nil-Coalescing is useful when you want to avoid empty values and need a standard default. Example 2 (Advanced): Error Control and Protection Let’s move on to advanced examples that demonstrate how Optionals help manage nested data and protect against unpredictable errors. guard let: Reliable Value Checking guard let: Reliable Value Checking guard let checks the value and exits the function if the data is nil, which is useful for mandatory data. guard let func greetUser(_ name: String?) {
    guard let unwrappedName = name else {
        print("No name provided")
        return
    }
    print("Hello, \(unwrappedName)!")
} func greetUser(_ name: String?) {
    guard let unwrappedName = name else {
        print("No name provided")
        return
    }
    print("Hello, \(unwrappedName)!")
} In real work, guard let is convenient for mandatory data checks, like validating form fields. If the value is empty, you can immediately exit the function. guard let Optional Chaining: Safe Access to Nested Values Optional Chaining ( ?. ) allows you to access nested data without the risk of a crash. If any object in the chain is nil, the entire result will be nil. ?. let userNameLength = user?.profile?.name?.count let userNameLength = user?.profile?.name?.count Optional Chaining is particularly useful when working with JSON data and complex structures. For example, if you’re loading a user profile from an API, Optional Chaining simplifies checking each field. Practical Applications of Optionals in iOS Projects Example 1: Retrieving User Profile Data from an API API responses may contain empty fields, and Optionals help handle these situations gracefully without causing crashes. struct UserProfile {
    var name: String?
    var age: Int?
}

func displayUserProfile(user: UserProfile) {
    let displayName = user.name ?? "Guest"
    print("User Profile: \(displayName)")
} struct UserProfile {
    var name: String?
    var age: Int?
}

func displayUserProfile(user: UserProfile) {
    let displayName = user.name ?? "Guest"
    print("User Profile: \(displayName)")
} Here, if the user’s name isn’t specified, a default value—“Guest”—will be used. Example 2: Registration Form Validation Optionals and guard let allow for proper handling of required and optional form fields. For example, checking if an email address is provided during registration. guard let struct RegistrationForm {
    var username: String
    var email: String?
}

func registerUser(with form: RegistrationForm) {
    guard let email = form.email else {
        print("Email not provided")
        return
    }
    print("Registering user with email \(email)")
} struct RegistrationForm {
    var username: String
    var email: String?
}

func registerUser(with form: RegistrationForm) {
    guard let email = form.email else {
        print("Email not provided")
        return
    }
    print("Registering user with email \(email)")
} Conclusion: Why Optionals Are Essential for Professionals Optionals are a critical part of writing reliable code in Swift. Using Optional Binding, guard let , Nil-Coalescing, and Optional Chaining shows a commitment to building robust and secure applications. In my iOS development experience, I consistently use these techniques to write resilient code that withstands unpredictable conditions and missing data. guard let

Building Resilient iOS Apps: A Guide to Swift Optionals

Uni-OVSeg: A Step Towards Efficient and Bias-Resilient Vision Systems

HackerNoon editorial team has launched this interview series with women in tech to celebrate their achievements and share their struggles. We need more women in technology, and by sharing stories, we can encourage many girls to follow their dreams. Share your story today! Tell us about yourself! I am a digital transformation leader in enterprise supply chain operations, advising CPOs/CTOs/CFOs on cloud technology implementations. I have experience working for renowned organizations such as Deloitte Consulting (Big 4) as well as Meta (formerly Facebook). I completed my Masters in Industrial & Systems Engineering from North Carolina State University. Why did you choose this field in the first place? The intersection of technology & industrial operations is very interesting! I’ve always been drawn to problem-solving, and technology offers powerful tools to tackle complex, real-world challenges. Specifically, supply chain technology appealed to me because it impacts nearly every industry and affects millions of people. The opportunity to enhance efficiency, reduce costs, and drive resilience across such a critical function inspired me to pursue this field. What tech are you most excited/passionate about right now and why? Right now, I’m most excited about AI-driven analytics and automation. These technologies hold incredible potential for predictive decision-making and real-time optimizations in supply chain operations. AI allows us to move from reactive to proactive, making entire supply chains more responsive and resilient to changes or disruptions. What tech are you most worried about right now and why? Data privacy and security in the context of cloud computing is a concern for me. As more companies adopt cloud solutions, there’s an increasing need to protect sensitive information. Any breach can have serious consequences not only for individual companies but for the industry as a whole. Ensuring robust security protocols and continuous updates is essential. What are your hobbies and interests outside of tech? Outside of work, I love hiking, traveling, and cooking (as a creative outlet). Being in nature helps me recharge and gain perspective. Traveling keeps me inspired and curious. I have traveled to 45 countries and hiked in 33 national parks across the globe. Let's talk about breaking the glass ceiling. What were the biggest challenges you faced as a woman in tech, and how did you deal with them? One of the biggest challenges was proving my technical competence in a male-dominated environment, especially early on in my career. I dealt with it by constantly learning, and building a strong network of mentors and peers who provided support and guidance. Eventually, my work spoke for itself, but it took persistence. Any questionable misogynistic story/situation you faced/handled, and you want to share with the HackerNoon Fam? There have been moments where I felt my ideas were dismissed initially, only to be recognized when repeated by a male colleague. I’ve learned to assert myself respectfully and speak up. While it’s disappointing that these situations still happen, addressing them directly has helped shift the dynamics in those teams. What was the biggest setback/failure that you faced, and how did you manage it? I have learned to be agile through experience. It has been through several small lessons, but they have taught me the importance of agility and learning to deal with failure by applying lessons quickly. What's your biggest achievement that you're really proud of? One of my proudest achievements was being a part of a large-scale cloud transformation project for a global non-profit organization that completely overhauled access to life-saving necessities. The results were transformative; we significantly reduced costs and improved efficiency. Seeing the direct impact of our work on people’s lives was incredibly rewarding. In your opinion, why do we see this huge gender gap in the tech industry, and how can we reduce it? The gender gap is largely due to a combination of factors—lack of representation, stereotypes, and limited access to mentorship. To reduce this gap, we need to normalize women in technical roles and create support systems through mentorship, networking, and training programs. Encouraging STEM education for young girls is also crucial to growing interest early on. Who is your tech idol? Why? I find inspiration in the collective efforts of women in tech who are breaking barriers and redefining the industry. From engineers and entrepreneurs to advocates and educators, this community is making significant strides toward inclusivity and innovation. Their dedication to mentoring others, sharing knowledge, and pushing for diversity motivates me to contribute positively to the field and to support the next generation of tech leaders. Do you have any advice for aspiring girls who want to join the field? Stay confident! The tech industry thrives on diverse perspectives, and there’s room for anyone ready to learn and bring fresh ideas. Seek out mentors, stay curious, and don’t let doubt stop you. Each step you take helps open doors for others. HackerNoon editorial team has launched this interview series with women in tech to celebrate their achievements and share their struggles. We need more women in technology, and by sharing stories, we can encourage many girls to follow their dreams. Share your story today! HackerNoon editorial team has launched this interview series with women in tech to celebrate their achievements and share their struggles. We need more women in technology, and by sharing stories, we can encourage many girls to follow their dreams. Share your story today ! this interview series with women in tech Share your story today Tell us about yourself! I am a digital transformation leader in enterprise supply chain operations, advising CPOs/CTOs/CFOs on cloud technology implementations. I have experience working for renowned organizations such as Deloitte Consulting (Big 4) as well as Meta (formerly Facebook). I completed my Masters in Industrial & Systems Engineering from North Carolina State University. Why did you choose this field in the first place? Why did you choose this field in the first place? The intersection of technology & industrial operations is very interesting! I’ve always been drawn to problem-solving, and technology offers powerful tools to tackle complex, real-world challenges. Specifically, supply chain technology appealed to me because it impacts nearly every industry and affects millions of people. The opportunity to enhance efficiency, reduce costs, and drive resilience across such a critical function inspired me to pursue this field. What tech are you most excited/passionate about right now and why? Right now, I’m most excited about AI-driven analytics and automation. These technologies hold incredible potential for predictive decision-making and real-time optimizations in supply chain operations. AI allows us to move from reactive to proactive, making entire supply chains more responsive and resilient to changes or disruptions. What tech are you most worried about right now and why? What tech are you most worried about right now and why? Data privacy and security in the context of cloud computing is a concern for me. As more companies adopt cloud solutions, there’s an increasing need to protect sensitive information. Any breach can have serious consequences not only for individual companies but for the industry as a whole. Ensuring robust security protocols and continuous updates is essential. What are your hobbies and interests outside of tech? Outside of work, I love hiking, traveling, and cooking (as a creative outlet). Being in nature helps me recharge and gain perspective. Traveling keeps me inspired and curious. I have traveled to 45 countries and hiked in 33 national parks across the globe. Let's talk about breaking the glass ceiling. What were the biggest challenges you faced as a woman in tech, and how did you deal with them? One of the biggest challenges was proving my technical competence in a male-dominated environment, especially early on in my career. I dealt with it by constantly learning, and building a strong network of mentors and peers who provided support and guidance. Eventually, my work spoke for itself, but it took persistence. Any questionable misogynistic story/situation you faced/handled, and you want to share with the HackerNoon Fam? Any questionable misogynistic story/situation you faced/handled, and you want to share with the HackerNoon Fam? There have been moments where I felt my ideas were dismissed initially, only to be recognized when repeated by a male colleague. I’ve learned to assert myself respectfully and speak up. While it’s disappointing that these situations still happen, addressing them directly has helped shift the dynamics in those teams. What was the biggest setback/failure that you faced, and how did you manage it? What was the biggest setback/failure that you faced, and how did you manage it? I have learned to be agile through experience. It has been through several small lessons, but they have taught me the importance of agility and learning to deal with failure by applying lessons quickly. What's your biggest achievement that you're really proud of? What's your biggest achievement that you're really proud of? One of my proudest achievements was being a part of a large-scale cloud transformation project for a global non-profit organization that completely overhauled access to life-saving necessities. The results were transformative; we significantly reduced costs and improved efficiency. Seeing the direct impact of our work on people’s lives was incredibly rewarding. In your opinion, why do we see this huge gender gap in the tech industry, and how can we reduce it? In your opinion, why do we see this huge gender gap in the tech industry, and how can we reduce it? The gender gap is largely due to a combination of factors—lack of representation, stereotypes, and limited access to mentorship. To reduce this gap, we need to normalize women in technical roles and create support systems through mentorship, networking, and training programs. Encouraging STEM education for young girls is also crucial to growing interest early on. Who is your tech idol? Why? I find inspiration in the collective efforts of women in tech who are breaking barriers and redefining the industry. From engineers and entrepreneurs to advocates and educators, this community is making significant strides toward inclusivity and innovation. Their dedication to mentoring others, sharing knowledge, and pushing for diversity motivates me to contribute positively to the field and to support the next generation of tech leaders. Do you have any advice for aspiring girls who want to join the field? Stay confident! The tech industry thrives on diverse perspectives, and there’s room for anyone ready to learn and bring fresh ideas. Seek out mentors, stay curious, and don’t let doubt stop you. Each step you take helps open doors for others.

Women in Tech: Megha Chaudhary on Leadership, Resilience, and Inspiring the Next Generation

SINGAPORE, November 9, 2024 –MEXC,a leading global cryptocurrency exchange, has pledged a __€100,000 donation __to support relief efforts following the devastating floods that recently struck Valencia, Spain. Heavy rainfall has caused severe flooding across parts of Spain, resulting in widespread damage to communities and infrastructure.To provide assistance to this humanitarian crisis, MEXC has mobilized resources to support affected individuals and contribute to local recovery initiatives Managed by the MEXC Spain Team, the €100,000 donation aims to support immediate relief efforts and provide vital resources to those impacted by the disaster. These funds will assist the Spanish Red Cross in the delivery of essential aid, including food, medical supplies, and emergency shelter, alleviating the suffering of those affected by this disaster. "Our hearts go out to all those impacted. During this challenging time, we are committed to working closely with local partners to understand how we can best support them," said Tracy Jin, VP of MEXC.“We’re honored to stand alongside our users and the community, doing everything we can to provide a safe space where they can find relief and support as they rebuild and work to keep their loved ones safe." Since the onset of the crisis, the MEXC Spain team has collaborated closely with local relief organizations to ensure aid reaches where it is most needed. This initiative reaffirms MEXC’s longstanding commitment to supporting communities in times of need, exemplified by its recent efforts during the 2023 Türkiye earthquake, where MEXC contributed 1 million Turkish Lira to aid emergency responses. Partnering with local organizations, MEXC provided essential support to expedite relief efforts and address urgent needs on the ground. MEXC remains steadfast in its dedication to delivering timely, impactful assistance, strengthening resilience and solidarity in the communities it serves. About MEXC Founded in 2018, __MEXC __is dedicated to being "Your Easiest Way to Crypto." Known for its extensive selection of trending tokens, airdrop opportunities, and low fees, MEXC serves over 30 million users across 170+ countries. With a focus on accessibility and efficiency, our advanced trading platform appeals to both new traders and seasoned investors alike. MEXC provides a seamless, secure, and rewarding gateway to the world of digital assets. This story was distributed as a release by Btcwire under HackerNoon’s Business Blogging Program. Learn more about the program here SINGAPORE, November 9, 2024 –MEXC,a leading global cryptocurrency exchange, has pledged a __ €100,000 donation __to support relief efforts following the devastating floods that recently struck Valencia, Spain. €100,000 donation Heavy rainfall has caused severe flooding across parts of Spain, resulting in widespread damage to communities and infrastructure.To provide assistance to this humanitarian crisis, MEXC has mobilized resources to support affected individuals and contribute to local recovery initiatives Managed by the MEXC Spain Team , the €100,000 donation aims to support immediate relief efforts and provide vital resources to those impacted by the disaster. These funds will assist the Spanish Red Cross in the delivery of essential aid, including food, medical supplies, and emergency shelter, alleviating the suffering of those affected by this disaster. MEXC Spain Team MEXC Spain Team "Our hearts go out to all those impacted. During this challenging time, we are committed to working closely with local partners to understand how we can best support them," said Tracy Jin, VP of MEXC.“We’re honored to stand alongside our users and the community, doing everything we can to provide a safe space where they can find relief and support as they rebuild and work to keep their loved ones safe." "Our hearts go out to all those impacted. During this challenging time, we are committed to working closely with local partners to understand how we can best support them," said Tracy Jin, VP of MEXC.“We’re honored to stand alongside our users and the community, doing everything we can to provide a safe space where they can find relief and support as they rebuild and work to keep their loved ones safe." Since the onset of the crisis, the MEXC Spain team has collaborated closely with local relief organizations to ensure aid reaches where it is most needed. This initiative reaffirms MEXC’s longstanding commitment to supporting communities in times of need, exemplified by its recent efforts during the 2023 Türkiye earthquake, where MEXC contributed 1 million Turkish Lira to aid emergency responses . Partnering with local organizations, MEXC provided essential support to expedite relief efforts and address urgent needs on the ground. MEXC remains steadfast in its dedication to delivering timely, impactful assistance, strengthening resilience and solidarity in the communities it serves. MEXC Spain team MEXC Spain team MEXC contributed 1 million Turkish Lira to aid emergency responses MEXC contributed 1 million Turkish Lira to aid emergency responses About MEXC Founded in 2018, __ MEXC __is dedicated to being "Your Easiest Way to Crypto." Known for its extensive selection of trending tokens, airdrop opportunities, and low fees, MEXC serves over 30 million users across 170+ countries. MEXC With a focus on accessibility and efficiency, our advanced trading platform appeals to both new traders and seasoned investors alike. MEXC provides a seamless, secure, and rewarding gateway to the world of digital assets. This story was distributed as a release by Btcwire under HackerNoon’s Business Blogging Program. Learn more about the program here This story was distributed as a release by Btcwire under HackerNoon’s Business Blogging Program. Learn more about the program here here here

Floods In Spain: Crypto Exchange MEXC Donates €100,000 To Support Local Relief And Resilience

Oorstromings in Spanje: Crypto Exchange MEXC skenk € 100 000 om plaaslike verligting en veerkragtigheid te ondersteun

Oversvømmelser i Spanien: Crypto Exchange MEXC donerer €100.000 for at støtte lokal nødhjælp og modstandskraft

Überschwemmungen in Spanien: Kryptobörse MEXC spendet 100.000 € zur Unterstützung lokaler Hilfsmaßnahmen und Widerstandsfähigkeit

Inundaciones en España: la plataforma de intercambio de criptomonedas MEXC dona 100.000 € para apoyar la ayuda y la resiliencia locales

سیل در اسپانیا: Crypto Exchange MEXC 100,000 یورو برای حمایت از امداد و مقاومت محلی اهدا می کند

Banjir di Spanyol: Bursa Kripto MEXC Donasikan €100.000 untuk Mendukung Pemulihan dan Ketahanan Lokal

スペインの洪水：暗号通貨取引所MEXCが地元の救援と復興支援に10万ユーロを寄付

Mpela Na Espagne: Crypto Exchange MEXC Epesi €100.000 Pona Ko Soutenir Relief Local Et Resilience

Tondra-drano any Espaina: Ny Crypto Exchange MEXC dia manome €100,000 hanohanana ny fanampiana sy ny faharetana eo an-toerana

Inundații în Spania: Crypto Exchange MEXC donează 100.000 EUR pentru a sprijini ajutorul și rezistența locală

Umwuzure Muri Espagne: Crypto Guhana MEXC Yatanze € 100.000 yo Gufasha Inkeragutabara no Kwihangana

Ispaniýadaky suw joşmalary: Kripto alyş-çalyş MEXC ýerli kömek we çydamlylygy goldamak üçin 100,000 funt sterling berdi

Table of Links Abstract and I. Introduction II. Background III. Problem Definition IV. DAG-Oriented Solutions V. Game Theoretical Analysis VI. Simulation Model VII. Evaluation VIII. Countermeasures IX. Discussion and Future Work X. Related Work XI. Conclusion and References IX. DISCUSSION AND FUTURE WORK Centralization. In the scope of Experiment I (see Sec. VII-A), we demonstrated that the relative profit of greedy miners decreases as their number G increases. Therefore, greedy miners are incentivized to form a single mining pool, maximizing their relative profit. As a negative consequence, the decentralization of the blockchain network is impacted. Throughout. In our simulations, we adjusted the parameters to focus on investigating potential issues related to decreased profits and general throughput (collisions), rather than maximizing the simulated protocol’s throughput. However, we argue that this had no impact on the results of our evaluation, and similar results can be achieved even with higher throughput (i.e., τ > λ). Connectivity of Miners. In our experiments, we used γ = 1 and equally connected honest and greedy miners. However, in practice, greedy miners can be better connected since they want to include high-value transactions as the first ones, and thus profit even more. Assuming other γ than 1 can result only in lower profits of (potentially) weakly connected honest miners while it does reduce the profits of greedy miners who are incentivized to be strongly connected regardless of γ. Future Work. We plan to experiment in detail with the methods enabling DAG-PROTOCOLS to be resilient to demonstrated attacks even in the context of Proof-of-Stake protocols. As the next step in theoretical analysis, it would be interesting to examine the dynamic behavior of greedy miners who adapt their strategies (switching between multiple strategies) to the current conditions of the protocol. Last, we attributed a fee to the first miner who included a transaction in our simulations, but other schemes for distributing the fees among all miners could also be investigated. However, such schemes would not eliminate collisions (and thus decreased throughput), thereby enabling miners still to select transactions greedily due to varying fees. Authors:
(1) Martin Peresıni, Brno University of Technology, Faculty of Information Technology (iperesini@fit.vut.cz);
(2) Ivan Homoliak, Brno University of Technology, Faculty of Information Technology (ihomoliak@fit.vut);
(3) Federico Matteo Bencic, University of Zagreb, Faculty of Electrical Engineering and Computing (federico-matteo.bencic@fer.hr);
(4) Martin Hruby, Brno University of Technology, Faculty of Information Technology (hruby@fit.vut.cz);
(5) Kamil Malinka, Brno University of Technology, Faculty of Information Technology (malinka@fit.vut). This paper is available on arxiv under CC BY 4.0 DEED license. Table of Links Abstract and I. Introduction Abstract and I. Introduction II. Background II. Background III. Problem Definition III. Problem Definition IV. DAG-Oriented Solutions IV. DAG-Oriented Solutions V. Game Theoretical Analysis V. Game Theoretical Analysis VI. Simulation Model VI. Simulation Model VII. Evaluation VII. Evaluation VIII. Countermeasures VIII. Countermeasures IX. Discussion and Future Work IX. Discussion and Future Work X. Related Work X. Related Work XI. Conclusion and References XI. Conclusion and References IX. DISCUSSION AND FUTURE WORK Centralization . In the scope of Experiment I (see Sec. VII-A), we demonstrated that the relative profit of greedy miners decreases as their number G increases. Therefore, greedy miners are incentivized to form a single mining pool, maximizing their relative profit. As a negative consequence, the decentralization of the blockchain network is impacted. Centralization Throughout . In our simulations, we adjusted the parameters to focus on investigating potential issues related to decreased profits and general throughput (collisions), rather than maximizing the simulated protocol’s throughput. However, we argue that this had no impact on the results of our evaluation, and similar results can be achieved even with higher throughput (i.e., τ > λ). Throughout Connectivity of Miners . In our experiments, we used γ = 1 and equally connected honest and greedy miners. However, in practice, greedy miners can be better connected since they want to include high-value transactions as the first ones, and thus profit even more. Assuming other γ than 1 can result only in lower profits of (potentially) weakly connected honest miners while it does reduce the profits of greedy miners who are incentivized to be strongly connected regardless of γ. Connectivity of Miners Future Work. We plan to experiment in detail with the methods enabling DAG-PROTOCOLS to be resilient to demonstrated attacks even in the context of Proof-of-Stake protocols. As Future Work. the next step in theoretical analysis, it would be interesting to examine the dynamic behavior of greedy miners who adapt their strategies (switching between multiple strategies) to the current conditions of the protocol. Last, we attributed a fee to the first miner who included a transaction in our simulations, but other schemes for distributing the fees among all miners could also be investigated. However, such schemes would not eliminate collisions (and thus decreased throughput), thereby enabling miners still to select transactions greedily due to varying fees. Authors: (1) Martin Peresıni, Brno University of Technology, Faculty of Information Technology (iperesini@fit.vut.cz); (2) Ivan Homoliak, Brno University of Technology, Faculty of Information Technology (ihomoliak@fit.vut); (3) Federico Matteo Bencic, University of Zagreb, Faculty of Electrical Engineering and Computing (federico-matteo.bencic@fer.hr); (4) Martin Hruby, Brno University of Technology, Faculty of Information Technology (hruby@fit.vut.cz); (5) Kamil Malinka, Brno University of Technology, Faculty of Information Technology (malinka@fit.vut). Authors: Authors: (1) Martin Peresıni, Brno University of Technology, Faculty of Information Technology (iperesini@fit.vut.cz); (2) Ivan Homoliak, Brno University of Technology, Faculty of Information Technology (ihomoliak@fit.vut); (3) Federico Matteo Bencic, University of Zagreb, Faculty of Electrical Engineering and Computing (federico-matteo.bencic@fer.hr); (4) Martin Hruby, Brno University of Technology, Faculty of Information Technology (hruby@fit.vut.cz); (5) Kamil Malinka, Brno University of Technology, Faculty of Information Technology (malinka@fit.vut). This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv available on arxiv

The Future of DAG Protocols: Connectivity, Centralization, and Resilience

Ethereum Meets Distributed Validator Technology: A New Era for Resilient Financial Systems

In my previous article, Managing Architectural Tech Debt, I talked about understanding and managing architectural technical debt. Architectural technical debt is the often ignored, but ironically, one of the most damaging, categories of technical debt. In this article, I want to dive deeper into one way to manage architectural technical debt (and technical debt as a whole)—architectural observability (AO). AO is a new category of observability that I believe is just as important, if not more so, as application performance management (APM). I believe we need to shift left observability—to the architectural stage—where we can not just see symptoms, but fix core problems. Let’s take a look. APM Is (Half) the Answer You already know that APM is important. Gartner defines it as “software that enables the observation and analysis of application health, performance and user experience.” And IDC reports that companies using APM solutions see a 2.5x improvement in mean time to resolution (MTTR) and a 50% reduction in the number of incidents. APM and observability: Helps to ensure better user experiences by monitoring, in real-time, performance and responsiveness.
Can help identify defects.
Can provide data to teams, such as usage patterns, bottlenecks, and overall health to keep systems healthy. Overall, APM has become a necessary tool for troubleshooting and fixing issues in enterprise environments. APM has become table stakes. And APM works! In my current role, we use APM to observe the usage of our APIs to understand the breakdown of URI (uniform resource identifier) requests across all of our consumers. When our APIs are not functioning as expected, we lean to APM in order to gain visibility into performance bottlenecks. In cases where an alert is triggered, the same interface can be utilized for initial troubleshooting efforts in order to help pin down the root cause. But even though APM works, there’s a problem. APM identifies the symptoms of the defects, but not the actual defects themselves. It’s up to the team to track down why the problems are occurring. And with the pressure we often feel in prod to “just fix the problem as fast as you can,” I often see that while symptoms may be addressed, teams don’t have the time (or organizational support) to find and fix the actual core problems. Imagine taking aspirin because you get a headache every night, but never taking the time to figure out why you keep having headaches. To find—and address—the why of our defects, we need architectural observability. Architectural Observability: Getting to the Real Answers We need to shift our processes left, stop focusing on symptoms, and instead focus on the root cause of these problems and actually reduce the number of incidents caught with APM. That’s where architectural observability comes in. Architectural observability is the ability to analyze an application’s architecture (both statically and dynamically), understand how it works, observe changes, and identify and fix architectural technical debt. Architectural observability is the next step in observability tools. Architectural observability gives you visibility into your application architecture, helping you solve problems (not just identify symptoms) earlier in the SDLC by identifying architectural issues. You probably already have the data you need to implement AO—it uses the same data sources as APM (for example, OpenTelemetry (OTel). But AO takes that data and applies a layer of intelligence that focuses on analyzing the architecture and the sources of architectural technical debt. For example, an AO tool might analyze: Architectural complexity - The interdependence and relationships of services within the architecture, the number of flows in a service, identifying multi-hop flows and circular flows. Dependency mappings - Relationships among services including circular dependencies. Architectural drift - What has changed since your last release, what new domains/services were added, what new dependencies and flows were introduced. Technical debt - Such as resource exclusivity, service dependencies, duplicate services that should be merged, and complexity. Technical debt is a huge problem in the industry. 70% of organizations say that technical debt is a major obstacle to innovation. Database-related issues - Examine if multiple services are accessing tables. Architectural observability is proactive and strategic. Where APM tools alert on the leaks in the roof when it is already raining, AO identifies architectural issues that can lead to those leaks, way before they actually occur. Using Tools to Gain Architectural Observability Used well, AO doesn’t just help you find issues earlier, but helps you: Truly discover and understand your architecture and its relationships and dependencies.
Prevent issues caused by architectural changes.
Make systems more resilient and scalable by continually monitoring, modernizing, and strengthening your architecture.
Minimize technical debt. I love that last one. As I pointed out in my last article, architectural debt is a foe of mine that I have been battling for over a decade. Architectural observability is a new field and is starting to gain traction as something teams must have. There aren’t many tools yet built around the concept, but let’s look at how your team might use one of the first AO tools—vFunction—to gain AO. Once you’ve connected to your applications (through the OTel connector or similar), the tool analyzes your system (in this case with vFunction, it’s using AI to understand and analyze your architecture). Then you get a report on the current state of your architecture. You’ll see details such as: A visualization of the architecture across your entire app portfolio
A map of services and entry points, cross services APIs, and external APIs
Exclusivity of database tables (Kafka, Redis, MongoDB) and other resources
Complexity scores
And more… And you can use architectural observability to monitor your architecture not just in the present state, but dynamically as it changes. Changes to your architecture (a.k.a., architectural drift)? You’ll know right away.
Add a dependency impacting resiliency? You’ll catch it before migrating.
Did you create a circular flow? Did you significantly increase the complexity of your system? Find out early. Incurring even more technical debt? You can’t hide from it now. With architectural observability, you now have hard proof of how architectural debt is affecting your systems and how, by using AO, you can identify and prioritize the actual problems in your systems early and often, rather than only addressing the symptoms in production. AO makes applications more resilient, more scalable, and helps your team move faster. And AO can help proactively. Is your team moving from a monolith to a microservice? AO can give you a plan to move your architecture forward. With AO, you could analyze your monolith, understand how its domains and functionality are structured and connected, and then get actionable steps on how to modularize and move the functionality to microservices. And once you have a distributed architecture (microservices or distributed monoliths), you’ll want to make sure your architecture doesn’t drift or get more complex to the point that things start to break, you lose control, and you have to slow down your engineering velocity. AO keeps your applications in check whether monolith or microservices. Architectural Observability Gives You Better Systems My readers may recall that I have been focused on the following mission statement, which I feel can apply to any IT professional: “Focus your time on delivering features/functionality that extends the value of your intellectual property. Leverage frameworks, products, and services for everything else.” - J. Vester Architectural observability adheres to my mission statement perfectly. By moving from plain vanilla observability to architectural observability, we can shift left for more reliable, more resilient, and better-performing systems. This shift affords us more time to spend on the business problems that our teams understand best. As John F. Kennedy once said: “The best time to repair the roof is when the sun is shining.” Architectural observability should be placed on the same level (or higher) as APM. With AO, teams can truly understand their architecture, have a broader and more insightful view of their applications than with APM alone, and fix problems earlier. Have a really great day! In my previous article, Managing Architectural Tech Debt , I talked about understanding and managing architectural technical debt. Architectural technical debt is the often ignored, but ironically, one of the most damaging , categories of technical debt. Managing Architectural Tech Debt architectural the most damaging In this article, I want to dive deeper into one way to manage architectural technical debt (and technical debt as a whole)— architectural observability (AO) . AO is a new category of observability that I believe is just as important, if not more so, as application performance management (APM). I believe we need to shift left observability—to the architectural stage—where we can not just see symptoms, but fix core problems. architectural observability (AO) Let’s take a look. APM Is (Half) the Answer You already know that APM is important. Gartner defines it as “software that enables the observation and analysis of application health, performance and user experience.” And IDC reports that companies using APM solutions see a 2.5x improvement in mean time to resolution (MTTR) and a 50% reduction in the number of incidents. IDC reports APM and observability: Helps to ensure better user experiences by monitoring, in real-time, performance and responsiveness. Can help identify defects. Can provide data to teams, such as usage patterns, bottlenecks, and overall health to keep systems healthy. Helps to ensure better user experiences by monitoring, in real-time, performance and responsiveness. Can help identify defects. Can provide data to teams, such as usage patterns, bottlenecks, and overall health to keep systems healthy. Overall, APM has become a necessary tool for troubleshooting and fixing issues in enterprise environments. APM has become table stakes. And APM works! In my current role, we use APM to observe the usage of our APIs to understand the breakdown of URI (uniform resource identifier) requests across all of our consumers. When our APIs are not functioning as expected, we lean to APM in order to gain visibility into performance bottlenecks. In cases where an alert is triggered, the same interface can be utilized for initial troubleshooting efforts in order to help pin down the root cause. But even though APM works, there’s a problem. APM identifies the symptoms of the defects, but not the actual defects themselves . It’s up to the team to track down why the problems are occurring. And with the pressure we often feel in prod to “just fix the problem as fast as you can,” I often see that while symptoms may be addressed, teams don’t have the time (or organizational support) to find and fix the actual core problems. but not the actual defects themselves why Imagine taking aspirin because you get a headache every night, but never taking the time to figure out why you keep having headaches. To find—and address—the why of our defects, we need architectural observability . why architectural observability Architectural Observability: Getting to the Real Answers We need to shift our processes left, stop focusing on symptoms, and instead focus on the root cause of these problems and actually reduce the number of incidents caught with APM. root cause of these problems That’s where architectural observability comes in. Architectural observability is the ability to analyze an application’s architecture (both statically and dynamically), understand how it works, observe changes, and identify and fix architectural technical debt. Architectural observability Architectural observability is the next step in observability tools. Architectural observability gives you visibility into your application architecture, helping you solve problems (not just identify symptoms) earlier in the SDLC by identifying architectural issues. You probably already have the data you need to implement AO—it uses the same data sources as APM (for example, OpenTelemetry (OTel). But AO takes that data and applies a layer of intelligence that focuses on analyzing the architecture and the sources of architectural technical debt. For example, an AO tool might analyze: Architectural complexity - The interdependence and relationships of services within the architecture, the number of flows in a service, identifying multi-hop flows and circular flows. Architectural complexity - The interdependence and relationships of services within the architecture, the number of flows in a service, identifying multi-hop flows and circular flows. Architectural complexity Dependency mappings - Relationships among services including circular dependencies. Dependency mappings - Relationships among services including circular dependencies. Dependency mappings Architectural drift - What has changed since your last release, what new domains/services were added, what new dependencies and flows were introduced. Architectural drift - What has changed since your last release, what new domains/services were added, what new dependencies and flows were introduced. Architectural drift Technical debt - Such as resource exclusivity, service dependencies, duplicate services that should be merged, and complexity. Technical debt is a huge problem in the industry. 70% of organizations say that technical debt is a major obstacle to innovation. Technical debt - Such as resource exclusivity, service dependencies, duplicate services that should be merged, and complexity. Technical debt is a huge problem in the industry. 70% of organizations say that technical debt is a major obstacle to innovation. Technical debt major obstacle to innovation. Database-related issues - Examine if multiple services are accessing tables. Database-related issues - Examine if multiple services are accessing tables. Database-related issues Architectural observability is proactive and strategic. Where APM tools alert on the leaks in the roof when it is already raining, AO identifies architectural issues that can lead to those leaks, way before they actually occur. Using Tools to Gain Architectural Observability Used well, AO doesn’t just help you find issues earlier, but helps you: Truly discover and understand your architecture and its relationships and dependencies. Prevent issues caused by architectural changes. Make systems more resilient and scalable by continually monitoring, modernizing, and strengthening your architecture. Minimize technical debt. Truly discover and understand your architecture and its relationships and dependencies. Prevent issues caused by architectural changes. Prevent Make systems more resilient and scalable by continually monitoring, modernizing, and strengthening your architecture. Minimize technical debt. I love that last one. As I pointed out in my last article , architectural debt is a foe of mine that I have been battling for over a decade. my last article Architectural observability is a new field and is starting to gain traction as something teams must have. There aren’t many tools yet built around the concept, but let’s look at how your team might use one of the first AO tools—vFunction—to gain AO. Once you’ve connected to your applications (through the OTel connector or similar), the tool analyzes your system (in this case with vFunction, it’s using AI to understand and analyze your architecture). Then you get a report on the current state of your architecture. You’ll see details such as: A visualization of the architecture across your entire app portfolio A map of services and entry points, cross services APIs, and external APIs Exclusivity of database tables (Kafka, Redis, MongoDB) and other resources Complexity scores And more… A visualization of the architecture across your entire app portfolio A map of services and entry points, cross services APIs, and external APIs Exclusivity of database tables (Kafka, Redis, MongoDB) and other resources Complexity scores And more… And you can use architectural observability to monitor your architecture not just in the present state, but dynamically as it changes. Changes to your architecture (a.k.a., architectural drift)? You’ll know right away. Add a dependency impacting resiliency? You’ll catch it before migrating. Did you create a circular flow? Did you significantly increase the complexity of your system? Find out early. Changes to your architecture (a.k.a., architectural drift)? You’ll know right away. Add a dependency impacting resiliency? You’ll catch it before migrating. Did you create a circular flow? Did you significantly increase the complexity of your system? Find out early. Incurring even more technical debt? You can’t hide from it now. more With architectural observability, you now have hard proof of how architectural debt is affecting your systems and how, by using AO, you can identify and prioritize the actual problems in your systems early and often, rather than only addressing the symptoms in production. AO makes applications more resilient, more scalable, and helps your team move faster. And AO can help proactively. Is your team moving from a monolith to a microservice? AO can give you a plan to move your architecture forward. With AO, you could analyze your monolith, understand how its domains and functionality are structured and connected, and then get actionable steps on how to modularize and move the functionality to microservices. And once you have a distributed architecture (microservices or distributed monoliths), you’ll want to make sure your architecture doesn’t drift or get more complex to the point that things start to break, you lose control, and you have to slow down your engineering velocity. AO keeps your applications in check whether monolith or microservices. Architectural Observability Gives You Better Systems My readers may recall that I have been focused on the following mission statement, which I feel can apply to any IT professional: “Focus your time on delivering features/functionality that extends the value of your intellectual property. Leverage frameworks, products, and services for everything else.” - J. Vester “Focus your time on delivering features/functionality that extends the value of your intellectual property. Leverage frameworks, products, and services for everything else.” - J. Vester Architectural observability adheres to my mission statement perfectly. By moving from plain vanilla observability to architectural observability , we can shift left for more reliable, more resilient, and better-performing systems. This shift affords us more time to spend on the business problems that our teams understand best. architectural observability As John F. Kennedy once said: “The best time to repair the roof is when the sun is shining.” Architectural observability should be placed on the same level (or higher) as APM. With AO, teams can truly understand their architecture, have a broader and more insightful view of their applications than with APM alone, and fix problems earlier. Have a really great day!

From Observability to Architectural Observability—Shifting Left for Resiliency

Stories, News & Mentions about RESILIO

Resilio’s Stories on HackerNoon