Angular with Serverless backend API using Azure Functions

What to expect

  • Setting common understanding

    • What, Why and How

  • Demo
    • Run the Test Project
    • Explore the project code Implementation
    • Visit Azure Portal
      •  Azure Functions,CosmosDb, APIM
  • Q & A

Ryan Niño Dizon

linkedin.com/in/ryanninodizon
sessionize.com/ryanninodizon
youtube.com/@LearnWithJon
medium.com/@ryanninodizon
github.com/ryannninodizon

What is Serverless 

No infrastructure management
 

Using fully managed services enables developers to avoid administrative tasks and focus on core business logic. With a serverless platform, you simply deploy your code, and it runs with high availability.

Dynamic scalability



With serverless computing, the infrastructure dynamically scales up and down within seconds to match the demands of any workload.

Faster time to market


Serverless applications reduce the operations dependencies on each development cycle, increasing development teams’ agility to deliver more functionality in less time.

More efficient use of resources

 

Shifting to serverless technologies helps organizations reduce Total Cost of Ownership (TCO) and reallocate resources to accelerate the pace of innovation.

What is Serverless 

Serverless Computing vs. Traditional Computing

backend/service/api

{Id:123,Name:"Ryan",LastName:"Dizon"}

 

backend/service/api

{Id:123,Name:"Ryan",LastName:"Dizon"}

 

(Runtime: 100ms)

(Uptime: 72h)

Azure Function Apps 

Events

Code

Output

Azure Function Apps 

Web/Mobile Apps Backends

Scheduled Task Automations

Workflows and Orchestrations

IoT Connected Backends

Stream Processing

Machine Learning

FaaS is at the center of serverless

Single Responsibility
 

 

Functions are simple, reusable bits of code that do a specific job, take an input and give back a result.

Short-Lived


 

Functions don't stay after they finish doing their job, making resources available for more tasks.

Stateless

 

Functions don't remember things or depend on what other tasks are doing.

Event-driven and scalable

 

Functions react to set events and quickly make copies as many times as necessary.

Workflow and orchestration with Durable Functions

Manageable sequencing

External events correlation

Process Monitoring

Fanning out and fanning in

Http-based async long-running APIs

Human Interaction

Hosting Plans

Consumption Plan
 

 

Event-driven scaling(to zero)

Only pay for what you use

Premium Plan


 

Event-driven scaling

 

Pre-warmed instances

 

Additional networking options

App Service Plan

 

CPU/memory scaling

 

Always on

 

Additional networking options

App Service Environment

 

CPU/memory scaling

 

Always on

 

Most robust netwrorking options and isolation

Add Azure SDK Tools

Enough Slides presentation and show us the code!

DEMO

linkedin.com/in/ryanninodizon
sessionize.com/ryanninodizon
youtube.com/@LearnWithJon
medium.com/@ryanninodizon
github.com/ryannninodizon

Thank you

for having me here

Made with Slides.com