business application architecture in modern multi-cloud environment / microsoft saas + serverless...

Business application architecture in modern multi-cloud environment

-Microsoft SaaS Business application type-

Kazuya Sugimoto Tokyo .NET Developers Meetup #26 - 2017-10-24

See the World as a Database

Speaker

Kazuya Sugimoto

• CData Software Japan, LLC Lead Engineer

• Japan Dynamics User Community Member

• Microsoft MVP for Business Solution

• From Aomori. My company at Sendai.

Blog：Morning Girlhttp://kageura.hatenadiary.jp/

Twitter：@sugimomoto Facebook：sugimomoto

CData Software, Inc. (http://www.cdata.com/)

Started: 1994 (/nsoftware)

Location: Chapel Hill, NC, USA

CData Japan: 2016/6 (JV with Infoteria) (http://www.cdata.co.jp)

About

“CData Software is a leading provider of data access and connectivity solutions. We specialize in the

development of Drivers and data access technologies for real-time access to on-line or on-premise

applications, databases, and Web APIs.

Our drivers are universally accessible, providing access to data through established data standards and

application platforms such as

ODBC, JDBC, ADO.NET, OData, SSIS, BizTalk, Excel, etc.”

http://www.cdata.com/

http://www.cdata.co.jp/


Topics

Business application architecture in modern multi-cloud environment.

Microsoft SaaS + Serverless Architecture (FaaS) Approach


Why is it now required to connect cloud business applications?

1.


Recent FAQ Topics

Recently, my company has many inquiries "I want to connect the cloud more flexibly and smoothly".Cloud service is indispensable for us now.And I use a lot of cloud services.

Web site

BI

SNS

IoT

SharePoint


Data in cloud era

using multiple SaaS and on-premise custom application

in combination

How to cooperate data between applications and services is a key

point


Centralized Management

Marketing

Product

Inventory

Data

Integration

Platform

Manual

work

DWH

BI

Customer

Deal

Integrated management centered on

data platform

using (ETL / EAI /

DWH)


Distributed Management

Marketing

Product

Inventory

Manual

work

DWH

BI

Customer

Deal

All applications and services are

connected by "many-to-many"

Micro service architecture


Comparison

Centralized Management Distributed Management

Bimodal Mode1 (SoR/System of Record) Mode2 (SoE/System of Engagement)

Initiative IT department End user department

importance Stability Speed · Convenience

It is not a story of which is superior, but based on each characteristic, it

is selected

Hybrid operation and shift (distribution → concentration) are

also necessary


Why is it desirable to use serverless?2.


Microsoft Serverless Service

Flow Logic Apps Functions

User End user Power user Developer

How to makeWorkflowDesigner

WorkflowDesigner

Programming

StoryFor simple business

optimization,

If your integration scenario is too

advanced for Flow

If a step in your integration scenario

requires highly custom

transformation


DEMO：Link inquiry data to SharePoint

SharePoint

Money

forward

Storage

FunctionsServiceBusAzure SQLWeb appsCustomer Support

Azure FunctionsSetting data

Azure FunctionsSetting data

CustomerTrade History

SupportBusiness

Management


Serverless Architecture Pros

Loosely coupled asynchronous

Quick development, use and verification

Freedom of scale

Realize a smooth business process

Agile & business use verification

Retry possible

Respond quickly to business expansion


Serverless Architecture Cons

Restrictions on APIs supported by

serverless service

Retry processing on failure

State monitoring

Using Web api tool

3rd party tool

UsingMessaging service

Queue service

Monitor serverlessservice with

serverless service


Summary

· Serverless architecture is effective for connecting any business applications.

· Applications are not to be used independently but to use while relying on various SaaS


Thank you!

business application architecture in modern multi-cloud environment / microsoft saas + serverless...

Technology