5 Things you didn't know about Azure Cognitive Services

In this edition of Azure Tips and Tricks, you will learn about 5 things you didn’t know about Azure Cognitive Services.

Subscribe : https://www.youtube.com/channel/UC0m-80FnNY2Qb7obvTL_2fA

#azure

What is GEEK

Buddha Community

5 Things you didn't know about Azure Cognitive Services

How To Develop, Build, Deploy Application using .NET 5, CI/CD, Azure App Service, Azure...

Develop, Build, Deploy applications using .NET 5, CI/CD, Azure App Service, Azure SQL Database, Azure Storage Account.

Welcome to my hands-on session on the Complete Development and Deployment of a.NET5 application using Azure services. My name is Sandeep Soni. I am a Microsoft Certified Trainer and an Azure Architect.

Connect with me 👋
Call Sandeep Soni for Career Guidance ► +91 98490 01840
Connect with me on LINKEDIN ► https://www.linkedin.com/in/sandeepsoni123/

👉🏼 Upcoming FREE Tech Webinars: https://www.bestdotnettraining.com/courses-and-webinars
👉🏼 Join our WhatsApp group: https://chat.whatsapp.com/CiFJr9qmid08NesQ86WWvg

#deccansoft #bestdotnettraining #sandeepsoni

▬▬▬▬▬▬ COURSE OVERVIEW 📚 ▬▬▬▬▬▬
🔥 Topics Discussed 🔥
► .NET5
► CI/CD Pipelines
► Azure App Service
► Azure SQL Database
► Azure Storage Account

💻 📡 LIVE Webinars & Courses
► Check our upcoming schedule 👉🏼 https://www.bestdotnettraining.com/courses-and-webinars
► 📲 Join our WhatsApp group to get all updates 👉🏼 https://chat.whatsapp.com/CiFJr9qmid08NesQ86WWvg
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
We want to reach 100K Subscriber, please do subscribe so we reach our goal faster :)
Subscribe for related videos: https://www.youtube.com/user/Deccansoft123

👨🏻‍🏫 This complete tutorial is compiled by Sandeep Soni, a Microsoft Certified Trainer, a Software & Corporate Trainer for 24 years!
For more great tutorials from the creator of this course, check out https://www.bestdotnettraining.com/

📞 Reach us @ +91 8008327000 Kashmira Shah

📱 Connect with us

#azure sql database #azure sql #azure #azure app service #.net 5 #ci/cd

Implement a full text search using Azure Cognitive Search in ASP.NET Core

This article shows how to implement a full text search in ASP.NET Core using Azure Cognitive Search. The search results are returned using paging and the search index can be created, deleted from an ASP.NET Core Razor Page UI.

Code: https://github.com/damienbod/AspNetCoreAzureSearch

Creating the Search in the Azure Portal

In the Azure Portal, search for Azure Cognitive Search and create a new search service. Create the search using the portal wizard and choose the correct pricing model as required. The free version supports three indexes but does not support managed identities. This is good for exploring, evaluating the service.

If using the free version, you will need to use API keys to access the search service. This can be found in the **Keys **blade of the created cognitive search.

Of course the Azure Cognitive Search could also be created using Azure CLI, Arm templates or Powershell. The service can also be created direct from code.

Create an Azure Cognitive Search index

In the ASP.NET Core Razor page application, the Azure.Search.Documents nuget package is used to create and search the Azure Cognitive search service. Add this to your project.

The index and the document field definitions can be created in different ways. We will use attributes and add these to the document search class properties to define the fields of the documents.

#.net core #asp.net core #aspnet5 #azure #azure cognitive search #lucene #azure search #cognitive azure search #full text #lucerne #razor pages

Ron  Cartwright

Ron Cartwright

1600624800

Getting Started With Azure Event Grid Viewer

In the last article, we had a look at how to start with Azure DevOps: Getting Started With Audit Streaming With Event Grid

In the article, we will go to the next step to create a subscription and use webhook event handlers to view those logs in our Azure web application.

#cloud #tutorial #azure #event driven architecture #realtime #signalr #webhook #azure web services #azure event grid #azure #azure event grid #serverless architecture #application integration

Eric  Bukenya

Eric Bukenya

1624713540

Learn NoSQL in Azure: Diving Deeper into Azure Cosmos DB

This article is a part of the series – Learn NoSQL in Azure where we explore Azure Cosmos DB as a part of the non-relational database system used widely for a variety of applications. Azure Cosmos DB is a part of Microsoft’s serverless databases on Azure which is highly scalable and distributed across all locations that run on Azure. It is offered as a platform as a service (PAAS) from Azure and you can develop databases that have a very high throughput and very low latency. Using Azure Cosmos DB, customers can replicate their data across multiple locations across the globe and also across multiple locations within the same region. This makes Cosmos DB a highly available database service with almost 99.999% availability for reads and writes for multi-region modes and almost 99.99% availability for single-region modes.

In this article, we will focus more on how Azure Cosmos DB works behind the scenes and how can you get started with it using the Azure Portal. We will also explore how Cosmos DB is priced and understand the pricing model in detail.

How Azure Cosmos DB works

As already mentioned, Azure Cosmos DB is a multi-modal NoSQL database service that is geographically distributed across multiple Azure locations. This helps customers to deploy the databases across multiple locations around the globe. This is beneficial as it helps to reduce the read latency when the users use the application.

As you can see in the figure above, Azure Cosmos DB is distributed across the globe. Let’s suppose you have a web application that is hosted in India. In that case, the NoSQL database in India will be considered as the master database for writes and all the other databases can be considered as a read replicas. Whenever new data is generated, it is written to the database in India first and then it is synchronized with the other databases.

Consistency Levels

While maintaining data over multiple regions, the most common challenge is the latency as when the data is made available to the other databases. For example, when data is written to the database in India, users from India will be able to see that data sooner than users from the US. This is due to the latency in synchronization between the two regions. In order to overcome this, there are a few modes that customers can choose from and define how often or how soon they want their data to be made available in the other regions. Azure Cosmos DB offers five levels of consistency which are as follows:

  • Strong
  • Bounded staleness
  • Session
  • Consistent prefix
  • Eventual

In most common NoSQL databases, there are only two levels – Strong and EventualStrong being the most consistent level while Eventual is the least. However, as we move from Strong to Eventual, consistency decreases but availability and throughput increase. This is a trade-off that customers need to decide based on the criticality of their applications. If you want to read in more detail about the consistency levels, the official guide from Microsoft is the easiest to understand. You can refer to it here.

Azure Cosmos DB Pricing Model

Now that we have some idea about working with the NoSQL database – Azure Cosmos DB on Azure, let us try to understand how the database is priced. In order to work with any cloud-based services, it is essential that you have a sound knowledge of how the services are charged, otherwise, you might end up paying something much higher than your expectations.

If you browse to the pricing page of Azure Cosmos DB, you can see that there are two modes in which the database services are billed.

  • Database Operations – Whenever you execute or run queries against your NoSQL database, there are some resources being used. Azure terms these usages in terms of Request Units or RU. The amount of RU consumed per second is aggregated and billed
  • Consumed Storage – As you start storing data in your database, it will take up some space in order to store that data. This storage is billed per the standard SSD-based storage across any Azure locations globally

Let’s learn about this in more detail.

#azure #azure cosmos db #nosql #azure #nosql in azure #azure cosmos db

Azure Series #2: Single Server Deployment (Input)

In the previous article, we discussed the Gateway to your single server deployment (example: webserver). In this section, we shall continue with Input and Core Infrastructure.

Input for single-server deployment

When you talk about Data for your organization, it covers all three things, “People, Process, and Technology”. More details for the “Streaming and Sourcing Layer” can be found in a separate section (will update the link soon).

**_People: The Who. _**Producers and Consumers of data.

**_Process: The How. _**How the data is curated and put to use.

**_Technology: The What: _**What technologies are used to fetch, process, pass on and store.

Data: While People, Process and Technology is the golden triangle, if you think about it, the very reason the entire state-of-the-art ecosystem exists is merely to get the raw data to a usable form.

1. Data catalog

Any great state-of-art ecosystem is a waste if the data in need for consumers cannot be discovered and from the Producers side, if data cannot be documented/tagged properly that makes it useable for the consumers or end-users. Azure Data Catalog helps to bridge this gap of making the data correctly discoverable by fixing the traditional problems for both consumers and producers and also helps organizations to get the best value out of their existing information assets.

2. Streaming

While we will discuss more as part of the sourcing section, we shall cover the basics of streaming.

1/ Queue Storage

2/ Service Bus

3/ Event Hubs

4/ Event Grid

#azure-interview #azure-event-grid #azure-event-hub #azure #azure-service-bus