Menene DeFi Aggregator | Manyan 5 DeFi aggregators.

A cikin wannan sakon, zaku koyi Menene DeFi Aggregator | Manyan 5 DeFi aggregators

1. Menene DeFi?

DeFi yana nufin raba kudi; yana kawar da masu shiga tsakani tsakanin mutane ko kungiyoyi masu yin mu'amalar kudi. Muhimman abubuwan da suka shafi su ne; kunna software na dubawa, amfani da lokuta, da stablecoins. Ana sanya hannu kan kwangiloli ta hanyar lantarki, tare da sharuɗɗan da aka bayyana a cikinsu.

Makullin kowane DeFi ya ƙunshi hanyar ciniki a kan DeFi, wanda ƙila za a iya yin ciniki tare da wasu ko a'a. Kwangila ko sharuɗɗan kasuwanci wani ne; yarjejeniya ce da ke aiki bisa doka akan DeFi. Hakanan akwai tari inda ake yin ciniki. A can, zaku iya neman lamuni da sauran ayyukan da aka yi. A ƙarshe shine mai tarawa wanda ke haɗa yadudduka daban-daban.

Kodayake DeFi shine ra'ayi mai girma, shine makomar kudi da ma'amaloli na duniya, musamman tare da halin yanzu na hauhawar farashin kaya. Fasahar da ke kewaye da DeFi har yanzu tana kan ci gaba, kamar yadda ya bayyana a cikin wasu masu tarawa da suka yi karo da juna, wanda ke haifar da hasara mai yawa ga masu saka hannun jari da yawa. Akwai buƙatar ƙungiyoyi masu sarrafawa don sa ido kan ayyukan masu tara DeFi da yawa.

Menene Aggregator DeFi?

Mai tarawa na DeFi yana haɗu da cinikai a kan dandamali daban-daban na kuɗi (DeFi) zuwa wuri ɗaya, yana adana lokacin masu amfani da haɓaka haɓakar kasuwancin cryptocurrency. Kamar yadda sunan ya nuna, DeFi yana bazuwa a cikin blockchain daban-daban kamar Ethereum da Binance Smart Chain. A cikin kowane blockchain akwai yanayin yanayin keɓancewar ka'idojin kuɗi. 

Duk da yake samun zaɓi mai yawa na ka'idoji daban-daban yana da fa'ida don haɓaka saka hannun jari da samun mafi kyawun ƙimar yawan amfanin ƙasa daga lamuni na crypto, inganci da dacewa suna kangewa tunda bayanan kuɗi ya bazu cikin ƙa'idodi da yawa. Wannan shine inda masu tarawa DeFi ke bunƙasa. 

DeFi aggregators suna siffanta mafi kyawun farashi daga DEXs, sabis na ba da lamuni da wuraren waha ruwa zuwa wuri guda domin masu amfani su inganta kasuwancin su. Ba tare da mai tarawa ba, masu amfani suna buƙatar zuwa kowane dandamali akan kowane mutum don kwatanta farashin da zai samar musu da mafi kyawun ciniki. Sannan, mai amfani dole ne ya aiwatar da kowace ma'amala da hannu ta amfani da kwangiloli masu wayo. Duk da yake wannan dabarun na iya zama mai kyau don kasuwancin crypto na yau da kullun, yana iyakancewa waɗanda ke neman aiwatar da dabarun ciniki na ci gaba. 

Ba wai kawai masu tarawa ke jan mafi kyawun farashi ba, amma wasu masu tarawa na DeFi har ma suna ba da wata hanya ta musamman, mai sauƙin amfani don tantancewa da haɗa dabarun ciniki na sauran masu amfani ta hanyar ingantacciyar hanyar ja da sauke. Ta wannan hanyar, masu amfani za su iya ƙirƙirar sabuwar dabara ta nasu ta amfani da wahayin sauran 'yan kasuwa masu nasara. Tsarin ja da sauke kuma yana taimaka wa masu amfani su hango hadaddun ka'idojin DeFi ta hanyar tubalan da za a iya gina su a kan juna.

Aggregators sun sanya UX/UI a kan gaba, suna ba da ƙwarewa mafi girma ga hanyar gargajiya ta mu'amala da hannu tare da yadudduka na ruwa. A sakamakon haka, wannan yana taimaka wa masu amfani waɗanda ba su da matsayin crypto-savvy kamar yadda masana kasuwanci ke kewaya duniyar DeFi cikin sauƙi. 

Matsalolin da ke da yuwuwar yin amfani da mai tara DeFi shine kuɗin gas. Yayin da Ethereum ke ci gaba da kaiwa sabon matsayi na kowane lokaci kuma ƙarar ƙararrawa ta karu a fadin hanyar sadarwa, kudaden gas suna bin wannan haɓakar haɓaka. Yawancin lokaci, kuɗin gas ya fi girma akan masu tarawa idan aka kwatanta da amfani da ƙa'idar mutum ɗaya. Duk da haka, wasu masu tarawa sun sami mafita ga wannan matsala ta hanyar iskar gas ko iskar gas da aka haɓaka a cikin dandamali waɗanda ke barin masu amfani su adana kuɗi akan kuɗin gas. Yana da mahimmanci a lura cewa yayin da kuɗin gas na iya zama mafi girma a kan mai tarawa, suna aiki a matsayin nau'in "kudin dacewa" tun da ingantawa da ingantaccen aiki wanda ya zo tare da mai tarawa zai iya fin kuɗin gas.  

Duk da yake DeFi tabbas ya taimaka kawo miliyoyin sababbin masu amfani zuwa kasuwar cryptocurrency, har yanzu akwai masu amfani waɗanda ke tsoratar da adadin ƙa'idodin da za a zaɓa daga da takamaiman lingo na masana'antu. Sakamakon haka, yawancin masu sha'awar crypto sun gwammace kawai su riƙe cryptocurrencies kamar Bitcoin (BTC) a cikin walat ba tare da sanya shi don amfani mai kyau ba. Tare da zuwan DeFi aggregators, sabon shigarwar zuwa masana'antu na iya amfana daga DeFi ba tare da fahimtar rikitattun fasaha na ciniki, coding, blockchain, da dai sauransu. Mai tarawa yana ba da iko ga waɗannan sababbin masu amfani kuma yana taimaka musu su yanke shawarar kasuwanci mafi kyau.

A cikin tattalin arziƙin da ba a san shi ba irin wannan, har yanzu yana da mahimmanci a daidaita wasu fannoni na DeFi don dacewa da inganci. DeFi aggregators suna tattaro mafi kyawun duniyoyin biyu na dabarun ƙungiyoyi masu tsattsauran ra'ayi da ka'idojin kuɗi don ƙirƙirar kayan aiki mai mahimmanci a cikin wannan sabuwar masana'anta mai ban sha'awa. 

Amfanin DeFi Aggregator 

Mai tarawa yana jan mafi kyawun farashi daga ko'ina cikin shimfidar DeFi - gami da DEXs, sabis na ba da lamuni da wuraren waha ruwa - zuwa wuri guda don masu amfani su inganta kasuwancin su. Ba tare da amfani da mai tarawa ba, masu amfani dole ne su ziyarci musanya daban-daban daban-daban, kwatanta farashin ciniki akan kowace musayar don samun mafi kyawun ciniki sannan aiwatar da kowace ma'amala da hannu ta amfani da kwangiloli masu wayo. 

Bincika farashi da hannu a cikin musanya don mafi kyawun musanyawa baya bada izinin hadaddun hanyoyin kasuwanci ko hanyoyin kasuwanci. Masu tarawa ba wai kawai suna jawo mafi kyawun farashi ba, amma suna ba da damar masu amfani su kwatanta da hada dabarun ta hanyar jawowa da sauke tubalan don ƙirƙirar mafi kyawun dabarun. 

Mafi kyawun DeFi, mafi daidaiton bayanan da aka yi wa masu amfani; wannan yana haifar da mafi kyawun ƙwarewar farashi ga masu amfani a cikin yanayin muhalli, gami da:

DEX: a lokacin DEX (musayar cryptocurrencies), jimillar bayanin yana taimaka wa mai amfani don samun damar haɗa daidaitattun takwarorinsu yayin ma'amalar ɗan-ɗan-tsara. Kwangiloli na kama-da-wane ko ayyukan ma'amaloli suna sanya shi lafiya ga duk masu amfani. Zai fi kyau idan kun lura cewa mafi kyawun ƙwarewar dandamali na DeFi, mafi kyawun tabbacin aminci ga kowa.

SWAP: masu amfani za su iya musanya cryptocurrencies; yayin ma'amala, zaku iya musanya alamar cryptocurrency ku da wani. Ƙirar bayanan yana da taimako saboda za ku yanke shawara mafi kyau bisa ga gaskiya kamar CRO (ƙaddamar da ƙimar canji) da ke samuwa akan nau'i-nau'i da za ku iya musanya.

Bayar da Lamuni: akan wannan, zaku iya samun mafi kyawun bayani don lamuni masu dacewa da zaɓuɓɓukan aro akan DeFi. Ribar da kuke samu daga ba da rancen kuɗaɗen ku zuwa tafki yana da fa'ida saboda mafi kyawun aikin cryptocurrency, kuna da kwarin gwiwa game da dawowar ku.

Wuraren ruwa: tafkin ruwa na ku zai ƙaru lokacin da kuke amfani da tarawar da ta dace. Za ku sami ingantacciyar daidaituwa yayin amfani da DeFi wanda ke ba da damar yawancin cryptocurrencies. Za ku iya yada tushen cryptocurrency ku ta hanyar da ta dace lokacin da aka ba ku cikakkun bayanai don yanke shawara ta hanyar tarawa.

---

2. Top 5 Aggregator Layer Platform a Defi

Maimakon kasancewa da hannu ta hanyar tafkuna masu yawa, masu amfani da DeFi za su iya amfani da mai tarawa DeFi don samun dama ga kewayon musayar ra'ayi da wuraren kasuwanci a kan dashboard guda ɗaya, wanda ke jan bayanai daga nau'ikan musayar iri-iri da masu yin kasuwa ta atomatik. 

Yanzu, bari mu kalli manyan 5 DeFi aggregators.

2.1. 1inch

1inch yana ɗaya daga cikin manyan masu tarawa DEX waɗanda ke ba da mafi kyawun ƙimar ta hanyar gano hanyoyin musanyawa mafi inganci a duk manyan DEXes. Don haka cire buƙatar masu amfani don neman mafi kyawun farashin musaya da ƙananan kuɗin mu'amala a tsakanin musayar.

Ribobi

• 1 inch ya sami mafi kyawun ƙimar
• Babu kuɗin inch 1
• Babu kudin cirewa ko ajiya
• Yana aiki tare da walat daban-daban
• Kuna iya saita umarni iyaka
• Yana aiki tare da walat daban-daban
• Babban kewayon cryptocurrencies

Fursunoni

• Ba a tsara shi ba a Amurka
• Kudin gas na iya zama m
• Bai dace da sababbin masu zuba jari ba
• Zaɓuɓɓukan fiat masu iyaka

Ziyarci: https://app.1inch.io/#/1/swap/ETH/DAI

---

2.2. Dydx

Dydx shi ne na musamman na DeFi aggregator dandali wanda ke bawa yan kasuwa damar yin ayyukan ciniki kamar lamuni / lamuni. Tare da fasalin ciniki na asali, akwai hanyoyi da yawa don ƙyale 'yan kasuwa su sami kudin shiga mai sauri da sauri. 

Ribobi

• Babu kuɗin gas lokacin ciniki na dindindin ko musanya kadarori masu goyan baya
• Gabatarwar alamar DYDX
• Doguwa da gajere tare da babban aiki
• Sami riba akan kadarorin da aka ajiya da kuma gasa farashin lamuni

Fursunoni

• Zaɓin iyaka don nau'i-nau'i na ciniki na gefe (uku)
• Kadarori 3 kawai akwai don musanya
• Matsakaicin riba na Ethereum wani lokaci yana iya kaiwa 0%, wanda hakan ya sa ya zama mara amfani

Ziyarci: https://dydx.exchange/

---

23. Instadapp

Instadapp yana ɗaya daga cikin sanannun dandali mai tarawa Defi waɗanda ke haɗa dukkan manyan ka'idojin DeFi zuwa cikin mahallin mai amfani guda ɗaya wanda ke ba masu amfani damar sarrafa komai ba tare da canzawa tsakanin gidajen yanar gizon yarjejeniya ba. Don haka buɗe sabuwar ƙofa ga masu amfani don yin amfani da cikakkiyar damar raba kuɗin kuɗi.

Instadapp shine tsarin rashin amana na 100% da tsarin da ba na tsarewa ba wanda ke ba da damar amfani don waƙa da motsa kadarorin su na crypto da aka rarraba akan ka'idoji daban-daban a cikin ainihin lokaci ta hanyar dashboard guda. Don ba da damar wannan, Insadapp ya haɗa nau'ikan ka'idoji na DeFi a kan bayansu kuma yana ba da sauƙi na gaba-gaba don masu amfani don samun ƙwarewar DeFi maras kyau ga ƙwararru da sabbin abubuwa iri ɗaya.

Ziyarci: https://instadapp.io/

---

2.4. Zerion

Zerion yana bawa yan kasuwa damar gano yuwuwar kowane kadari akan kasuwa da kasuwanci a mafi kyawun farashi daga dashboard guda.

Ka'idar tana bin ka'idoji sama da 50, yana mai sauƙaƙa nemo alamomin da ba su da yawa.

 Hakanan yana samar da ruwa daga manyan musayar ra'ayi, kuma wannan yana ba masu amfani damar yin ciniki guda ɗaya zuwa wuraren tafkunan ruwa da ma dabarun sarrafa kansu. Wannan yana nufin cewa za su iya musayar kadarori, da aika su zuwa wani walat a cikin ma'amala guda ɗaya.

Ribobi

• Hanyar da ba ta tsarewa ba
• 60+ DeFi ladabi suna goyan bayan
• Tsarin rajista mai sauri
• Yana goyan bayan wallet shida
• 13 fiat kudaden tallafi
• Akwai taɗi kai tsaye

Fursunoni

• Musanya mara tsari
• Complex don sabon shiga

Ziyarci: https://zerion.io/

---

2.5. Plasma.Finance

Tare da Plasma.Finance, zaku iya sarrafa fayil ɗinku, Fiat on/off ramp, wuraren ruwa, DEX da SWAP aggregator, rance da rance gami da musanya sarkar kadara daga maɓalli ɗaya. 

Yana ɗaya daga cikin mafi sauƙi hanyoyin siye da siyar da alamu saboda yana ba da damar katin kiredit ko haɗin banki. Ana yin wannan ta hanyar haɗin gwiwa tare da plasmapay, ramp, da simplex.

Ziyarci: https://apy.plasma.finance/#/market

A ƙarshe, yana da mahimmanci a tuna cewa sararin DeFi har yanzu sabo ne kuma bai girma ba. Wannan yana nufin cewa har yanzu akwai rashin tabbas da yawa da ke tattare da dorewar dogon lokaci na ayyukan DeFi da yawa. Don haka, saka hannun jari ta hanyar tarawar DeFi bazai dace da kowa ba.

Ina fatan wannan sakon zai taimake ku. Kar ku manta kuyi like, comment da sharing zuwa wasu. Na gode!

Kara karantawa: Manyan Shafukan Labarai na Cryptocurrency guda 50 da kuke buƙatar sani

What is GEEK

Buddha Community

Oracles in DeFi Systems: Off-Chain Aggregation vs Centralized Solutions

DeFi projects are changing the way we’re interacting with digital funds. We’re taking real money and transforming them into digital assets that can be used in blockchain-powered applications. Anyway, as much as we want to think that the cryptocurrency world is one that is separated from the actual real-world, it is not. Otherwise, why are you checking the USD price of your tokens?

We are changing the way we are interacting with each other financially, but we are not changing the way we are interacting with the world. Real-world events are influencing our lives and our digital funds. However, blockchain seems to have its own peace. Yes, the price of a token is going up or down. But one ETH will always be one ETH on its blockchain. A block on the blockchain doesn’t know the time. It’s just a block with a number. But blockchain blocks are generated faster or slower based on the external world miners activity.

#defi #cryptocurrency #crypto #oracles-in-defi #off-chain-aggregating-defi #community-curated-oracle-defi #blockchain-oracles #bridge-defi-provable-defi

Avail Defi wallet development services to ensure efficient fund management

DeFi wallet development services are used for storing the crypto coins and tokens of the users safely. There is no third party involved in the platform. The users need not disclose their personal identity or submit any personal information to register themselves on the wallet. It is non-custodial, easily compatible, utilizes fully encrypted private keys, easy to access, and is completely decentralized. Top-notch security measures are taken to safeguard the users’ funds and data. The different types of DeFi wallets are single-currency, multi-currency, business wallets, web, mobile, hardware, and desktop wallets.

**The typical features of a DeFi wallet are **

Safety measures such as two-factor authentication, biometric authentication, DDoS mitigation, anti-phishing software, SSL implementation, HSM implementation, browser detection security, and multi-signature wallets.
An inbuilt QR code scanner for quick execution of payments.
Whitelisting and blacklisting of wallet addresses.
Merchant integration services.
Seamless integration with numerous payment gateways.
Can be used for the transfer of funds, peer-to-peer payments, preparing invoices, and bill payments.
Is compatible across web, mobile, and desktop.
Protection from inflation, economic downturn, and a market crash,
Auto-denial of duplicate payments helps to prevent chargeback fraud.

Make full use of professional DeFi wallet development services and improve your financial position in no time.

#defi wallet development services, #defi wallet development company, #defi wallet developers, #defi wallet development, #defi wallet development solution, #build your defi wallet,

Substrate Knowledge Map For Hackathon Participants

Substrate Knowledge Map for Hackathon Participants

The Substrate Knowledge Map provides information that you—as a Substrate hackathon participant—need to know to develop a non-trivial application for your hackathon submission.

The map covers 6 main sections:

1. Introduction
2. Basics
3. Preliminaries
4. Runtime Development
5. Polkadot JS API
6. Smart Contracts

Each section contains basic information on each topic, with links to additional documentation for you to dig deeper. Within each section, you'll find a mix of quizzes and labs to test your knowledge as your progress through the map. The goal of the labs and quizzes is to help you consolidate what you've learned and put it to practice with some hands-on activities.

Introduction

One question we often get is why learn the Substrate framework when we can write smart contracts to build decentralized applications?

The short answer is that using the Substrate framework and writing smart contracts are two different approaches.

Smart contract development

Traditional smart contract platforms allow users to publish additional logic on top of some core blockchain logic. Since smart contract logic can be published by anyone, including malicious actors and inexperienced developers, there are a number of intentional safeguards and restrictions built around these public smart contract platforms. For example:

Fees: Smart contract developers must ensure that contract users are charged for the computation and storage they impose on the computers running their contract. With fees, block creators are protected from abuse of the network.

Sandboxed: A contract is not able to modify core blockchain storage or storage items of other contracts directly. Its power is limited to only modifying its own state, and the ability to make outside calls to other contracts or runtime functions.

Reversion: Contracts can be prone to undesirable situations that lead to logical errors when wanting to revert or upgrade them. Developers need to learn additional patterns such as splitting their contract's logic and data to ensure seamless upgrades.

These safeguards and restrictions make running smart contracts slower and more costly. However, it's important to consider the different developer audiences for contract development versus Substrate runtime development.

Building decentralized applications with smart contracts allows your community to extend and develop on top of your runtime logic without worrying about proposals, runtime upgrades, and so on. You can also use smart contracts as a testing ground for future runtime changes, but done in an isolated way that protects your network from any errors the changes might introduce.

In summary, smart contract development:

• Is inherently safer to the network.
• Provides economic incentives and transaction fee mechanisms that can't be directly controlled by the smart contract author.
• Provides computational overhead to support graceful logical failures.
• Has a low barrier to entry for developers and enables a faster pace of community interaction.

Substrate runtime development

Unlike traditional smart contract development, Substrate runtime development offers none of the network protections or safeguards. Instead, as a runtime developer, you have total control over how the blockchain behaves. However, this level of control also means that there is a higher barrier to entry.

Substrate is a framework for building blockchains, which almost makes comparing it to smart contract development like comparing apples and oranges. With the Substrate framework, developers can build smart contracts but that is only a fraction of using Substrate to its full potential.

With Substrate, you have full control over the underlying logic that your network's nodes will run. You also have full access for modifying and controlling each and every storage item across your runtime modules. As you progress through this map, you'll discover concepts and techniques that will help you to unlock the potential of the Substrate framework, giving you the freedom to build the blockchain that best suits the needs of your application.

You'll also discover how you can upgrade the Substrate runtime with a single transaction instead of having to organize a community hard-fork. Upgradeability is one of the primary design features of the Substrate framework.

In summary, runtime development:

• Provides low level access to your entire blockchain.
• Removes the overhead of built-in safety for performance.
• Has a higher barrier of entry for developers.
• Provides flexibility to customize full-stack application logic.

To learn more about using smart contracts within Substrate, refer to the Smart Contract - Overview page as well as the Polkadot Builders Guide.

Navigating the documentation

If you need any community support, please join the following channels based on the area where you need help:

• Substrate Technical channel on Discord or Element.
• ink! Smart Contract channel on Discord or Element
• Frontier EVM Compatibility channel on Discord or Element
• PolkatodJS API channel on Discord

Alternatively, also look for support on Stackoverflow where questions are tagged with "substrate" or on the Parity Subport repo.

Use the following links to explore the sites and resources available on each:

Substrate Developer Hub has the most comprehensive all-round coverage about Substrate, from a "big picture" explanation of architecture to specific technical concepts. The site also provides tutorials to guide you as your learn the Substrate framework and the API reference documentation. You should check this site first if you want to look up information about Substrate runtime development. The site consists of:

Knowledge Base: Explaining the foundational concepts of building blockchain runtimes using Substrate.

Tutorials: Hand-on tutorials for developers to follow. The first SIX tutorials show the fundamentals in Substrate and are recommended for every Substrate learner to go through.

How-to Guides: These resources are like the O'Reilly cookbook series written in a task-oriented way for readers to get the job done. Some examples of the topics overed include:

• Setting up proper weight functions for extrinsic calls.
• Using off-chain workers to fetch HTTP requests.
• Writing tests for your pallets It can also be read from

API docs: Substrate API reference documentation.

Substrate Node Template provides a light weight, minimal Substrate blockchain node that you can set up as a local development environment.

Substrate Front-end template provides a front-end interface built with React using Polkadot-JS API to connect to any Substrate node. Developers are encouraged to start new Substrate projects based on these templates.

If you face any technical difficulties and need support, feel free to join the Substrate Technical matrix channel and ask your questions there.

Additional resources

Polkadot Wiki documents the specific behavior and mechanisms of the Polkadot network. The Polkadot network allows multiple blockchains to connect and pass messages to each other. On the wiki, you can learn about how Polkadot—built using Substrate—is customized to support inter-blockchain message passing.

Polkadot JS API doc: documents how to use the Polkadot-JS API. This JavaScript-based API allows developers to build custom front-ends for their blockchains and applications. Polkadot JS API provides a way to connect to Substrate-based blockchains to query runtime metadata and send transactions.

Quiz #1

👉 Submit your answers to Quiz #1

Basics

Set up your local development environment

Here you will set up your local machine to install the Rust compiler—ensuring that you have both stable and nightly versions installed. Both stable and nightly versions are required because currently a Substrate runtime is compiled to a native binary using the stable Rust compiler, then compiled to a WebAssembly (WASM) binary, which only the nightly Rust compiler can do.

Also refer to:

• Set up Substrate for Unix-based machines
• Set up Substrate for Windows

Lab #1

👉 Complete Lab #1: Run a Substrate node

Interact with a Substrate network using Polkadot-JS apps

Polkadot JS Apps is the canonical front-end to interact with any Substrate-based chain.

You can configure whichever endpoint you want it to connected to, even to your localhost running node. Refer to the following two diagrams.

1. Click on the top left side showing your currently connected network:

1. Scroll to the bottom of the menu, open DEVELOPMENT, and choose either Local Node or Custom to specify your own endpoint.

Quiz #2

👉 Complete Quiz #2

Lab #2

👉 Complete Lab #2: Using Polkadot-JS Apps

Notes: If you are connecting Apps to a custom chain (or your locally-running node), you may need to specify your chain's custom data types in JSON under Settings > Developer.

Polkadot-JS Apps only receives a series of bytes from the blockchain. It is up to the developer to tell it how to decode and interpret these custom data type. To learn more on this, refer to:

• Polkadot JS doc: Type basics
• Polkadot JS doc: Extending types

You will also need to create an account. To do so, follow these steps on account generation. You'll learn that you can also use the Polkadot-JS Browser Plugin (a Metamask-like browser extension to manage your Substrate accounts) and it will automatically be imported into Polkadot-JS Apps.

Notes: When you run a Substrate chain in development mode (with the --dev flag), well-known accounts (Alice, Bob, Charlie, etc.) are always created for you.

Lab #3

👉 Complete Lab #3: Create an Account

Preliminaries

You need to know some Rust programming concepts and have a good understanding on how blockchain technology works in order to make the most of developing with Substrate. The following resources will help you brush up in these areas.

Rust

You will need familiarize yourself with Rust to understand how Substrate is built and how to make the most of its capabilities.

If you are new to Rust, or need a brush up on your Rust knowledge, please refer to The Rust Book. You could still continue learning about Substrate without knowing Rust, but we recommend you come back to this section whenever in doubt about what any of the Rust syntax you're looking at means. Here are the parts of the Rust book we recommend you familiarize yourself with:

• ch 1 - 10: These chapters cover the foundational knowledge of programming in Rust
• ch 13: On iterators and closures
• ch 18 - 19: On advanced traits and advanced types. Learn a bit about macros as well. You will not necessarily be writing your own macros, but you'll be using a lot of Substrate and FRAME's built-in macros to write your blockchain runtime.

How blockchains work

Given that you'll be writing a blockchain runtime, you need to know what a blockchain is, and how it works. The **Web3 Blockchain Fundamental MOOC Youtube video series provides a good basis for understanding key blockchain concepts and how blockchains work.

The lectures we recommend you watch are: lectures 1 - 7 and lecture 10. That's 8 lectures, or about 4 hours of video.

Quiz #3

👉 Complete Quiz #3

Substrate runtime development

High level architecture

To know more about the high level architecture of Substrate, please go through the Knowledge Base articles on Getting Started: Overview and Getting Started: Architecture.

In this document, we assume you will develop a Substrate runtime with FRAME (v2). This is what a Substrate node consists of.

Each node has many components that manage things like the transaction queue, communicating over a P2P network, reaching consensus on the state of the blockchain, and the chain's actual runtime logic (aka the blockchain runtime). Each aspect of the node is interesting in its own right, and the runtime is particularly interesting because it contains the business logic (aka "state transition function") that codifies the chain's functionality. The runtime contains a collection of pallets that are configured to work together.

On the node level, Substrate leverages libp2p for the p2p networking layer and puts the transaction pool, consensus mechanism, and underlying data storage (a key-value database) on the node level. These components all work "under the hood", and in this knowledge map we won't cover them in detail except for mentioning their existence.

Quiz #4

👉 Complete Quiz #4

Runtime development topics

In our Developer Hub, we have a thorough coverage on various subjects you need to know to develop with Substrate. So here we just list out the key topics and reference back to Developer Hub. Please go through the following key concepts and the directed resources to know the fundamentals of runtime development.

Key Concept: Runtime, this is where the blockchain state transition function (the blockchain application-specific logic) is defined. It is about composing multiple pallets (can be understood as Rust modules) together in the runtime and hooking them up together.

Runtime Development: Execution, this article describes how a block is produced, and how transactions are selected and executed to reach the next "stage" in the blockchain.

Runtime Develpment: Pallets, this article describes what the basic structure of a Substrate pallet is consists of.

Runtime Development: FRAME, this article gives a high level overview of the system pallets Substrate already implements to help you quickly develop as a runtime engineer. Have a quick skim so you have a basic idea of the different pallets Substrate is made of.

Lab #4

👉 Complete Lab #4: Adding a Pallet into a Runtime

Runtime Development: Storage, this article describes how data is stored on-chain and how you could access them.

Runtime Development: Events & Errors, this page describe how external parties know what has happened in the blockchain, via the emitted events and errors when executing transactions.

Notes: All of the above concepts we leverage on the #[pallet::*] macro to define them in the code. If you are interested to learn more about what other types of pallet macros exist go to the FRAME macro API documentation and this doc on some frequently used Substrate macros.

Lab #5

👉 Complete Lab #5: Building a Proof-of-Existence dApp

• Writing Tests for Your Pallet: learn to build up a mock runtime and write test cases for your pallet logics.

Lab #6

👉 Complete Lab #6: Building a Substrate Kitties dApp

Quiz #5

👉 Complete Quiz #5

Polkadot JS API

Polkadot JS API is the javascript API for Substrate. By using it you can build a javascript front end or utility and interact with any Substrate-based blockchain.

The Substrate Front-end Template is an example of using Polkadot JS API in a React front-end.

• Runtime Development: Metadata, this article describes the API allowing external parties to query what API is open for the chain. Polkadot JS API makes use of a chain's metadata to know what queries and functions are available from a chain to call.

Lab #7

👉 Complete Lab #7: Using Polkadot-JS API

Quiz #6

👉 Complete Quiz #6: Using Polkadot-JS API

Smart contracts

Learn about the difference between smart contract development vs Substrate runtime development, and when to use each here.

In Substrate, you can program smart contracts using ink!.

• Learn about smart contract development in Substrate
• Learn about Smart contract development using ink!

Quiz #7

👉 Complete Quiz #7: Using ink!

What we do not cover

A lot 😄

On-chain runtime upgrades. We have a tutorial on On-chain (forkless) Runtime Upgrade. This tutorial introduces how to perform and schedule a runtime upgrade as an on-chain transaction.

About transaction weight and fee, and benchmarking your runtime to determine the proper transaction cost.

Off-chain Features

There are certain limits to on-chain logic. For instance, computation cannot be too intensive that it affects the block output time, and computation must be deterministic. This means that computation that relies on external data fetching cannot be done on-chain. In Substrate, developers can run these types of computation off-chain and have the result sent back on-chain via extrinsics.

Tightly- and Loosely-coupled pallets, calling one pallet's functions from another pallet via trait specification.

Blockchain Consensus Mechansim, and a guide on customizing it to proof-of-work here.

Parachains: one key feature of Substrate is the capability of becoming a parachain for relay chains like Polkadot. You can develop your own application-specific logic in your chain and rely on the validator community of the relay chain to secure your network, instead of building another validator community yourself. Learn more with the following resources:

• Cross-chain Message Passing (XCMP), how parachain and relay-chain communicate to each others
• Workshop: Using cumulus to build your parachain

Terms clarification

• Substrate: the blockchain development framework built for writing highly customized, domain-specific blockchains.
• Polkadot: Polkadot is the relay chain blockchain, built with Substrate.
• Kusama: Kusama is Polkadot's canary network, used to launch features before these features are launched on Polkadot. You could view it as a beta-network with real economic value where the state of the blockchain is never reset.
• Web 3.0: is the decentralized internet ecosystem that, instead of apps being centrally stored in a few servers and managed by a sovereign party, it is an open, trustless, and permissionless network when apps are not controlled by a centralized entity.
• Web3 Foundation: A foundation setup to support the development of decentralized web software protocols. Learn more about what they do on thier website.

Others

• Answers to quizzes and labs

---

Author: substrate-developer-hub
Source Code: https://github.com/substrate-developer-hub/hackathon-knowledge-map
License: 

#blockchain #substrate 

Magento Ecommerce SEO Best Practices

Running a business online? Well, I have come across many of you who bend back and forth trying to up their game by hiring a relevant Magento development company and further following the best SEO practices. Fortunately, we are living in an era where you can find a plethora of methods or ways to enhance their SEO procedures. The following post acts as a perfect guide that can assist you in enhancing your SEO tactics/strategies and help you to up your game.

Why is there a need for SEO for eCommerce? 1
How is SEO beneficial for your eCommerce Store? 2
#1 Generate Sustainable Traffic 2
#2 Drives Brand Awareness 3
#3 Amazing Customer Experience 3
#4 Free 3
#5 Capturing the Long Tail Keywords 4

Magento Ecommerce SEO Best Practices 4
#1 Duplicate Content 6
#2 Keeping your store Up-to-Date 7
#3 Enhance the Website Speed 7
#4 Check the Magento SEO URLs 8
#5 Optimize Product Images 9
Final Thoughts 9

Why is there a need for SEO for eCommerce?

Do you think that SEO is a mere method of producing a high amount of traffic? Well, to be precise SEO is way more than you think. Striving hard to compete in today’s insanely tricky and competitive world is a bit kind of a challenge, especially after the COVID pandemic. So what exactly is SEO? Well, it is short-term known for Search Engine Optimization. The process of increasing traffic visiting a website by gaining a higher position in comparison to the previous one. Originally, SEO was supposed to attract as many visitors as possible.

Now, whenever you try surfing the internet to look for specific information, I am sure you must come across several options, some of which are the best while others are not in the Search Engine Result Pages (SERPs). In other words, the high position of the website means more possibility of visitors visiting and becoming your regular customers. Further, I would like to mention the pros of considering SEO for your eCommerce store.

We are residing in an era where there’s a race for increasing visitors, traffic and revenue and an organic search can be pretty much of help here.

How is SEO beneficial for your eCommerce Store?

Even today, Search Engine Optimization is overlooked as a highly crucial aspect of eCommerce business marketing strategy. However, here below I would like to mention several benefits offered by SEO. Read Away!

#1 Generate Sustainable Traffic

One of the obvious benefits of considering SEO is generating a sustainable amount of traffic. There are several methods available such as paid social media, and search engine ads that can certainly assist in driving tons and tons of visitors in an extremely short span of time. You see, maintaining such an impressive amount of traffic is tricky and all the paid methods are pretty expensive. I mean here you have to keep paying the ad provider again and again. And over time, you might have to pay more to drive volume with the increase in competition.

In fact, hereby incorporating the best SEO strategies, you will be able to create a more sustainable level of traffic. You see, most SEO investments tend to happen right at the beginning of the process and can certainly offer long-lasting results. At the same time, it is extremely important to keep the content well up to date and the website keeps on running smoothly. Learn more regaring content marketing.

#2 Drives Brand Awareness

In today’s scenario, making people well-aware of your brand is very important and SEO offers a great amount of help in doing so. In fact, it turns out to be the sure-shot way for low-cost brand awareness. I mean if your website gets to appear on the very first page of Google, there is a 100% chance for people looking for a particular product ending up stumbling on your website and even buying the product.

Such kinds of rankings can also turn out to be endorsements which do visitors click on and keep the brand in mind while making the final decision. Without a doubt, top ranking is one of the most powerful positions to be in and unlike your competitors you aren’t falling short here.

#3 Amazing Customer Experience

When you end up ranking on the top of the SERPs, it becomes pretty easy for customers to visit your store. Also, this without a doubt increases the buying chances. In fact, according to several stats, almost all the users don’t even bother looking at the websites that are listed on the second page of Google. So ranking on the first page of Google turns out to be a must.

Now tell me something: do you remember URLs? Of course, not! What we generally do is we simply google things and then view websites or stores ranking on the first page of the search result. Not to mention if the website is already ranked on the first page it means that it is the best in terms of navigation, content quality, high-quality images, and whatnot! As a result, an amazing customer experience can be expected here.

#4 Free
The next advantage of considering SEO for your eCommerce store is that it is available for free. Unlike PPC ads or social ads or search engine ads, you don’t have to pay whether it might work wonders for you or not. All you have to do is follow some of the best SEO practices that earn you a great source of traffic without the requirement of paying any kind of upfront costs. Though you may not spend extravagantly on SEO, you can hire a team of SEO experts at a reasonable price who carry an immense amount of experience ranking eCommerce stores by boosting search engine rankings.

#5 Capturing the Long Tail Keywords

Another crucial advantage of considering SEO for your eCommerce store is that it captures the long-tail keyword. You see 15% of search engine queries are new and unique and a long tail keyword strategy is the implication of these queries within the content and presents it seamlessly that it successfully covers at a higher rate.

Although, eCommerce sites are typically well-structured in such a way that they do end up targeting those long-term searches. For example, first, you look for clothing rather than women’s clothing, then dresses, jumpsuits, pants, jeans, tops, t-shirts, shirts and whatnot! Similarly, an eCommerce store follows the same path, so if you have the keyword “women dresses” Jeans for Women” then the end user can directly land up on your site. Here all you have to do is opt for a robust and scalable SEO strategy.

I can simply go on and on when it comes to the benefits of eCommerce SEO such as building trust, increasing sales, expanding remarketing audiences, increasing site usability, fast loading speed, etc. eCommerce SEO is a growing trend and not making the most of it means you might have a lot to lose. Further, I would like to mention some of the best Magento eCommerce SEO practices to take into account.

Magento Ecommerce SEO Best Practices

When we use the word eCommerce, Magento is something that automatically comes to your mind. Why so? Because Magento and eCommerce are like chocolate and peanut butter, they can make incredible taste when merged. In fact, there are a plethora of reasons such as power, security and customizability why Magento is a go-to platform for retailers planning to strengthen their online presence. Now I am sure you must have come across the term Magento SEO. Well, it is a set of SEO adjustments that are unique and never heard of before. In fact, Magento turns out to be more like a blessing in disguise for SEO as it incorporates some of the most amazing features such as robots.txt file, sitemap.xml, etc.

To come up with a strong technical foundation you need:
● Great URL Structure
● Meta information
● Headings
● Faceted Navigation
● Crawling and Indexing
● Site Speed
● HTTPS

In order to rank your Magento store well, especially through the organic search results, there are certain aspects you must take into consideration. Yes, I am talking about the three pillars:

1. Technology – A strong technical foundation of the website can certainly assist search engines in finding and understanding your site as soon and as effectively as possible.
2. Relevance – Is your content relevant to the search query? For that, you have to make sure that you end up creating content that’s useful and satisfying for the end users.
3. Authority – Try to build trust by adding as many links as you can to your website.

It may quite interest you to know that doing SEO for a typical website is far easier than doing that of an eCommerce store featuring hundreds and thousands of page listings or product listings. Fret not, here down below I would like to mention some of the most intimidating SEO tips that must be taken into account for the betterment of your eCommerce store.

#1 Duplicate Content

What exactly is duplicate content? Now I am sure you must have seen similar content over the internet. I mean two websites having the same heading, title, paras, images basically everything seems to be extremely identical. Can you spot which one is original and which one is copied? Now what happens is when multiple versions are similar to each other, it becomes way difficult for search engines to distinguish between the two. And that’s the reason why search engines rarely tend to display the duplicate pages in the search engine rankings. You must be wondering whether the duplication can harm SEO. Well, of course, it does and in many ways!

One of the obvious ways is that duplicate content can result in high penalties leading to harming your page rankings and organic traffic. You see search engines in such cases tend to determine which version is more relatable to the query of the audience and then give a specific rank. Though there is no denying the fact that duplicate content can severely dilute link equity and credibility.

I have come across many of you who have this question, can this be visible to the naked eyes? Well, not really because duplication is hidden in the code of the site so you need software to check things precisely. Best practices to combat duplicate content are:

● 301 redirect
● Make use of Meta Robot Tags
● Make relevant changes in Meta Title Tags
● Use Canonical tag
● Eliminate pages

Mainly duplicate content issues occur in pages such as product filtering, product sorting, pagination, the same product in different categories, variation of a similar product and so forth.

#2 Keeping your store Up-to-Date

Another crucial tip to take into account is keeping your Magento store up to date. Now since you have already developed an intimidating Magento store but not keeping it up-to-date means you won’t get desired results and keep your customers hooked for a long period of time. Of course, Magento development is very crucial but what’s more crucial is to maintain the website. Here’s how!

● Analyze website performance – You have to keep examining the overall performance of the website day in and day out. Fortunately, there are a wide range of magento tools available that may assist you well in analyzing the website. So that you can beware of negative clicks, visits, bounce rate, search queries and whatnot!

● Website speed – With an increasingly short attention span of users, website owners these days must keep severe track of the speed of the website. If the website doesn’t load within three seconds then your customers are more likely to shift to your competitors.

● Regular updates – Fresh and relevant information are favored by all and your end users are certainly not an exception here. So try rewriting your website at regular intervals to keep your users stay relevant and on top of Google.

Here you do have a choice. You can either update things manually through a system upgrade or else seek assistance from a relevant Magento development company which offers seamless maintenance.

#3 Enhance the Website Speed

The next step that needs to be taken into consideration is enhancing the website speed. The slow loading speed can be quite discouraging and tiresome. Now, first of all, let us understand why this happens in the first place. One of the obvious reasons for slow loading speed include not meeting the system requirements, making use of inappropriate extensions, MySQL, NGINX, and PHP configurations not optimized, disabling caching, use of slow hardware and whatnot!

Further, I would like to mention a few ways through which you can speed up your Magento store.

● Update regularly – When a different version is released then you need to know that it is astronomical. And the same goes for every other technology available. You see developers in the Magento community tend to strive extremely hard to make the latest version secure, robust and scalable to a great extent. So don’t miss out on the big update, you never know it can be way more useful.
● Optimize your database – Databases tend to store data in one location. Now what happens when the data is poorly optimized, it takes way longer to server requests. As a result, this surely reflects in performance.
● Enable Magento Cache Management – Now let’s take a situation where you are sending an invite to around 1000 people. Now when you do it manually, it takes a hell lot of time and effort. How about sending bulk emails too?
○ Create a copy of your site in the local cache
○ Magento returns the copy instead of recreating a new site

Also, make this a regular habit of the site audit. Right from adding the relevant amount of pages to getting notified if the website speed gets slow make use of the website audit tool to identify relevant issues such as broken links, SSL errors, lack of mobile optimization and whatnot!

#4 Check the Magento SEO URLs

Another interesting tip to take into account is keeping tabs on Magento SEO URLs and seeing whether they are SEO-friendly or not. One of the most amazing features offered by Magento was that it enabled the end users to edit their product URLs freely. Yes, in other words, it is extremely easy to make relevant changes to all the links, especially the ones which are in regard to the product categories, and CMS pages. In other words, you no longer have to worry about 440 errors or missing content here.

Some of the best and most common examples to consider:
● website.com/category/
● website.com/category/sub-category/
● website.com/category-sub-category/product-name/

#5 Optimize Product Images

Another crucial step to take into account is to optimize product images. By doing so you can conduct better search rankings. Now you must be wondering what image optimization is. Well, it is all about reducing the file size of your image and all this happens without sacrificing quality. Here’s how you can do so!

● Name image descriptively – You will be listing hundreds and thousands of products so don’t keep the default names given by the camera. Try to incorporate relevant keywords so that when the crawler goes through your file names, it finds them relevant. Take a deep look at the website analytics and relevant keyword patterns and then make crucial decisions here.

● Choosing image dimensions – Now since you are creating an eCommerce store, of course, you have to show the product from different angles. For example, the back, the front, the interiors, engines and whatnot! In addition, do not forget to add a relevant description so that potential users end up landing on your website.

● Reduce the file size – As mentioned earlier, the attention span is pretty much less and your eCommerce store not loading in a span of 3 seconds means you are losing out on your potential customers. It may also interest you to know that Google uses page load time as one of the crucial ranking factors.

And that’s all for now!

Final Thoughts

Though SEO is one of the most conventional and traditional approaches, there are numerous new and quick options such as paid ads, social media ads, and emails, that can offer immediate returns. However, on the contrary, investing or hiring a reliable SEO agency might not provide immediate returns but it certainly can be a slow yet sustainable path to achieve growth in the long run. Take certain aspects such as keyword selection, content creation, and tech SEO in mind and do try investing in opportunities that are within your reach.

It doesn’t matter whether you are a techie or a non-techie, but you have to be realistic knowing that SEO strategy won’t be an overnight success – it may take weeks, months and even a year but have faith that one day your eCommerce store will be found on the top search rankings. Stay motivated, and keep going because that’s the only way we move forward.

I hope you did find the following post meaningful. If so feel free to share this among your peers and do help us in spreading the word.

Original Source: [HERE]

Hangfire en ASP.NET Core 3.1

En este artículo, aprendamos sobre Hangfire en ASP.NET Core 3.1 y cómo integrarlo con sus aplicaciones principales. Una tarea de programación común a la que nos enfrentamos regularmente es ejecutar trabajos en segundo plano. Y ejecutar estos trabajos correctamente sin estropear su código no es una tarea fácil, pero tampoco es difícil. Solía ​​trabajar con los servicios de Windows para programar varias tareas dentro de mi aplicación C#. Luego, me encontré con esta biblioteca casi increíble: Hangfire, y nunca me fui.

Trabajos en segundo plano en ASP.NET Core

Básicamente, los trabajos en segundo plano son aquellos métodos o funciones que pueden tardar mucho tiempo en ejecutarse (cantidad de tiempo desconocida). Estos trabajos, si se ejecutan en el subproceso principal de nuestra aplicación, pueden o no bloquear la interacción del usuario y puede parecer que nuestra aplicación .NET Core se ha bloqueado y no responde. Esto es bastante crítico para las aplicaciones orientadas al cliente. Por lo tanto, tenemos trabajos en segundo plano, similares a los subprocesos múltiples, estos trabajos se ejecutan en otro subproceso, lo que hace que nuestra aplicación parezca bastante asíncrona.

También deberíamos tener la posibilidad de programarlos en un futuro cercano para que esté completamente automatizado. La vida de un desarrollador sería muy dura sin estas increíbles posibilidades.

¿Qué es Hangfire?

Hangfire es una biblioteca de código abierto que permite a los desarrolladores programar eventos en segundo plano con la mayor facilidad. Es una biblioteca altamente flexible que ofrece varias funciones necesarias para hacer que la tarea de programación de trabajos sea pan comido. Hangfire en ASP.NET Core es la única biblioteca que no puede perderse.

Integración de Hangfire en ASP.NET Core 3.1

Para este tutorial, tengamos un escenario específico para que podamos explicar Hangfire y su potencial completo. Digamos que estamos desarrollando una API que se encarga de enviar correos al Usuario para diferentes escenarios. Tiene más sentido explicar Hangfire de esta manera. Hangfire es una de las bibliotecas más fáciles de adaptar, pero también muy poderosa. Es uno de los paquetes que ayuda por completo a crear aplicaciones de forma asíncrona y desacoplada.

Como mencioné anteriormente, Hangfire usa una base de datos para almacenar los datos del trabajo. Usaremos la base de datos del servidor MSSQL en esta demostración. Hangfire crea automáticamente las tablas requeridas durante la primera ejecución.

Configuración del proyecto ASP.NET Core

Comenzaremos creando un nuevo proyecto ASP.NET Core con la plantilla API seleccionada. Ahora cree un controlador de API vacío. Llamémoslo HangfireController. Estoy usando Visual Studio 2019 Community como mi IDE y POSTMAN para probar las API.

Instalación de los paquetes Hangfire

Instalando el único paquete que necesitarías para configurar Hangfire.

Install-Package Hangfire

Configuración de Hangfire

Una vez que haya instalado el paquete, ahora estamos listos para configurarlo para que sea compatible con nuestra aplicación ASP.NET Core API. Este es un paso bastante sencillo, además, una vez que instale el paquete, se le mostrará un Léame rápido que le muestra el paso para completar la configuración.

Navigate to Startup.cs / ConfigureServices so that it looks like the below code snippet.
public void ConfigureServices(IServiceCollection services)
{
services.AddHangfire(x => x.UseSqlServerStorage("<connection string>"));
services.AddHangfireServer();
services.AddControllers();
}

Explicación.
Línea #3 Agrega el servicio Hangfire a nuestra aplicación. También hemos mencionado el almacenamiento que se utilizará, el servidor MSSQL, junto con la cadena/nombre de conexión.
La línea n.º 4 en realidad enciende el servidor Hangfire, que es responsable del procesamiento de trabajos.

Una vez hecho esto, vayamos al método Configurar y agregue la siguiente línea.

app.UseHangfireDashboard("/mydashboard");

Explicación.
Lo que hace esta línea es que nos permite acceder al panel de hangfire en nuestra aplicación ASP.NET Core. El tablero estará disponible yendo a /URL de mi tablero. Iniciemos la aplicación.

Esquema de la base de datos Hangfire

Cuando inicia su aplicación ASP.NET Core por el momento, Hangfire verifica si tiene un esquema de Hangfire asociado disponible en su base de datos. Si no, creará un montón de tablas para ti. Así es como se vería su base de datos.

Panel de Hangfire

Después de cargar la aplicación, vaya a <localhost>/mydashboard. Podrá ver el panel de control de Hangfire.

Desde el tablero podrás monitorear los trabajos y sus estados. También le permite activar manualmente los trabajos disponibles. Esta es la característica ÚNICA que diferencia a Hangfire de otros programadores. Tablero incorporado. ¿Cuan genial es eso? La captura de pantalla anterior es la de la descripción general del panel. Exploremos también las otras pestañas.

Pestaña de trabajos.

Todos los trabajos que están disponibles en el almacén de datos (nuestro servidor MSSQL) se enumerarán aquí. Obtendrá una idea completa del estado de cada trabajo (En cola, Exitoso, Procesando, Fallido, etc.) en esta pantalla.

Pestaña Reintentos.

Los trabajos tienden a fallar de vez en cuando debido a factores externos. En nuestro caso, nuestra api intenta enviar un correo al usuario, pero hay un problema de conexión interna, lo que hace que el trabajo no se ejecute. Cuando falla un trabajo, Hangfire continúa intentándolo hasta que pasa. (configurable)

Pestaña de trabajos recurrentes.

¿Qué sucede si necesita enviar por correo el uso de su factura mensualmente? Esta es la característica principal de Hangfire, trabajos recurrentes. Esta pestaña le permite monitorear todos los trabajos configurados.

Pestaña Servidores.

Recuerde, al configurar Hangfire en la clase Startup.cs, lo hemos mencionado. services.AddHangfireServer().. Esta es la pestaña donde muestra todos los Hangfire Server activos. Estos servidores son responsables de procesar los trabajos. Digamos que no ha agregado los servicios. AddHangfireServer() en la clase de inicio, aún podría agregar trabajos Hangfire a la base de datos, pero no se ejecutarán hasta que inicie un servidor Hangfire.

Protección del panel Hangfire

Esta es una característica bastante obvia. Dado que el tablero puede exponer datos muy confidenciales como nombres de métodos, valores de parámetros, ID de correo electrónico, es muy importante que protejamos/restringamos este punto final. Hangfire, listo para usar, hace que el tablero sea seguro al permitir solo solicitudes locales. Sin embargo, puede cambiar esto implementando su propia versión de IDashboardAuthorizationFilter . Si ya implementó la Autorización en su API, puede implementarla para Hangfire. Consulte estos pasos para asegurar el tablero.

Tipos de trabajo en Hangfire

Los trabajos en segundo plano en ASP.NET Core (o digamos cualquier tecnología) pueden ser de muchos tipos según los requisitos. Repasemos los tipos de trabajo disponibles con Hangfire con la implementación adecuada y la explicación en nuestro proyecto ASP.NET Core API. Vamos a codificar.

Despedir y olvidar trabajos

Los trabajos de disparar y olvidar se ejecutan  solo una vez  y casi  inmediatamente  después de la creación. Crearemos nuestro primer trabajo de fondo. Abre el controlador Hangfire que habíamos creado. Crearemos un punto final POST que dé la bienvenida a un usuario con un correo electrónico (idealmente). Añade estos códigos.

[HttpPost]
[Route("welcome")]
public IActionResult Welcome(string userName)
{
var jobId = BackgroundJob.Enqueue(() => SendWelcomeMail(userName));
return Ok($"Job Id {jobId} Completed. Welcome Mail Sent!");
}

public void SendWelcomeMail(string userName)
{
//Logic to Mail the user
Console.WriteLine($"Welcome to our application, {userName}");
}

Explicación.
La línea #5 almacena JobId en una variable. Puede ver que en realidad estamos agregando un trabajo en segundo plano representado por una función ficticia SendWelcomeMail. El JobId se vuelve a publicar más tarde en el Panel de control de Hangfire. Cree la aplicación y ejecútela. Vamos a probarlo con Postman.

Tenga en cuenta la URL y cómo estoy pasando el nombre de usuario al controlador. Una vez que lo ejecute, obtendrá nuestra respuesta requerida. “Id. de trabajo 2 completado. ¡Correo de bienvenida enviado!”. Ahora veamos el tablero de Hangfire.

En la pestaña Correcto, puede ver el recuento de trabajos completados. También puede ver los detalles de cada trabajo, similar a la captura de pantalla anterior. Todos los parámetros y nombres de funciones se exponen aquí. ¿Quiere volver a ejecutar este trabajo con los mismos parámetros? Presiona el botón Volver a poner en cola. Vuelve a agregar su trabajo en la cola para que Hangfire lo procese. Sucede casi de inmediato.

Trabajos retrasados

Ahora, qué pasa si queremos enviar un correo a un usuario, no inmediatamente, sino después de 10 minutos. En tales casos, utilizamos trabajos retrasados. Veamos su implementación, después de lo cual lo explicaré en detalle. En el mismo controlador, agregue estas líneas de código. Es bastante similar a la variante anterior, pero le introducimos un factor de retraso.

[HttpPost]
[Route("delayedWelcome")]
public IActionResult DelayedWelcome(string userName)
{
var jobId = BackgroundJob.Schedule(() => SendDelayedWelcomeMail(userName),TimeSpan.FromMinutes(2));
return Ok($"Job Id {jobId} Completed. Delayed Welcome Mail Sent!");
}

public void SendDelayedWelcomeMail(string userName)
{
//Logic to Mail the user
Console.WriteLine($"Welcome to our application, {userName}");
}

Explicación.
La línea #5 programó el trabajo en un período de tiempo definido, en nuestro caso son 2 minutos. Eso significa que nuestro trabajo se ejecutará 2 minutos después de que Postman haya llamado a la acción. Abramos Postman de nuevo y probemos.

Puede ver que recibimos la respuesta esperada de Postman. Ahora. vuelva rápidamente al Panel de control de Hangfire y haga clic en la pestaña Trabajos/programados. Diría que el trabajo se ejecutará en un minuto. Ahí estás para. Ha creado su primer trabajo programado usando Hangfire con facilidad.

trabajos recurrentes

Nuestro Cliente tiene una suscripción a nuestro servicio. Obviamente, tendríamos que enviarle un recordatorio sobre el pago o la factura en sí. Esto llama la necesidad de un trabajo recurrente, donde puedo enviar correos electrónicos a mis clientes mensualmente. Esto es compatible con Hangfire mediante el programa CRON.
¿Qué es CRON? CRON es una utilidad basada en el tiempo que puede definir intervalos de tiempo. Veamos cómo lograr tal requisito.

[HttpPost]
[Route("invoice")]
public IActionResult Invoice(string userName)
{
RecurringJob.AddOrUpdate(() => SendInvoiceMail(userName), Cron.Monthly);
return Ok($"Recurring Job Scheduled. Invoice will be mailed Monthly for {userName}!");
}

public void SendInvoiceMail(string userName)
{
//Logic to Mail the user
Console.WriteLine($"Here is your invoice, {userName}");
}

La línea #5 establece claramente que estamos tratando de agregar/actualizar un trabajo recurrente, que llama a una función tantas veces como lo define el esquema CRON. Aquí enviaremos la factura al cliente mensualmente el primer día de cada mes. Ejecutemos la aplicación y cambiemos a Postman. Estoy ejecutando este código el 24 de mayo de 2020. Según nuestro requisito, este trabajo debe despedirse el 1 de junio de 2020, que es dentro de 7 días. Vamos a ver.

Entonces, esto funcionó. Pasemos a Hangfire Dashboard y vayamos a la pestaña Trabajos recurrentes.

¡Perfecto! Funciona como excepción. Puede pasar por varios esquemas CRON aquí que pueden coincidir con sus requisitos. Aquí hay una pequeña documentación agradable para comprender cómo se usan varias expresiones CRON.

Continuaciones

Este es un escenario más complicado. Permítanme tratar de mantenerlo muy simple. Un usuario decide darse de baja de su servicio. Después de que confirme su acción (tal vez haciendo clic en el botón para cancelar la suscripción), nosotros (la aplicación) tenemos que cancelar la suscripción del sistema y enviarle un correo de confirmación después de eso también. Entonces, el primer trabajo es realmente cancelar la suscripción del usuario. El segundo trabajo es enviar un correo confirmando la acción. El segundo trabajo debe ejecutarse solo después de que el primer trabajo se haya completado correctamente. Obtener el escenario?

[HttpPost]
[Route("unsubscribe")]
public IActionResult Unsubscribe(string userName)
{
var jobId = BackgroundJob.Enqueue(() => UnsubscribeUser(userName));
BackgroundJob.ContinueJobWith(jobId, () => Console.WriteLine($"Sent Confirmation Mail to {userName}"));
return Ok($"Unsubscribed");
}

public void UnsubscribeUser(string userName)
{
//Logic to Unsubscribe the user
Console.WriteLine($"Unsubscribed {userName}");
}

Explicación.
Línea #5 El primer trabajo que realmente contiene lógica para eliminar la suscripción del usuario.
Línea #6 Nuestro segundo trabajo que continuará después de que se ejecute el primer trabajo. Esto se hace pasando el Id. de trabajo del trabajo principal a los trabajos secundarios.

Iniciemos la aplicación y vayamos a Postman.

Ahora, vaya al Tablero y verifique el trabajo exitoso. Verá 2 nuevos trabajos ejecutados en el orden exacto que queríamos. Eso es todo por este tutorial. Espero que tengan claro estos conceptos y les resulte fácil integrar Hangfire en las aplicaciones ASP.NET Core.

Resumen

En esta guía detallada, hemos repasado los conceptos de trabajos en segundo plano, características e implementación de Hangfire en aplicaciones ASP.NET Core y varios tipos de trabajos en Hangfire. El código fuente utilizado para demostrar este tutorial está publicado en GitHub. Te dejo el enlace a continuación para que lo consultes. ¿Tienes experiencia con Hangfire? ¿Tienes alguna consulta/sugerencia? Siéntase libre de dejar a continuación en la sección de comentarios. ¡Feliz codificación!

Fuente: https://codewithmukesh.com/blog/hangfire-in-aspnet-core-3-1/

#aspdotnet #hangfire