15. > Stay Connected.
Email: olaf.gradin@fiserv.com Twitter: @gradinDotCom
Catch another Fiserv story tomorrow before lunch:
From Inception to Production – Migrating .NET Apps to PCF
#springone@s1p
Editor's Notes
Principal Platform Architect, Fiserv – 14 years
manages and moves money and information for millions, $75 TN per year
Fintech leader, conservative industry –
doesn’t like making drastic changes to the technology that could risk those 75 TN
two such drastic changes I had the pleasure of being a lead designer on…
propose a platform
Fundamental changes – what changes?
Cohesive, centralized mgmt.
commodity pricing
faster time to market
2 years
Persistent factor
Devs looking at PCF
faster time to market
engineers needed PaaS
6 months
Taking risks…
No .NET
Enabled flexibility
Provided systematic improvements
Conservative industry
Heavy ITIL controls
Enter DevOps
Listen to their advice
Pivotal modeled great behavior – went to Palo Alto, CA
engaged our developers
but follow your business case
Microsoft reference architecture
Experience revolved around clients more than servers
We built for availability over capacity
tea ceremony about servitude to guests
A platform does nothing without a customer
found willing partners
PCF began with developer interest
work together to deliver platform and capabilities
cloud enablement team
Both cases resulted in partners, roadmap guidance
Windows enterprise mgmt. good
not intended to manage servers (SCCM, ADS)
Concourse Pipelines in PaaS era is creativity incarnate
But know your limits;
value of PCF was marketplace, but we learned not to go all in on those
Automate everything; PCF embodied this ideal, but Windows required a lot of creativity
Even with automation, there is still struggle in manual efforts and arcane practices
PaaS Brought about a new way of thinking
Revolutionary automation improvements with .NET platform
despite that, required manual intervention
new datacenters
major releases
disaster recovery
resource capacity adds
IaC represents a program to deliver our platform to a variety of unique environments while remaining agnostic to those differences
Our first deployment of PCF was on grossly different hardware from the first production deployment. It made -0- difference
Today, 6 major releases and countless minors against 8 foundations in 4 datacenters
Idempotent, always clean, always consistent
The mark of an excellent tea host and ceremony is the attention to detail.
The tea ceremony can be an analogy of how a process lends itself to a system. A system built for a community.
We have a community of engineers, operators, and developers; providers and customer, working together, and as long as the providers are keeping their customer’s tenets in mind, then you’ll have the platforms of your dreams for decades to come!