Tech Interview

Front End

Visual side of application.

Ux/UI Design

React / Angular Frameworks

• javascript library for building UI

• changing the function updates the UI

• tons of libraries out there

Back End

Database

APIs

Cloud Servers

.Net Framework

software development tools for building and running Web applications, Web Services, Windows Mobile, Desktop Apps

Shared Class Libraries

APIs

Multiple Languages (C# VB and Python)

Security

DB work w/out SQL

Azure

Public cloud computing platform that provides a variety of services for developing web applications

App Development

Testing

App Service - don’t need infrastructure concerns like a VM

VMs

Analytics

Storage - Virtual Hard Drives

Azure Storage

Disaster recovery

Select multiple datacenters for VMs or serverless

Azure Virtual Machines

Create a processor for your application. Likely need multiple and they all need storage, fileshare, and servers

They need infrastructure like data warehouses

Use this for things that are not web or mobile apps

Azure App Service

Platform as a Service instead of VMs

Host web and mobile without infastructure

Upload code to app service instance and let app service handle details

Rest APIS

Azure Containers

Self contained software environments- No OS

Could have entire application and third party packages

Easy to deploy versus VMs

Provide container with code and config and it will build your application

Can run batch jobs without environment and dependencies

Container Orchestration Solutions help implement microservices

Azure Functions

Serverless solution versus containers where you just provide code and the cloud handles where it runs. no datacenters

You are only running individual functions versus an entire application

Azure Blob Storage

cloud based non-structured data storage

Networking / VMs

Shared infrastructure in the cloud

VMs

• Non one outside network can see comms

• Would not allow out of network comms w/ db

• can separate public and private networks with subnets

API

Application Programming Interface

JSON/XML

Each Request/Response is an API call

Server Endpoint, Header, Response

REST API

Representational State Transfer Application Programming Interface

Standardized industry wide. Don’t need to worry about formatting.

• HTTP Requests

• Client and Server Application

• Used for microservices

• Stateless - dont need to worry about state of data

• Caching - high performance

CRUD

CREATE → POST

READ → GET

UPDATE → PUT

DELETE → DELETE

REST API Makeup

Header - API Key and authentication Data

Operation: Get, Delete, Update etc

EndPoint - URL (https://icecream.com/api/flavors

Param/Body - the information being passed to the server

REST API Ice Cream Example: Read/Get

Operation: Get

Endpoint: /API/Flavors

Param/Body:

Response: ID 0 = Strawberry, ID 1 = Mint

Rest API Example: Replace

Operation: Put

Endpoint: /API/Flavors/1

Param/Body: Flavor: Chocolate

Response: 1 is now chocolate

Rest API Ice Cream Example: Post/Create

Operation: Post

Endpoint: /API/Flavors/2

Param/Body: Flavor 2 = berry

Response: 2 is now berry

Salesforce

CRM Cloud software

Ecommerce

Analytics

AI

QlikView

Cloud Based SaaS Analytics

SAP

Operations and customer relations for businesses

• customer satisfaction

• systems apps and products

Azure Storage

Blob

File storage

SQL DB

Cache

Azure VNET

Virtual network for VMs so that they can communicate

Outbound and inbound traffic to internet