Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Customer Success: Java Micro-
Services with Pivotal Cloud Foundry on
Azure
Thomas Fredell (Chief Product Officer) Ashish P...
Our Journey
2
• Who is Merrill
• Business Challenges & Opportunities
• Conceptual Architecture
• Why PCF?
• Why Azure?
• T...
Thomas Fredell, Chief Product Officer
3
Ashish Pagey, Architect
4
Who is Merrill Corporation?
5
About
6
 50 year history! Now, SaaS + Service!
 Financial Transactions & Reporting
 Marketing & Communications for
Regu...
Quick Poll
7
 Who’s using Azure?
 Who’s doing Microservices?
 Who’s using PCF?
 Who is using PCF on Azure?
Our Journey
8
• Who is Merrill
• Business Challenges & Opportunities
• Conceptual Architecture
• Why PCF?
• Why Azure?
• T...
Global Opportunities
9
Customers
everywhere!
Data residency
requirements…
Security and Compliance Needs
10
Security and
compliance essential…
architected in from the
beginning
Need to Move Fast
11
Competition moves fast.
How do you disrupt, not
get disrupted?
Old, monolithic systems
12
Prior platform –
Monolithic! Hard
/ Slow to change
Need for Coaching & Support
13
Managing change is hard.
Good coaching and
support is critical to ease
the way.
Our Journey
14
• Who is Merrill
• Business Challenges & Opportunities
• Conceptual Architecture
• Why PCF?
• Why Azure?
• ...
App1
Moving from…
15
POJO Beans
App2
POJO Beans
App3…
POJO Beans
Moving to…
16
REST Service APIs
Service Container
Pivotal Cloud Foundry
Infrastructure
(Azure IaaS)
3rd Party tools)
Micro...
Our Journey
17
• Who is Merrill
• Business Challenges & Opportunities
• Conceptual Architecture
• Why PCF?
• Why Azure?
• ...
POC Goals and Success Criteria
18
Pivotal
Use Case
Number
Pivotal Use Case Merrill Success
Criteria
Pivotal
reference
arch...
Of many options, PCF won because…
19
Azure IaaS
Pivotal Cloud
Foundry
Spring Boot, Spring
Cloud
Azure
Service
Fabric
Sprin...
Our Journey to Cloud Native
20
Research,
comparison due
diligence
4 week technical PoC
PoC findings, decision,
procurement...
Our Journey
21
• Who is Merrill
• Business Challenges & Opportunities
• Conceptual Architecture
• Why PCF?
• Why Azure?
• ...
Azure Security & Compliance
22
Azure Global Footprint
23
26 regions!
With 8 to come.
24
ASP.NET 5 Preview
Azure SDK 2.5.1
Team Foundation Server 2015 preview
Azure Machine Learning GA
Azure HDInsight for Lin...
Our Journey
25
• Who is Merrill
• Business Challenges & Opportunities
• Conceptual Architecture
• Why PCF?
• Why Azure?
• ...
Lessons on the way to production…
26
 Learning curve is steep... plan
to get help!
 Organization changes to both
people ...
Our current state by the numbers
27
Scrum teams
using PCF6Spaces in one
PCF domain2
Time to deploy new
app <1d
Meeting our challenges & opportunities
Challenge / Opportunity Azure + PCF
Global Opportunities Azure’s Huge Global Footpr...
Learn More. Stay Connected.
Merrill is hiring awesome people!
To apply, email: Tami.Gold@merrillcorp.com
Related Session
K...
Upcoming SlideShare
Loading in …5
×

Adopting Azure, Cloud Foundry and Microservice Architecture at Merrill Corporation

1,332 views

Published on

SpringOne Platform 2016
Speakers: Thomas Fredell; Chief Product Officer, Merrill & Ashish Pagey; Architecture Team Lead, Merrill

Come learn how Merrill Corporation is solving real business challenges and transforming their business directly from Merill's product and architecture leaders. By partnering with Pivotal and Microsoft Merill can rapidly deliver software as Java microservices deployed to Pivotal Cloud Foundry running on Microsoft Azure.

Published in: Technology
  • Be the first to comment

Adopting Azure, Cloud Foundry and Microservice Architecture at Merrill Corporation

  1. 1. Customer Success: Java Micro- Services with Pivotal Cloud Foundry on Azure Thomas Fredell (Chief Product Officer) Ashish Pagey (Architect) Merrill Corporation
  2. 2. Our Journey 2 • Who is Merrill • Business Challenges & Opportunities • Conceptual Architecture • Why PCF? • Why Azure? • Top Learnings & Takeaways • Thank You!
  3. 3. Thomas Fredell, Chief Product Officer 3
  4. 4. Ashish Pagey, Architect 4
  5. 5. Who is Merrill Corporation? 5
  6. 6. About 6  50 year history! Now, SaaS + Service!  Financial Transactions & Reporting  Marketing & Communications for Regulated Industry  Customer Content & Collaboration pssst We’re looking for development, DevOps and product management talent! Are you awesome? Contact us at Tami.Gold@MerrillCorp.com
  7. 7. Quick Poll 7  Who’s using Azure?  Who’s doing Microservices?  Who’s using PCF?  Who is using PCF on Azure?
  8. 8. Our Journey 8 • Who is Merrill • Business Challenges & Opportunities • Conceptual Architecture • Why PCF? • Why Azure? • Top Learnings & Takeaways • Thank You!
  9. 9. Global Opportunities 9 Customers everywhere! Data residency requirements…
  10. 10. Security and Compliance Needs 10 Security and compliance essential… architected in from the beginning
  11. 11. Need to Move Fast 11 Competition moves fast. How do you disrupt, not get disrupted?
  12. 12. Old, monolithic systems 12 Prior platform – Monolithic! Hard / Slow to change
  13. 13. Need for Coaching & Support 13 Managing change is hard. Good coaching and support is critical to ease the way.
  14. 14. Our Journey 14 • Who is Merrill • Business Challenges & Opportunities • Conceptual Architecture • Why PCF? • Why Azure? • Top Learnings & Takeaways • Thank You!
  15. 15. App1 Moving from… 15 POJO Beans App2 POJO Beans App3… POJO Beans
  16. 16. Moving to… 16 REST Service APIs Service Container Pivotal Cloud Foundry Infrastructure (Azure IaaS) 3rd Party tools) Micro-servicesInfrastructure Search Content Metadata Users … App UseCaseUI Use Case A Use Case B  Service Discovery  Service Configuration  Routing  Load Balancing  Service Composition  Container support  Fault monitoring  Messaging  Language support  Minimize lock-in
  17. 17. Our Journey 17 • Who is Merrill • Business Challenges & Opportunities • Conceptual Architecture • Why PCF? • Why Azure? • Top Learnings & Takeaways • Thank You!
  18. 18. POC Goals and Success Criteria 18 Pivotal Use Case Number Pivotal Use Case Merrill Success Criteria Pivotal reference architecture Merrill microservice artifacts Durham environment ready to Durham demonstration of Pivotal components complete Durham demonstration of Merrill Azure environment ready to Azure demonstration of Pivotal components complete Azure demonstration of Merrill components complete Install PCF on Azure na na na na na na na A.1 Deploy a Microservice 1.1, 1.2, 1.3, 3.1, 10.1 na na signed off: Franck/DS26 Feb 16 A.2 Spring Cloud Configuration Server 4.2 na na signed off: Franck/DS26 Feb 16 A.3 Spring Cloud Service Registry 4.1 signed off: Franck/DS26 Feb 16 A.4 Services calls with Spring Cloud Circuit Breaker 4.1 na na signed off: Franck/DS26 Feb 16 A.5 API Gateway Security Patterns 9 na na na na na na na na A.6 Zero Downtime Service Upgrades 8.1, 8.2 signed off: Franck/DS/Ashish26 Feb 16 A.7 Eventing/Messaging between Services 2.1, 2.2 na na na signed off: Franck/DS26 Feb 16 A.8 High Availability of Applications 6 signed off: Jeremiah22 Feb 16 B.1 Monitoring Metrics and Alerts 10 na na na na na na na B.2 Application Log Management 10.1 na na na na na na signed off: Franck/Ashish2 Mar 16 B.3 Organizations and Spaces (Environments) na na na na na na signed off: Ashish22 Feb 16 B.4 Auto Scaling 5 na na na na na signed off: Franck/Ashish2 Mar 16 na B.5 High Availability of PCF Services 7.1 na na na na na signed off: Darren, Ashish, Jeremiah24 Feb 16 na B.6 High Availability of Underlying PCF VMs 7 na na na na na signed off: Darren, Ashish, Jeremiah24 Feb 16 na B.7 Patching the Platform with no Downtime 13.0, 13.1 na na signed off: Franck/Ashish2 Mar 16 na na na na B.8 Understanding Pivotal's Patching Process 13.0, 13.2 na na na na na na na na B.9 The Plan Beyond the POC 14 na na na na na na na na C.1 Deploying Apps from IntelliJ 11 na na na na na na na na C.2 Locally Debug Services 11.1 na na na na na na na na C.3 Continuous Deployment with Jenkins 8 na 3/3/2016 PCF on Azure Cloud Native Apps/Services Operational Use Cases Development Tooling Composite A Composite B Core C Core D Azure PaaS Core E Core F
  19. 19. Of many options, PCF won because… 19 Azure IaaS Pivotal Cloud Foundry Spring Boot, Spring Cloud Azure Service Fabric Spring Boot, ++ Docker Spring Boot,++  Best coverage of our key requirements  Best Developer experience  Scalability  PCF Agile Expertise & DNA  Integration with Application Frameworks: Spring Boot & Spring cloud
  20. 20. Our Journey to Cloud Native 20 Research, comparison due diligence 4 week technical PoC PoC findings, decision, procurement DOJO, Implementation
  21. 21. Our Journey 21 • Who is Merrill • Business Challenges & Opportunities • Conceptual Architecture • Why PCF? • Why Azure? • Top Learnings & Takeaways • Thank You!
  22. 22. Azure Security & Compliance 22
  23. 23. Azure Global Footprint 23 26 regions! With 8 to come.
  24. 24. 24 ASP.NET 5 Preview Azure SDK 2.5.1 Team Foundation Server 2015 preview Azure Machine Learning GA Azure HDInsight for Linux Pub Preview Azure HDInsight Support for Hadoop 2.6 pub preview Azure SQL Database security feature - Data Masking pub preview Azure SQL Database security features - Encryption Azure SQL Database security features - Row Level security Azure AD: API for SIEM Microsoft Intune monthly updates Remote Desktop Client for Windows Phone 8.1 Azure App Service Azure CDN Integration Azure Speed of Innovation
  25. 25. Our Journey 25 • Who is Merrill • Business Challenges & Opportunities • Conceptual Architecture • Why PCF? • Why Azure? • Top Learnings & Takeaways • Thank You!
  26. 26. Lessons on the way to production… 26  Learning curve is steep... plan to get help!  Organization changes to both people and process will be necessary to fully leverage the platform  Application re-architecture is imperative; running traditional 3- tier app on PCF won’t leverage all capabilities  Start with a clean slate; don’t replicate or map on-premise network topology to cloud
  27. 27. Our current state by the numbers 27 Scrum teams using PCF6Spaces in one PCF domain2 Time to deploy new app <1d
  28. 28. Meeting our challenges & opportunities Challenge / Opportunity Azure + PCF Global Opportunities Azure’s Huge Global Footprint Security and Compliance Azure Compliance The Need for Speed Pivotal Innovation Methodology Monolithic Systems Pivotal Architecture Approach Coaching and Support Microsoft Consulting and Pivotal Dojo 28
  29. 29. Learn More. Stay Connected. Merrill is hiring awesome people! To apply, email: Tami.Gold@merrillcorp.com Related Session Keep calm and cf push on Azure 12:10 PM Wednesday @springcentral spring.io/blog @pivotal pivotal.io/blog @pivotalcf http://engineering.pivotal.io

×