Pre-Con Ed: CA API Gateway: How to Deploy Your Gateway Across Multiple Environments and Architectures

World®
’16
Gateway Deployment Scenarios
and Best Practices
Jamie Williams
Senior Software Engineer
CA Technologies
DO3X48E
DEVOPS

2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of
warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
For Informational Purposes Only
Terms of this Presentation

Abstract
In this session, we will look at enterprise scenarios of deploying your CA API Gateway. We will
cover on-premises, public cloud, and PaaS/private cloud deployment, and the different form
factors available for each.
The comparison of the various models and discussion of real world examples will help the
attendee understand the pros and cons of each. We will also learn some best practices in
implementing such models.
Jamie
Williams
CA Technologies
Senior Software
Engineer

Agenda
INTRODUCTION TO THE CA API GATEWAY
GATEWAY DEPLOYMENT SCENARIOS
CHOOSING A MODEL
1
2
3
REAL WORLD EXAMPLES4
BEST PRACTICES5

CA API Gateway
§ Enables enterprises to securely expose services to external client
applications as APIs.
§ Provides runtime control over service-level authentication, authorization,
key management, credentialing, integrity, confidentiality, schema
validation, content inspection, data transformation, threat protection,
routing, protocol switching, SLA enforcement, logging, and other
functions.
§ Acts as an integration point for extending existing security and message
infrastructure to APIs.

CA API Gateway
CA API Gateway
Enterprise
Directory
API Server
Security
Boundary

Gateway Deployment Scenarios
§ On-Premises
§ Public Cloud
§ PaaS/Private Cloud
§ Hybrid

On-Premises Deployment
§ Hardware Appliance
§ Virtual Appliance
§ Docker Container
§ Software

On-Premises Deployment
Virtual or Hardware
Appliance

Form Factor Options for On-Premises Deployment
FORM FACTOR PROS CONS
Hardware • Best performance
• Best physical security
• Purpose built appliance
• Thales nCipher HSM
• Requires rack space
• No hardware migration
• Disaster recovery
Virtual Appliance • Mobility
• Scalability
• Ease of deployment
• Monitoring and management tooling
• Reduced performance due to overhead
• Potential resource contention
• ESX host maintenance
Docker • Mobility
• Scalability
• Simple upgrade story
• Migration, monitoring and management
tooling/UI not as developed as VMware
• Emergent technology

Public Cloud Deployment
§ AMI
§ Azure
§ Other hosting

APIs
AMI, Azure,
Docker, etc.

Form Factor Options for Public Cloud Deployment
FORM FACTOR PROS CONS
AMI • Many Gateway-friendly services
• Good monitoring
• Auto-scaling
• RDS
• Mature platform
• Expensive
Azure • Cheaper than AMI
• Good monitoring
• Auto-scaling
• Relatively few services
• Windows-centric

PaaS/Private Cloud Deployment
§ Cloud Foundry
§ OpenShift
§ Other PaaS

PaaS/Private Cloud Deployment
Docker Container

Pros and Cons of PaaS/Private Cloud
PROS CONS
• Mobility
• Scalability
• Auto-scaling
• Simple automated upgrade story
• Some have good deployment, management tooling
• Can be very opinionated/presecriptive
• Often minimal or no services
• Can have expensive licenses and support contracts
• Some have limited or unfriendly tooling

Hybrid Deployment
§ Combination of other scenarios

Hybrid Deployment Example
On-premises hardware with
Amazon Web Services
AMI
Hardware
Appliance

Choosing a Model
§ Performance
§ Latency
§ Uptime
§ Governance
§ Time to Market
What are your non-functional requirements?

Choosing a Model
§ Size of data centre
§ Budget, capital vs operational
§ Departmental silos
§ Will your corporate limitations be changing soon?
§ Might you change your mind about where a service is
deployed?
What are your corporate limitations?

Real World Examples
§ On-premises hardware for TLS, AWS for non-TLS (HTTP) traffic
§ On-premises VMware, auto-scaling in AWS for peak traffic
§ Federated Gateway clusters in separate IT infrastructures
§ Azure for Microsoft ecosystem support
CA customers’ Gateway deployment scenarios

Best Practices
§ Load Balancing
§ VMware best practice
§ Performance testing

Load Balancing
§ Failover
§ High availability
§ Balance load
§ Reduce overloading of individual nodes
Why implement load balancing?

Load Balancing
§ Choose Affinity and Balancing algorithms appropriate to the
user case
§ Configure timeouts for both Load Balancer and Gateway
routing appropriate to system behaviour at business level
§ Consider SSL Termination
Real world guidance

VMware Best Practices
§ Ensure Gateway VMs have reserved memory and processors
§ Disable DRS or configure Node Affinity for Gateway VMs on
hypervisor clusters
§ Do not run Gateway VMs on an overcommitted host
§ Do not confuse hyperthreaded cores for physical cores when
allocating processors
§ Size Gateway VMs suitably for the user case
Consistent performance requires consistent resources

Performance Testing
§ Network subsystems and back-end latency
§ Connection timeout vs Response timeout
§ Concurrency & Keepalive
§ Synchronization of testing
§ Long lived vs Short lived requests
§ Load balancing, error cases, and longer lasting effects
Confounding factors to be mindful of

Recommended Sessions
SESSION # TITLE DATE/TIME
DO3X47EV
CA API Gateway: Developing Custom Policies to Secure
Your Enterprise APIs
11/14/2016 at 10:00 am
DO3X49E
CA API Gateway: Managing and migrating Gateway
policies with the Gateway Migration Utility
11/14/2016 at 11:00 am
DO3X52E
CA Mobile App Services: Build the Powerful Mobile App
Every Enterprise Needs in Under an Hour
11/14/2016 at 1:00 pm

Questions?

Thank you.
Stay connected at communities.ca.com

@CAWORLD #CAWORLD © 2016 CA. All RIGHTS RESERVED.31 @CAWORLD #CAWORLD
DevOps – API Management and
Application Development
For more information on DevOps – API Management and
Application Development, please visit: http://cainc.to/DL8ozQ

Pre-Con Ed: CA API Gateway: How to Deploy Your Gateway Across Multiple Environments and Architectures

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (20)

Similaire à Pre-Con Ed: CA API Gateway: How to Deploy Your Gateway Across Multiple Environments and Architectures

Similaire à Pre-Con Ed: CA API Gateway: How to Deploy Your Gateway Across Multiple Environments and Architectures (20)

Plus de CA Technologies

Plus de CA Technologies (20)

Dernier

Dernier (20)

Pre-Con Ed: CA API Gateway: How to Deploy Your Gateway Across Multiple Environments and Architectures