Slide 1

The Ball / SOS on Azure Part 1 Kalle Launiala, Citrus Solutions Oy kalle.launiala@citrus.fi

Slide 2

About the Presentation Part 1 What is The Ball / SOS platform about? SOS Design: Logical Architecture SOS Design: Building Blocks, Master Information vs. Relations Demo: Platform Executing on Azure #td2013fi

Slide 3

About the Presentation Part 2 Developer getting started from scratch Git clone, build, debug, deploy Developing HTML(5) + jQuery UI on The Ball Demonstrating Web / Worker Role responsibilities The Ball Architecture Overview & Deep Dive #td2013fi

Slide 4

Rgis Laurent Director of Operations, Global Knowledge Competencies include: Gold Learning Silver System Management What is the Platform? The Ball, SOS whole package running on Windows Azure Size of the scope?

Slide 5

Digital Service & Software Factory on Azure #td2013fi

Slide 6

Genuine, Native, Cross-Platform #td2013fi

Slide 7

What is it? Publishing system for authorised information Web content Digital content Digital app/service development & integration So is it like SharePoint or BizTalk or IIS? Yes How do you install it? You dont. Just deploy and run.

Slide 8

The Ball / SOS / WTF? The Ball is fundamental Originated from information models for storing and processing information Context-insensitive shapeshifter SOS = Service Operating System Service model supporting incarnation of The Ball Authorization boundaries Context-sensitive itself content context insensitive ADM = Abstraction Design Methodology Enables mainstream developer to pull off the above...

Slide 9

Slide 10

Slide 11

Slide 12

Slide 13

Slide 14

Slide 15

Slide 16

Slide 17

Slide 18

Slide 19

Slide 20

Slide 21

Slide 22

Rgis Laurent Director of Operations, Global Knowledge Competencies include: Gold Learning Silver System Management Reality Check! How does The Ball apply for todays tech & business?

Slide 23

Seeing is believing... git clone git://github.com/abstractiondev/TheBallOnAzure cd TheBallOnAzure gitupdateproject.cmd notepad README.txt

Slide 24

The Ball Applies & Accelerates Core Software Development Services Information Management + Collaboration System Integration Services with Master Data Model Business Process + EA Automation Mobile Worker Solutions

Slide 25

Visual Studio 2012 & Azure: Powered by ADM Semantic Information Models Logical Business Operations Integration Interfaces & Contracts

Slide 26

Rgis Laurent Director of Operations, Global Knowledge Competencies include: Gold Learning Silver System Management SOS Design SOS constraints on The Ball

Slide 27

Logical Architecture is... Constraints Given and designwise chosen Reflecting real world and practices TODAY Giving the boundaries for practical implementation

Slide 28

Generic App Architecture

Slide 29

Implicit or explicit; architecture is

Slide 30

Collaboration: Roles & Emails People act as a role People collaborate with other people because of their role People trust emails Stronger trust is required for official actions SOS enables all the above to be digitally accelerated

Slide 31

Information is Owned Information has always owner Owner does not mean copyright holder However copyright holder IS an owner Owner authorizes the further use/distribution Privacy aspect is CRITICAL

Slide 32

Case: Smart Traffic Privacy Issues

Slide 33

... Applies everwhere

Slide 34

Rgis Laurent Director of Operations, Global Knowledge Competencies include: Gold Learning Silver System Management SOS Design Implementation Decisions

Slide 35

Collaboration: Roles & Emails

Slide 36

Authorization Contexts

Slide 37

Security Boundaries Recognized

Slide 38

Drill Down to Relevance... Users want unified experience Based on the interface, not on the application Applications and services are to serve Focus on usability not on bling-bling Applications need only fraction of information to operate their part Android apps partially use this kind of architecture

Slide 39

Service / Service Bus Interface Interface definition is like pseudo-language method call... Executing code ALWAYS knows what to call and from where Explicit semantics apply in reality MyApp.Customer != YourApp.Customer

Slide 40

Client-Server Service Interfaces

Slide 41

Service Bus Distributed Architecture

Slide 42

Pure Distributed Architecture

Slide 43

Auhtorized Producer - Consumer

Slide 44

Slide 45

Rgis Laurent Director of Operations, Global Knowledge Competencies include: Gold Learning Silver System Management Discovering Services Matching Consumer-Provider

Slide 46

Information = Real World Digital Automated Process Order pizza What kind of a Pizza? Pay your order Receive your pizza Manual Process Order pizza What kind of a pizza? Pay your order Receive your pizza

Slide 47

Real World Service Discovery

Slide 48

... Human Agreed Interfaces

Slide 49

Semantic Interface Matching Accepting the fact about implicit semantics MyApp.Customer != YourApp.Customer Both apps still have Class customer Integration needs to do semantic mapping (semantic.namespace.included) (semantic.ns.included)... Hash value is used to identify matching interfaces Mapping interface values as accordingly

Slide 50

Case ETLA: Real World Hospital Bluetooth, Acceleration Meters, GPS to track down real world nurses Real world processes != Consultant made processes More info from: http://blogs.etla.fi/palveluprosessi/

Slide 51

Rgis Laurent Director of Operations, Global Knowledge Competencies include: Gold Learning Silver System Management SOS Design Building Blocks

Slide 52

Slide 53

Slide 54

Building blocks... Information Model Class models with namespaces Process Model Service method model with orchestration sequence ADM module will concretize these to: Service Interface (platform agnostic; native code) Class model, serialized to storage Native code execution sequence Explicitly defined, documented, trackable, auditable...

Slide 55 ."> ..."> ." title="Example of Information Model .">

Example of Information Model ...

Slide 56

Example of Process Model

Slide 57

Rgis Laurent Director of Operations, Global Knowledge Competencies include: Gold Learning Silver System Management Master Information Management Relations in concrete manner

Slide 58

Master of information recognized Updates to master first Populating with subscription/monitoring Evaluation chains topology-sorted Series of updates updated as atomic sequence Scales well, because context size is small Security context or semantic context boundaries Replaces traditional relations Information is complete at every relevant stage

Slide 59

Slide 60

Rgis Laurent Director of Operations, Global Knowledge Competencies include: Gold Learning Silver System Management Demo Platform Executing

Slide 61

2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentations. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. Thank you for coming! Feedback can be given via mobile or laptop through techdays.fi seminar schedule. techdays.fi #td2013fi