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

What is GEEK

Buddha Community

Azure Series #2: Single Server Deployment (Input)
Aisu  Joesph

Aisu Joesph

1626490533

Azure Series #2: Single Server Deployment (Output)

No organization that is on the growth path or intending to have a more customer base and new entry into the market will restrict its infrastructure and design for one Database option. There are two levels of Database selection

  • a.  **The needs assessment **
  • **b. Selecting the kind of database **
  • c. Selection of Queues for communication
  • d. Selecting the technology player

Options to choose from:

  1. Transactional Databases:
    • Azure selection — Data Factory, Redis, CosmosDB, Azure SQL, Postgres SQL, MySQL, MariaDB, SQL Database, Maria DB, Managed Server
  2. Data warehousing:
    • Azure selection — CosmosDB
    • Delta Lake — Data Brick’s Lakehouse Architecture.
  3. Non-Relational Database:
  4. _- _Azure selection — CosmosDB
  5. Data Lake:
    • Azure Data Lake
    • Delta Lake — Data Bricks.
  6. Big Data and Analytics:
    • Data Bricks
    • Azure — HDInsights, Azure Synapse Analytics, Event Hubs, Data Lake Storage gen1, Azure Data Explorer Clusters, Data Factories, Azure Data Bricks, Analytics Services, Stream Analytics, Website UI, Cognitive Search, PowerBI, Queries, Reports.
  7. Machine Learning:
    • Azure — Azure Synapse Analytics, Machine Learning, Genomics accounts, Bot Services, Machine Learning Studio, Cognitive Services, Bonsai.

Key Data platform services would like to highlight

  • 1. Azure Data Factory (ADF)
  • 2. Azure Synapse Analytics
  • 3. Azure Stream Analytics
  • 4. Azure Databricks
  • 5. Azure Cognitive Services
  • 6. Azure Data Lake Storage
  • 7. Azure HDInsight
  • 8. Azure CosmosDB
  • 9. Azure SQL Database

#azure-databricks #azure #microsoft-azure-analytics #azure-data-factory #azure series

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

Azure Series #2: Single Server Deployment (Core Infrastructure — II)

4. Virtual Machines

Virtual machines are the computers you can hire on the Azure cloud. You can choose any OS including but not limited to Windows, Linux image, etc. You can choose the CPU, Memory, Network Interface Card (NIC), and Storage based on the workloads that you want to migrate or create new workloads in your virtual machines. A firm can have as many Virtual machines as you may see in the server rooms across regions in the organizations. If you want to deploy advanced solutions such as Big data or voluminous data processing, then you can choose an optimal server configuration. Virtual Machine is part of Virtual Network and Subnet. Whether or not you want to expose the VM publicly depends on which tier of the architecture your VM is going to sit.

Why use Virtual Machine:

Virtual Machines are nothing different from the Application Servers, Database Servers, Web Servers, Phone servers, etc. that are part of your primary and secondary site on-premise. Instead of these servers managed and maintained by the Infra team, the servers will be deployed by the cloud management team but will be managed by the Infra team of your organization and you shall deploy workloads on it. As per the shared security model, whatever that goes into the Virtual Machine, you are responsible to maintain, manage upgrades and ensure security. Whatever is deployed by Aure such as Linux VM, Windows VM, etc., upgrades and next versions will be automatic and downtime will be managed by Azure and will be notified to you. If you are procuring VM and deploying Database on it, then it becomes your responsibility to upgrade the database as it is not managed by Azure. Knowing this difference between unmanaged and managed is critical.

Types of Virtual Machine:

  • **Linux Virtual Machine: **Azure endorsed distribution has Linux on Azure includes SUSE, Redhat, Debian, etc., and Docker, Jenkins from the marketplace.
  • Windows Virtual Machine
  • SQL Server on Virtual Machine
  • **Data Science Virtual Machine **(Discussed in a later section)
  • **Virtual Machine Scaling Sets **(Discussed as part of Multi Scaleable server deployment)
  • Azure Bastion

These Virtual Machines are available in various sizes. We can logically group these sizes based on the key characteristics of the VM

  • Based on CPU: General Purpose or Compute Optimized with very good computing power. Balanced memory to CPU ratio. Advanced options include GPU (special machines) or HPC (for Big data or ML).
  • Based on Storage: Storage optimized with high disk throughput and space.
  • Based on Memory: Memory-optimized with high memory to CPU ratio.

#azure-batch #azure-interview #azure #azure

Azure Series #2: Single Server Deployment — part 1

Let’s assume for your organization, you know the number of users who will be accessing your application (web / mobile / BI reports) are defined and it does not fluctuate drastically like an Internet Organisation. All the fluctuations are measured and it is a step-up progression, measured and occurs over several years rather than like an erratic ECG graph. Your business could be a business with big ticket customers and is not catering for economies of scale. In such cases, you can go for Single server deployment in this case without over-engineering your business process and avoid unnecessary spend. Single server deployment for a lean and mean organization.

Gateway to your single server deployment

**Security **in general: Any cloud architecture should be ring fenced and also it should be security encompassing architecture in the sense that each and every resource that we deploy for the Single server architecture must have security-first architecture. Refer to “Azure Series #2: Cloud Security Roadmap” and Azure’s Security Benchmark.

1. Azure Active Directory

2. DNS

3. CDN

4. Advanced Threat Protection

5. DDoS Protection service

#azure-active-directory #azure-interview #azure-infrastructure #azure

Ruthie  Bugala

Ruthie Bugala

1620435660

How to set up Azure Data Sync between Azure SQL databases and on-premises SQL Server

In this article, you learn how to set up Azure Data Sync services. In addition, you will also learn how to create and set up a data sync group between Azure SQL database and on-premises SQL Server.

In this article, you will see:

  • Overview of Azure SQL Data Sync feature
  • Discuss key components
  • Comparison between Azure SQL Data sync with the other Azure Data option
  • Setup Azure SQL Data Sync
  • More…

Azure Data Sync

Azure Data Sync —a synchronization service set up on an Azure SQL Database. This service synchronizes the data across multiple SQL databases. You can set up bi-directional data synchronization where data ingest and egest process happens between the SQL databases—It can be between Azure SQL database and on-premises and/or within the cloud Azure SQL database. At this moment, the only limitation is that it will not support Azure SQL Managed Instance.

#azure #sql azure #azure sql #azure data sync #azure sql #sql server