Microservices and Azure App Services

MICROSERVICESAzure App Services

Damir Dobricdaenet

Agenda

Microservice and

Architecture Styles

Scale Cube

From Monoliths to

ldquoMicrordquo

API Gateway Pattern

Azure App Services

Api Apps + Logic Apps

What to expect

How about SOA

ldquoService orientation is a means

for integrating across diverse systemsrdquo

System 1 System 2

System 3

Microservices ApproachldquoMicroservices is an (trendy) Architektur Style to design a single

complex application as a group of small (micro) services whichare independend in development and deploymentldquo

Service 1 Service 3

Service 2

All services build ONE

system

Theory of Microsevices

Scale Cube

X = Loadbalancing scale Y = Functional Scale Z = Data Partitioning

X-Scale (Loadbalancing)

Node1 Node 2 Node N

DB

Share traffic across multiple nodes is ldquoeasyrdquo

Relational DB scales vertically only Horizontal scale is very difficult

Z-Scale (Data Partitioning)

Tire 1

DB2

Customers 0-10000

DB1

Customers 10001-hellip

Tire 1

DB2

Tenant 2

DB1

Tenant 1

Microservice = Y-Scale

PurchasingOrder

Tracking

DB

Microservice

Feature N

DB DB

Microservice

From Monoliths to Micro

Melvin Conwayrsquos LowldquoOrganizations which design systems are constrained to produce designs which are copies of the

communication structures of these organizationsrdquo

Wikipedia James Lewis + Martin Fowler

Three+ Tire Architecture

Result of organization described by Conwayrsquos low

Donrsquot panic Architecture is ok But Organization tends to produce monolithics

based on this architecture

Issues with MonolithsThis is typically 1 Binary

ie mdwdll

(I)You cannot combine

technologies if you use binary dependency

(II)Increasing number of features slows down

flexibility

(III)Growing application

increases complexity Growing across multiple

features means exponential complexity

(IV)Growing application

can slow down performance

(V)Growing application make maintenance

more complex

(VI)Cannot replace

application (or parts) prevents of using of

innovations

(VII)Application

Replacement ldquoimpossiblerdquo

Think ldquomicroldquo (mycro)

N-Tire is Ok butMonolith is NOT ok

Organize Application in Smaller independent (micro) components

If microComponents have to exchange information

define them as services

Microservice ArchitectureHmm but what

is the AppService

Need to ask my architect

Sorry guys but this is not a

Mycro-Service

hellip I mean this is not a ldquo3-tirerdquo architecture

$

DB DB DB

API Gateway These are Microservices They are typically used

inside of enterprise boundary

These is not a Microservice It is publicly accessable service used for integration (SOA) which consumes

and orchestrates Microservices

Hexagonal Architecture

A A A

SOAP AdapterEDIfact Adapter

REST AdapterA

AMQP Adapter

Microservice

Ports are logical artefactsAdapters are physical

implementation of ports

Issues with Microservices

Developers must be more operation focused due increased complexity

More discipline required in development documentation and deployment

Increased Dependencies

Multiple Versions of Services side by side (code immutability)

More complex test requirements

Every system is distributed system

Communication between services is slower (network)

Transaction compensation is more complex

Azure App Services

Microservices Composition

Service 1 v11 Service 3

Service 2

v1

Service 2

v2Service 1 v11

All services are packaged as NuGet package

NuGetPackage v2

NuGetPackage v11 Downloads a NuGet package2 Adds a reference to a NuGet

package

What did we learn today

We still have to hammer

Q amp A

Microservices(Azure App Services amp Co)

DAMIR DOBRIC

damirdobricdaenetcom

b-dadobrmicrosoftcom

Microsoft PTSP

(Partner Technical Solution Specialist)

Microsoft Most Valuable ProfessionalBlog Twitter

CloudAppsCloud CloudConsultingCloudAppsMiddlewareCloudAppsMiddlewareSoftware

Q amp A

Api Apps

References

bull Microservces

ndash httpmartinfowlercomarticlesmicroserviceshtml

ndash httpenwikipediaorgwikiMicroservices

ndash httpmicroservicesiopatternsmicroserviceshtml

ndash httpwwwinfoqcomarticlesmicroservices-intro

ndash httpgeekswithblogsnetcyoungDefaultaspx

bull API Apps Documentation

ndash Overview

httpazuremicrosoftcomen-usdocumentationarticlesapp-service-api-apps-why-best-

platform

ndash Connectors

httpazuremicrosoftcomen-usdocumentationarticlesapp-service-api-dotnet-triggers

bull Insert Into TestTable (Name toolnumber status) Values (Order1 abcde1 0 )

bull select count() from TestTable where status = 0

bull select count() from TestTable where status = 1

bull Update TestTable Set [Status] = 1 WHERE Status = 0 Select from TestTable WHERE [Status] = 1

bull Update TestTable Set [Status] = 2 WHERE status = 1

bull Select TOP(100) from TiglidurStandardTool

bull Select TOP(100) from TestTable

Logic Apps

Main point inserted in a form of a text

Use Yellow to impact key messages

Use short and direct text one row if you can

Donrsquot use bullets here but creative text

Title of key segment

USE CAPS FOR SECTIONS

TITLE OF THE SUBTHEME

Sub theme of presentation

Here are the bullets

My theme number one

bull Bullet 1

bull Bullet 2

bull Bullet 3

My theme number two

bull Bullet 1

bull Bullet 2

bull Bullet 3

Photo title

Text about the photo above

Nagrađujemo vas sa

100 WinCoin bodova što

ste posjetili predavanje

Osvojite dodatnih

100 WinCoin bodova

ukoliko popunite službeni

upitnikHVALA

MVAhttpwwwmicrosoftvirtualacademycom

Uspješni profesionalci nikad ne prestaju učiti Microsoft Virtual Academy nudi online Microsoft treninge vođene od eksperata da pomognu profesionalcima u daljnjem usavršavanju Treninzi su vođeni od vrhunskih stručnjaka na različitim tehnološkim područjima Nakon odslušanog treninga možete također provjeriti svoje znanje

Za bolje razumijevanje ovoga predavanja savjetujem da odslušate treninge na temuXXX1XXX2XXX3

Naziv treninga 1link1

Naziv treninga 2link1

Naziv treninga 3link1