imc - it trend 2014 : from private cloud to saas

36
Danupol Siamwalla [email protected] ICE Solution Ltd. Cloud Computing: From Personal Cloud to SaaS

Upload: danupol-siamwalla

Post on 07-Jan-2017

903 views

Category:

Technology


0 download

TRANSCRIPT

[email protected] ICE Solution Ltd.

Cloud Computing: From Personal Cloud to SaaS

Cloud Computing: From Personal Cloud to SaaS

Your Expectation?

Less information and more experience and adaptation

As organisation, how you can adopt SaaS

Real life Experience to share

Set of Expectation

โลกเราจะอยู่ยากขึ้นหรือง่ายขึ้น?

โลกเราจะอยู่ยากขึ้นหรือง่ายขึ้น? เทคโนโลยีกำลังพาเราไปไหน? จะใช้ชีวิตอย่างไร?

องค์กรต้องปรับตัวเพิ่มขึ้นอย่างไร ไอทีเราต้องทำงานเปลี่ยนไปอย่างไร

“Digital Gap”

Trending 2014

Focus Point Point 1: SaaS —> IaaS —> PaaS Point 2: Spear head solution andmarket solution Point 3: BPaaS is coming

Mobile Device Diversity and ManagementMobile Apps and Applications

The Internet of Everything

Hybrid Cloud and IT as Service BrokerCloud/Client ArchitectureThe Era of Personal Cloud

Software Defined Anything

Web-Scale ITSmart Machines

3-D Printing

http://www.crmlandmark.com/crmlabsindustrytrends.htm

SaaS จะเกิดขึ้นได้ ต้องอาศัยการมององค์กรเป็นกลุ่มงาน กลุ่มกระบวนการ กลุ่ม Application

http://martin-fulcrum.blogspot.com/2012/02/as-pendulum-swings-users-vs-enterprise.html

Case Study : DHAS Dropbox

ARCHITECTURE

http://blog.cobia.net/cobiacomm/2013/04/18/cloud-native-paas-architecture/

Multi-tenant architectureSingle version of the application & InfrastructureUsed for all customers

Some SaaS solutions do not use multi-tenancy

Virtualisation

Multitenant vs Virtualisation (Controversial)

Existing SaaS Concept

Case Study: ลูกค้ากลุ่มยา และเครื่องสำอางค์

Important Note Management by SLA Policy !!

Important Note: 1. ต้องแยกกระบวนการย่อย 2. ต้องสร้าง Architect ที่เหมาะสม 3. เริ่มมองเป็น Layer 4. เริ่มแตกเป็น Process 5. บาง Process เก่งบางเรื่องก็นำ

มาใช้

CHARACTERISTICS

Configurable and Customisable

Extreme fast deploymentSoftware Update mechanism Fast development, testing with single environment configuration

Who own?Who own software? Who own Data? Who own Configuration? Who own Process IP? —> Competitive advantage?

Rights?Rights to access configuration Rights to access data for testing purpose Rights to access user behaviour

ADOPTION DRIVER

Conclusion for Adoption reasons

TCOExpense vs Investment Less Operation expense Adoption Speed and Cost Better result with regional deployment

StandardisationStandard process for easier deployment Initial configuration for faster setup & startup Gain better acceptance (from personal to enterprise)

Easier Deployment & MaintenanceOn the fly deployment and expansion Accessibility to local support Sustainability for on premises provider

OBSTACLES

With SaaS, the users do not have a copy of the executable file: it is on the server, where the users can't see or touch it. Thus it is impossible for them to ascertain what it really does, and impossible to change

it. SaaS inherently gives the server operator the power to change the software in use, or the users' data being operated on.

Users must send their data to the server in order to use them. This has the same effect as spyware: the server operator gets the data. She/he gets it with no special effort, by the nature of SaaS. This gives

the server operator unjust power over the user.

http://en.wikipedia.org/wiki/Software_as_a_service

Identity Management (On premises, Cloud) Security

Data Integration & Synchronisation

Security (Data Protection)

On Premise Data Integration

OBSTACLES

[email protected] ICE Solution Ltd.

Cloud Computing: From Personal Cloud to SaaS