Pivotal cloud cache for .net microservices
Download as PPTX, PDF0 likes61 views
Pivotal is a key player in cloud-native .NET development, sponsoring the .NET Foundation and maintaining the Steeltoe.io framework for building microservices. The document outlines the features and advantages of Pivotal Cloud Cache (PCC), highlighting its automated provisioning, high availability, and fault tolerance, which are crucial for modern application architectures. It also discusses caching design patterns suitable for .NET microservices and mentions the Apache Geode Summit, focusing on advancing expertise in distributed caching solutions.
Pivotal cloud cache for .net microservices
- 1. © Copyright 2019 Pivotal Software, Inc. All rights Reserved. Nikhil Chandrappa Senior Data Engineer @ Pivotal Pivotal Cloud Cache For .NET Microservices
- 2. Pivotal is a leader in cloud native .NET How is Pivotal a part of it? .Net Foundation As a corporate sponsor Pivotal sits on the advisory council, collaborates closely with the .NET engineering team, and helps grow the .NET community. Steeltoe.io An application framework that provides libraries for .NET developers to build cloud-native applications and microservices. Pivotal maintains the project, and donated it to the .NET Foundation in 2017. Automation with no opinions Whether you use TFS, Azure DevOps, Jenkins, Octopus or any other pipeline tool; developers can easily push .NET apps to the platform. Windows Server OS Utilizing Microsoft Server OS native containerization, PASW enhances an already established technology.
- 3. Cloud Native Design - 12 factors Codebase One codebase tracked in revision control, many deploys Dependencies Explicitly declare and isolate dependencies Configuration Store config in the environment Backing services Treat backing services as attached resources Build, release, run Strictly separate build and run stages Processes Execute the app as one or more stateless processes Port Binding Export services via ports Concurrency Scale out via the process model Disposability Maximize robustness with fast startup and graceful shutdown Dev/Prod Parity Keep dev to prod as close as possible Logs Treat logs as event streams Admin Processes Run admin and management tasks as one-off processes Build
- 4. Cloud Native Design: Processes Execute the app as one or more stateless processes Build Stateless Processes Stateful Backing Services
- 5. Cloud Native Design: Backing Services Treat backing services as attached resources .NET Microservice Attached Resources
- 6. Caching is a Vital Part of Modern Application Architecture
- 7. Internet Scale Caching @ Netflix 7 “The Netflix customer experience relies heavily on caches to provide a high- volume, low latency, globally available data layer that backs our stateless services. Throughout a typical customer experience, from sitting down on the couch through playing a movie, caches play a role in every interaction.” #CachesEverywhere http://bit.ly/netflix-caching-2016
- 8. Internet Scale Caching @ Netflix
- 9. Internet Scale Caching @ Netflix
- 10. ➔VMs disappear ➔Availability Zones fail ➔Network lossy ➔Failures happen, minimize impact ➔Enterprise readiness ➔Cloud portability Motivation for Cloud Native Caching
- 11. ➔Distributed In-Memory Cache Based on Pivotal GemFire (Apache Geode) and optimized for PCF Apps. ➔Automated Provisioning and Management Customize service plan, on demand service broker, monitoring, failure recovery, and software updates with zero downtime. ➔High Availability and Linear Scalability ➔Fault Tolerant, No Single Point of Failure ➔Disk based Persistence ➔WAN replication between PCF foundations ➔PCF AZ aware! Pivotal Cloud Cache (PCC)
- 12. Self Service for Developer Productivity
- 13. Service-Service for Devs: Create PCC Instance ● Pivotal Cloud Cache is listed in PCF Marketplace. ● Developer can create a PCC cluster within the available Service Plans and Quota limits set by the Operator. ● Create Service Keys to access PCC cluster.
- 14. Binding Application to PCC Service
- 15. Pivotal Cloud Cache - Core Features
- 16. PCC Topology 2 Cache Server Cache Server Cache Server Locator 1 1 2 33 1 .NET Client Connection Pool 54.209.251.110 54.209.251.111 54.209.251.112 Locator Cache Server 2 54.209.251.113 PCF AZ 1 PCF AZ 2 Cache Server 3 1 54.209.251.112 Locator Cache Server 2 54.209.251.113 PCF AZ 3 ● Cluster Spanning Multiple PCF AZs ● PCC Native Redundancy prevent data loss
- 17. Pivotal Cloud Cache HA and Fault Tolerance Failing data copies are replaced transparently Data is replicated to other clusters and sites (WAN) Split Brain Detection is enabled Client and cluster disconnections are handled gracefully Data is persisted on local disk for ultimate durability “split brain”
- 18. Secure By Default Data security has to be baked in to everything we do ● Access Management ○ UAA serves as OAuth2 provider ● Credential management ○ CredHub for managing certificates ● Encryption of data in motion ○ Developers can opt into TLS Encryption, which is integrated with the platform ● Encryption of data at rest ○ Partner with external vendors to provide disk encryption
- 19. Cluster Scaling Out cf update-service pcc-dev-cluster -c '{"num_servers": 6}'
- 20. Caching Design Patterns for .NET Microservices
- 21. Design Pattern: Look-Aside Cache Cache data in the memory for frequent visit
- 22. Design Pattern: Front-ending a RDBMS (In-line cache) ● Cache provides applications and users with a low-latency, high throughput serving layer ● Asynchronous write-behind to disk by deploying custom code as AsyncEventListener and CacheLoader ● More economical than trying to increase the performance of the RDBMS ● Same pattern applies to front ending a mainframe Fast KV Store front-ending RDBMS 1000s of transactions per second 100s of transactions per second
- 23. Design Pattern: Session State Cache
- 24. Design Pattern: Foundation Replication
- 25. Modern Application Architectures Need Caching ● Cloud infrastructures are ephemeral. A highly available cache can keep serving data and protect against data loss even when the infrastructure fails ● Cloud infrastructures are elastic. An elastic cache like PCC can adjust to the needs of the application(s) ● Distributed application architectures are highly subject network latencies. A caching layer can reduce the dependence on the network ● Pivotal Cloud Cache is purpose built for the Pivotal Platform and it provides an easy to set up, configure, integrate, and deploy caching service PCC’s versatility makes it a great choice for various .NET microservices patterns and use cases
- 26. The Highest Concentration of Geode Expertise in One Place Apache Geode Summit 2019 Learn from practitioners, committers and data architects 12 Geode sessions ● Monday Geode Summit (Oct 7, 1-6PM): 8 consecutive Geode- only sessions ● Conference breakout sessions (Oct 8-10): 4 additional Geode sessions Registration options: full conference or Monday Geode Summit only October 7–10, 2019 Austin Convention Center Discount Code S1P200_JMirani for $200 off a full pass Register Now For the latest sessions list: Use the ‘Geode’ filter on the conference sessions page
- 27. Transforming how the world builds software © Copyright 2019 Pivotal Software, Inc. All rights Reserved.