Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
THE FANTASTIC VOYAGE TO PAAS
ARE WE THERE YET?
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
DISCLAIMER
• The delivery and timing of any future functionali...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
THE BASELINE
WHAT WE ARE…
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
ABOUT SAS INSTITUTE INC.
• Independent software vendor
• Leade...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Image: Marcin Wichary // creative commons
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
cards;
Image: Marcin Wichary // creative commons
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
datalines;
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS SOFTWARE HISTORY
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS SOFTWARE
• IBM Assembler + PL/1
HISTORY
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS SOFTWARE
• IBM Assembler + PL/1
• UNIX / PC  C
HISTORY
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS SOFTWARE
• IBM Assembler + PL/1
• UNIX / PC  C
• C ported...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS SOFTWARE
• IBM Assembler + PL/1
• UNIX / PC  C
• C ported...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS SOFTWARE
• IBM Assembler + PL/1
• UNIX / PC  C
• C ported...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS SOFTWARE
• IBM Assembler + PL/1
• UNIX / PC  C
• C ported...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Typical SAS
Solution Architecture
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Typical SAS
Solution Architecture
JVM, Spring, tc Server
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Typical SAS
Solution Architecture
JVM, Spring, tc Server
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Typical SAS
Solution Architecture
JVM, Spring, tc Server
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Typical SAS
Solution Architecture
JVM, Spring, tc Server
C & C...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
THE PURPOSE
WHAT WE WANT…
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
developers
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
APIs are a force multiplier
(lever, fulcrum, pulley)
Developer...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Image: lowjumpingfrog // creative commonsImage: Beverley Goodw...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
PORTABILITY MULTI-VENDOR ARCHITECTURE
MVS
Windows
AIX
HP-UX
So...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
PORTABILITY MULTI-CLOUD ARCHITECTURE
MVS
Windows
AIX
HP-UX
Sol...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Plus ça change
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Dynamic Router
Cloud Controller
UAA/Login Servers Health Manag...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Dynamic Router
Cloud Controller
UAA/Login Servers Health Manag...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
THE INVESTIGATION
WHAT WE DID AND FOUND…
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Visual Analytics
Architecture
C & C++ servers
JVM, Spring, tc ...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Visual Analytics
Architecture
JVM, Spring, tc Server
C & C++ s...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Visual Analytics
Architecture
JVM, Spring, tc Server
C & C++ s...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Visual Analytics
Architecture
JVM, Spring, tc Server
C & C++ s...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Visual Analytics
Architecture
JVM, Spring, tc Server
C & C++ s...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Visual Analytics
Architecture
JVM, Spring, tc Server
C & C++ s...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS Studio
Architecture
JVM, Spring, tc Server
C & C++ servers
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS Studio
Architecture
JVM, Spring, tc Server
C & C++ servers...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS Studio
Architecture
JVM, Spring, tc Server
C & C++ servers...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS Studio
Architecture
JVM, Spring, tc Server
C & C++ servers...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS Studio
Architecture
JVM, Spring, tc Server
C & C++ servers...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS Studio
Architecture
JVM, Spring, tc Server
C & C++ servers...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Here be dragons
Image: Lars Kasper
// creative commons
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Hoisting helps…
// creative commonsImage: Contando Estrelas
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
Image: Official U.S. Navy Page // creative commons
Given the d...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
THE FUTURE
WHAT IS NEXT…
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
NEAR TERM
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
NEAR TERM
• Socialization
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
NEAR TERM
• Socialization
• Decision making - what is it?
• an...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
NEAR TERM
• Socialization
• Decision making - what is it?
• an...
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS Cloud Analytics
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS Cloud Analytics
Enabled by Cloud Foundry?
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
BINDABLE SAS ANALYTICS
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
SAS products
within
Cloud Foundry
Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
sas.com
THE END
© 2014
CoreLogic Innovation
Fueled by Cloud Foundry
Richard Leurig, Senior Vice President
Innovation Development Center
59
60
Technologies
540+ Products and 5000+ applications, components, services, and tools identified across CoreLogic
Business...
■ Multitude of technology platforms
■ Complex, hard-wired, fragile and expensive
■ Today’s technologies are radically diff...
CoreLogic Fabric
Engagement Services
CoreLogic Products & Solutions
CoreLogic Data Repository
Cloud Infrastructure as a Se...
DATA
PROVISIONING
ARCHITECTURE DATALAKE
INFORMATION
DELIVERY
ARCHITECTURE
Sources Production Ready Delivery to Application...
1. Developers focused on developing products, not managing tech stacks
2. Standard UI frameworks & style guidelines to spe...
Foundational Services
Platform Fabric
Infrastructure as a Service
Platform as a Service
Data as a Service
Development as a...
 Development as a Service capability
 Data as a Service capability
 Scalability & Resiliency
 Architectural agility
 ...
Pivotal provides ‘open’ PaaS + Big Data Suite + Development Lab
Pivotal Partnership
LABS
■ Open Source Standard
■ Hybrid I...
68
CoreLogic & Pivotal Collaboration
1. Exciting and rapidly changing times in the technology industry.
2. Capabilities available today weren’t around 2-3 year...
Questions and Comments
Richard Leurig, Senior Vice President
CoreLogic Innovation Development Center
rleurig@corelogic.com...
© 2014
Upcoming SlideShare
Loading in …5
×

The Fantastic Voyage to PaaS - Are we there yet? (Cloud Foundry Summit 2014)

4,238 views

Published on

Keynote delivered by Casey Hadden, Software Developer and Architect at SAS.

SAS is a software vendor with 35+ years of industry history (and 35+ years of software decisions). From mainframes, Unix workstations, and client-server to web applications, big data, and cloud; one constant has been the changing computing environment. Throughout these eras, SAS software and the SAS business has adapted to each change in order to deliver valuable analytics to our customers.

With cloud environments firmly ensconced and PaaS gaining traction every day, how does SAS rework its software and business again to compete and thrive in this environment? How can SAS help to fill in the 'Analytics' portion of an enterprise PaaS strategy?

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,238
On SlideShare
0
From Embeds
0
Number of Embeds
2,985
Actions
Shares
0
Downloads
46
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Good morning
    Casey Hadden, developer, STO, SAS Institute
    Walk through the case study, how we’re exploring
    Where starting,
    why CF of interest,
    what we’ve done and learned,
    peek at what’s next
  • SAS sells stuff
    I’m talking about what’s next
    We might not do that
    So, nobody get the wrong impression
  • So, let’s start with where we are…
  • ISV
    Customers are on premise
    Mix of physical and virtual
    Growing hosting and SaaS
    70K customers and 150 products
    Not just new, also moving current products and suites
  • Products have been around a while
    SAS existed for 38 years
    First was research project at NCSU on punch cards (300K LOC, 40 feet high!)
    See that in CARDS; statement
  • Data to operate on
    First platform entanglement
  • Punch cards go extinct and other platforms arise
    Still have CARDS; today
    But SAS had an opportunity to redefine itself on new platforms
  • So, we created: DATALINES;
    Spirit of radical innovation and disruption to CF
  • In all seriousness
    SAS has seen change 38 years.
    Changes drive SAS to redefine
  • Originally, IBM assembler and PL/1 on mainframes.
  • Unix Workstations and PCs intro’d
    Rewrite into C
    two major codebases
  • C code backported to mainframe
    IBM assembler retired
    start of SAS’s MVA.
  • Client-server and basic web
    SAS started Java for cross platform
    Continuation of portability
  • web applications and server side
    SAS embraced the middle tier concepts
  • Product list, bundling, and IT integration
    Drive common components
    Common needs to evolve separately
    SOA concepts introduced
  • Today, all of that this basic picture of a SAS solution.
    investigation of CF, 3 of the tiers here: web, services, and compute.
  • JVM,
    heavy spring framework and related
    run on the vFabric tc Server
  • common functionality provided by the SAS platform
    security, configuration, and licensing.
    All of that common, cross cutting stuff.
  • Solutions deploy alongside
    build their own services and interfaces
  • Both sit on top of the SAS compute tier and analytics that drive SAS value.
    servers are mostly C & C++.
    Investigate both middle tier apps port
    And how to best give those access to analytics
  • Move on to purpose – why, what drove?
    STO ties business drivers and quality attributes to R&D work
    CF obvious: cloud
    Quality attributes like scalability, availability, reliability
    But a more hidden one…
  • developers, developer enablement, developer experience.
    SAS started as language
    Language was interface for many years
    Evolve with modern user interfaces
    Core of analytics value is still in SAS language and servers
    Solutions generate SAS code
  • today, developers are a force multiplier.
    Great to get results without writing code
    Value truly shows when embedded in processes
    Where SAS user interface isn’t
    Past wrote SAS code
    But need access analytics other platforms
    Drive for APIs and development platforms like CF
  • Tech office wants hoisting, rising tide
    Logon application + SSO providers, Web application theming, server connections
    CF has same qualities: scalability + reliability
  • main arch hoisting – MVA
    Core of success – portability
    Bulk is portable, small set if specific
    Servers move to new platforms without a lot of work
    But, that story is changing…
    Previous OS of choice
  • Now IaaS of choice
    Where CF and BOSH dramatically hoist applications
  • Large dev community
    Many here for 20+ years
    call introduction anecdote

    Been through previous iterations
    Know effort and leery
    compare old and new
  • See CF architecture
    And overlap SAS bits
  • Lots of commonality
    SAS logon vs CF UAA
    CF DEA pool vs SAS tc servers
    Start from commonality instead of completely new
  • Have baseline and purpose, move on to actual investigation.
    Aware of CF for a while
    started looking more in January
    Let’s see what has happened
  • Same architecture picture
    Actually dealing with VA
    Define VA
  • Focus on middle tier
    Readily supported with java buildpack
    Uses bits like Spring that are well known and supported
    Lots of support for initial effort
  • Still need to connect to compute
    Use user provided services to focus
    Once we get one thing, another project for brokers
  • 8 applications – services and UI
    Changes related to tc Server ownership
    Different living by yourself
    Dependencies, JNDI, assumption: servlet context
    Pull inward, self reliant, 12 factor
    Other benefits - contention
  • Repetition
    Move jars, change config
    1 person, couple of weeks
  • Learn even without CF
    Still want architectural qualities
    Have concrete implementation to consider pros and cons
  • SAS Studio was next
    Define SAS Studio
    Different from typical solutions: scale up and down
    Same JVM and analytic server components, but fewer when scaled down
  • Focus on CF integration
    Service broker instead of UPS
  • single web application - services and UI.
    same types of changes as before.
  • New bit is service broker for workspace
    Define workspace server
    Java + Spring is core,
    Steve Greenberg skeleton
  • 1 person, 1 week
    Pivotal used to demo at SGF
    Talked about specifics
    Zoom out to larger takeaways
  • Here be dragons
    Applications too big, long startup, memory settings
    All telling us something
    CF forces or lose benefits
    Customize install for upload size, scaling, fork buildpack
    Already doing that, so we don’t get as big a win
  • Hoisting helps, process falls into place
    Single connection mechanisms let that be rewritten
    Then spring let us easily switch
    Then spring profiles let both side by side
  • Since we have drivers and attributes, CF can be enforcer
    Encourages behavior we want anyway
    CF citizens have good qualities
    Smaller, focused, start quickly, non-fragile
    Self sufficient, perform interrogation and initialization themselves
    CF rewards that behavior making wins
    Internal enforcer feedback
  • Now that we’ve gotten an idea about what it takes, where does that leave us to go next?
  • near term, still investigating.
    Ported several major applications
    have to apply across products.
  • Socialize across R&D
    Tech office does in small groups
    And large with tech radar
  • Have to make a decision
    Are we going to pursue?
    Another platform, preferred platform
    THE platform?
  • Big puzzle is analytic servers
    Have to make those readily available
  • Give positive deicision, several points
    SAS Cloud analytics
    Our cloud, SaaS
    Private analytics cloud – your cloud or public
    Not trivial
  • Can Cloud Foundry enable those deliveries?
  • Once running, enable developers
    Drive up value
    What analytical services to make available?
    Forecasting, data quality, sas language execution
  • Finally, can we ship our products that deploy within CF?
    Take CI and make the servers, services, and apps simply available?
  • The SAS case study
    Personally, I think there is a lot of value here for SAS
    Hope we come back and change might to did.
    Thanks for your time
    I hope you all enjoy the rest of the conference.
  • The Fantastic Voyage to PaaS - Are we there yet? (Cloud Foundry Summit 2014)

    1. 1. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. THE FANTASTIC VOYAGE TO PAAS ARE WE THERE YET?
    2. 2. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. DISCLAIMER • The delivery and timing of any future functionality described for our products is subject to change without prior notification. • Information regarding potential future products is not a commitment or obligation to deliver any code or functionality, and in no way represents contractual obligation by SAS.
    3. 3. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. THE BASELINE WHAT WE ARE…
    4. 4. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. ABOUT SAS INSTITUTE INC. • Independent software vendor • Leader in analytics • 70K+ customers, 91% of Fortune 100 • 150+ products, $3.08 billion revenue • 25% of revenue back into R&D
    5. 5. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Image: Marcin Wichary // creative commons
    6. 6. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. cards; Image: Marcin Wichary // creative commons
    7. 7. Copyr ight © 2014, SAS Institute Inc. All rights reser ved.
    8. 8. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. datalines;
    9. 9. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS SOFTWARE HISTORY
    10. 10. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS SOFTWARE • IBM Assembler + PL/1 HISTORY
    11. 11. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS SOFTWARE • IBM Assembler + PL/1 • UNIX / PC  C HISTORY
    12. 12. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS SOFTWARE • IBM Assembler + PL/1 • UNIX / PC  C • C ported back to MVS  MVA HISTORY
    13. 13. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS SOFTWARE • IBM Assembler + PL/1 • UNIX / PC  C • C ported back to MVS  MVA • Client-server  Java HISTORY
    14. 14. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS SOFTWARE • IBM Assembler + PL/1 • UNIX / PC  C • C ported back to MVS  MVA • Client-server  Java • Web applications  Middle tier HISTORY
    15. 15. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS SOFTWARE • IBM Assembler + PL/1 • UNIX / PC  C • C ported back to MVS  MVA • Client-server  Java • Web applications  Middle tier • Integration, independent evolution  SOA HISTORY
    16. 16. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Typical SAS Solution Architecture
    17. 17. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Typical SAS Solution Architecture JVM, Spring, tc Server
    18. 18. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Typical SAS Solution Architecture JVM, Spring, tc Server
    19. 19. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Typical SAS Solution Architecture JVM, Spring, tc Server
    20. 20. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Typical SAS Solution Architecture JVM, Spring, tc Server C & C++ servers
    21. 21. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. THE PURPOSE WHAT WE WANT…
    22. 22. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. developers
    23. 23. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. APIs are a force multiplier (lever, fulcrum, pulley) Developers are a force multiplier Image: Didier Baertschiger // creative commons
    24. 24. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Image: lowjumpingfrog // creative commonsImage: Beverley Goodwin // creative commons Architectural Hoisting Image: Koshy Koshy // creative commons
    25. 25. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. PORTABILITY MULTI-VENDOR ARCHITECTURE MVS Windows AIX HP-UX Solaris SunOS Linux Tru64 IRIXOS/2
    26. 26. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. PORTABILITY MULTI-CLOUD ARCHITECTURE MVS Windows AIX HP-UX Solaris SunOS Linux Tru64 IRIXOS/2 GCE
    27. 27. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Plus ça change
    28. 28. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Dynamic Router Cloud Controller UAA/Login Servers Health Manager DEA PoolService Broker Node(s) User Provided Service Instances Messaging (NATS) Apps Cloud Foundry BOSH Build Packs Logging Internet Underlying Infrastructure PaaS Apps Plus ça change
    29. 29. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Dynamic Router Cloud Controller UAA/Login Servers Health Manager DEA PoolService Broker Node(s) User Provided Service Instances Messaging (NATS) Apps Cloud Foundry BOSH Build Packs Logging Internet Underlying Infrastructure PaaS vFabric Web Server SAS Logon Manager Metadata Workspace Analytics 3rd Party Database vFabric tc Server(s) SAS APM Apps SAS Deployment Wizard / vApps On-premise, Physical hardware Plus ça change
    30. 30. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. THE INVESTIGATION WHAT WE DID AND FOUND…
    31. 31. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Visual Analytics Architecture C & C++ servers JVM, Spring, tc Server
    32. 32. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Visual Analytics Architecture JVM, Spring, tc Server C & C++ servers • Concentrate on Java middle tier
    33. 33. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Visual Analytics Architecture JVM, Spring, tc Server C & C++ servers • Concentrate on Java middle tier • User provided services for dependencies
    34. 34. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Visual Analytics Architecture JVM, Spring, tc Server C & C++ servers • Concentrate on Java middle tier • User provided services for dependencies • 8 Web applications
    35. 35. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Visual Analytics Architecture JVM, Spring, tc Server C & C++ servers • Concentrate on Java middle tier • User provided services for dependencies • 8 Web applications • 1 person, 2 weeks of effort
    36. 36. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Visual Analytics Architecture JVM, Spring, tc Server C & C++ servers • Concentrate on Java middle tier • User provided services for dependencies • 8 Web applications • 1 person, 2 weeks of effort • Informs architecture even without CF
    37. 37. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS Studio Architecture JVM, Spring, tc Server C & C++ servers
    38. 38. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS Studio Architecture JVM, Spring, tc Server C & C++ servers • Smaller, collapsed architecture
    39. 39. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS Studio Architecture JVM, Spring, tc Server C & C++ servers • Smaller, collapsed architecture • Service brokers instead of UPS
    40. 40. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS Studio Architecture JVM, Spring, tc Server C & C++ servers • Smaller, collapsed architecture • Service brokers instead of UPS • 1 web application
    41. 41. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS Studio Architecture JVM, Spring, tc Server C & C++ servers • Smaller, collapsed architecture • Service brokers instead of UPS • 1 web application • 1 service broker for SAS Workspace
    42. 42. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS Studio Architecture JVM, Spring, tc Server C & C++ servers • Smaller, collapsed architecture • Service brokers instead of UPS • 1 web application • 1 service broker for SAS Workspace • 1 person, 1 week of effort
    43. 43. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Here be dragons Image: Lars Kasper // creative commons
    44. 44. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Hoisting helps… // creative commonsImage: Contando Estrelas
    45. 45. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. Image: Official U.S. Navy Page // creative commons Given the drivers -- PaaS can be the enforcer
    46. 46. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. THE FUTURE WHAT IS NEXT…
    47. 47. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. NEAR TERM
    48. 48. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. NEAR TERM • Socialization
    49. 49. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. NEAR TERM • Socialization • Decision making - what is it? • another platform • preferred platform • THE platform
    50. 50. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. NEAR TERM • Socialization • Decision making - what is it? • another platform • preferred platform • THE platform • Analytic servers
    51. 51. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS Cloud Analytics
    52. 52. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS Cloud Analytics Enabled by Cloud Foundry?
    53. 53. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. BINDABLE SAS ANALYTICS
    54. 54. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. SAS products within Cloud Foundry
    55. 55. Copyr ight © 2014, SAS Institute Inc. All rights reser ved. sas.com THE END
    56. 56. © 2014
    57. 57. CoreLogic Innovation Fueled by Cloud Foundry Richard Leurig, Senior Vice President Innovation Development Center
    58. 58. 59
    59. 59. 60 Technologies 540+ Products and 5000+ applications, components, services, and tools identified across CoreLogic Business Criticality 80% of Applications are Mission Critical or Important Life Cycle Stage 48% of Applications in Maintain or in Maintain w/enhancements stage Users & Use Cases 2M+ professional users Sub-second to multi-day transactions Technology 63% of Applications utilize JAVA (42%) or .NET (21%) Mainframe NATURAL 330 - Applications Grow Maintain Enhance 3681 - Components Physical Logical TBD 1009 - Data Stores RDBMS Object Store Flat File TBD ■ 532 - Tools ■ 300 - Externals 832 - Other The CoreLogic Landscape
    60. 60. ■ Multitude of technology platforms ■ Complex, hard-wired, fragile and expensive ■ Today’s technologies are radically different from the past ♦ Mobility, Voice & Social Networks – Engagement norm ♦ “Platform as a Service” – Operating System norm ♦ “Infrastructure as a Service” – Compute & Processing norm ♦ “Data as a Service” – emerging ways of handling “big data” ♦ “Development as a Service” – Application build and deploy ■ Real opportunity to change what we do & how we do it 61 Fundamentals
    61. 61. CoreLogic Fabric Engagement Services CoreLogic Products & Solutions CoreLogic Data Repository Cloud Infrastructure as a Service Ubiquitous Access Single Sign-On Solution Modules (integrated or separate) Re-usable Services Scalable, Flexible & Efficient Data & Analytics Delivery Common Components & Services 62 CoreLogic Vision
    62. 62. DATA PROVISIONING ARCHITECTURE DATALAKE INFORMATION DELIVERY ARCHITECTURE Sources Production Ready Delivery to Applications CoreLogic Data Repository CoreLogic Solutions & Services 63 CoreLogic Information Delivery
    63. 63. 1. Developers focused on developing products, not managing tech stacks 2. Standard UI frameworks & style guidelines to speed up development 3. Components separated from applications allowing independent upgrading 4. Reusable services with built-in high availability, DR & elastic scalability 5. Resource flexibility enabled by standard technologies 64 CoreLogic Design Principles
    64. 64. Foundational Services Platform Fabric Infrastructure as a Service Platform as a Service Data as a Service Development as a Service CoreLogic Applications Engagement Services Products & Solutions Web, Mobile, Voice Services 65 “Everything as a Service”
    65. 65.  Development as a Service capability  Data as a Service capability  Scalability & Resiliency  Architectural agility  Hybrid infrastructure support  SDLC integration  Market adoption  Support & Operations  Ecosystem  Vendor lock-in concerns (Open) Evaluation Criteria: Results of mini-POC plus following considerations: Pivotal Cloud Foundry Google App Engine Salesforce Force.com Amazon AWS Oracle Fusion Red Hat OpenShift ■ Conducted mini-POCs to assess capabilities Engaging Technology Experts 66
    66. 66. Pivotal provides ‘open’ PaaS + Big Data Suite + Development Lab Pivotal Partnership LABS ■ Open Source Standard ■ Hybrid IaaS Support ■ Technically Sound ■ Industry Adoption ■ Extreme Agile ■ Pair Programming ■ Test Driven Development ■ Experience ■ State-of-the-Art Data & Analytics Tools ■ Strong Data Science Team BIG DATA SUITE 67
    67. 67. 68 CoreLogic & Pivotal Collaboration
    68. 68. 1. Exciting and rapidly changing times in the technology industry. 2. Capabilities available today weren’t around 2-3 years ago. 3. Enterprise organizations can now take advantage of the agility and capabilities of Silicon Valley startups. 4. Companies who adopt this “new norm” have a competitive advantage and can differentiate themselves in their markets. 69 Our Journey Begins…
    69. 69. Questions and Comments Richard Leurig, Senior Vice President CoreLogic Innovation Development Center rleurig@corelogic.com 70
    70. 70. © 2014

    ×