Service mesh or

API management?
Deploy a comprehensive service architecture for your organization
See what’s inside

About this e-book

Chapter 1
Understand APIs and microservices

Chapter 2
Identify traffic direction and domain boundaries

Chapter 3
Deploy API management and service mesh solutions

Chapter 4
Build a complete service architecture with Red Hat

Chapter 5
Discover success across industries

Ready to get started?

Service mesh or API management? | Contents

About this e-book

Our increasingly digital world requires organizations to adapt their business and IT strategies, including application development and
deployment. Application programming interfaces (APIs) and microservices can help your organization modernize your applications to
improve speed, agility, and efficiency. In fact, 58% of organizations are adding a layer of APIs to modernize their applications.1 Mean-
while, 61% of organizations have used microservices for more than one year, and 28% have used them for more than three years.2

Even so, building a service management architecture that optimizes use of APIs and microservices can be confusing. Many organiza-
tions consider either API management or service mesh solutions but may not realize that these two technologies work best together.

This e-book provides essential knowledge and expert guidance for building an effective service management architecture that encom-
passes both API management and service mesh solutions.

Building a comprehensive service management architecture can help your organization:

Accelerate new service and Speed application launch Deliver real-time, data-based
API development by 2x.3 and update cycles.4 services to users.5

1 F5 Networks. “State of Application Strategy Report 2021,” March 2021.

2 Loukides, Mike and Steve Swoyer. “Microservices Adoption in 2020.” O’Reilly, 15 July 2020.
3 Red Hat case study. “Amsterdam Airport Schiphol builds agile cloud with Red Hat OpenShift,” 3 August 2017.
4 Red Hat case study. “Leading UAE bank builds competitive private cloud with Red Hat,” 1 May 2019.
5 Red Hat case study. “Uruguayan city builds apps with APIs and Red Hat OpenShift,” 22 January 2020.

Service mesh or API management? | 1

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Understand APIs and microservices

Many organizations want to move to API-centric and microservices-based IT architectures to improve speed, agility, and efficiency.
In fact, many organizations already use APIs to interact with their customers, partners, and other external users. Consistent, effective
management of these interfaces and services is critical for successful deployment and use.

However, determining which approaches and tools to use within your organization can be confusing. Most organizations look for either
an API management or a service mesh solution to accomplish this. These solutions have many things in common, but also many differ-
ences. While many organizations approach this as an either-or decision, these two technologies are actually complementary and work
together to deliver a complete service management architecture.

The following chapters discuss the similarities and differences between API management and service mesh approaches, when to
choose one over the other, and how to set up a comprehensive service management architecture using both solutions together.

API management Service mesh

solutions solutions

Rate limits
API contracts Observability

Monetization Resiliency
Policies

Chaos testing
Partner ecosystem

Security

Documentation Traffic routing

Service mesh or API management? | 2

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

What are APIs and microservices?

Microservices and APIs are at the core of cloud-native application development — an approach for rapidly developing innovative
application components to meet new and changing business needs.

APIs Microservices
APIs provide an interface into your business capabilities, Microservices deliver specific sets of functions and
allowing consumers to access services in a controlled responsibilities as part of a larger application or business
manner. They consist of tools, definitions, and protocols process. They are an architectural approach to building
for integrating application software and services. APIs applications. As a deployment pattern, microservices
let your products and services communicate with other can be combined and orchestrated to create complete
products and services without needing to build new con- applications and processes. They are distributed and
nectivity infrastructure. They can be created for internal, loosely coupled, so changes to one microservice will not
partner, or even public use, allowing others to develop affect other microservices or break the entire application.
applications that incorporate your services and providing Additionally, each microservice has its own life cycle
additional revenue streams. As a business-focused con- and can be managed and scaled independently. Finally,
struct, APIs serve as contracts between service providers microservices can be delivered either through a service
and service consumers. mesh or via an API.

Business services - API connections

Mobile Partner Website Affiliate Mobile Partner Website Affiliate

API API API API API API API API

Fulfillment services - Microservices architecture

Service mesh or API management? | 3

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

What is API management?

API management refers to the processes for exposing, controlling, and analyzing the interfaces that connect applications and data
across your enterprise and across clouds. It allows organizations that create APIs or use others’ APIs to monitor activity and ensure that
both developer and application needs are met. Managing APIs also helps you make sure your interfaces are used in compliance with the
appropriate corporate, regulatory, and security policies.

API management encompasses everything needed to use APIs in a business strategy:

► Monetization

► API consumer management

► Ecosystem creation and administration

► Product development

► Partner outreach and onboarding

Externally available business services

Mobile Partner Website Affiliate Mobile Partner Website Affiliate

API management

Internal fulfillment services

Service mesh or API management? | 4

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

How does API management work?

API management centralizes control of your API program from analytics and access control to monetization and developer workflows.
At a minimum, API management solutions should provide:

► Authentication. Create and check user keys and login credentials.

► Authorization. Authorize access and use via your existing ID management systems.

► Traffic management. Throttle and rate limit API use to protect your interfaces and services from abuse by consumers and some
denial of service (DoS) attacks.

► Security. Encrypt communications and manage security certificates.

Many API management solutions also provide:

► Developer portals.

► API life-cycle management.

► Analytics.

► Support for API monetization.

Comprehensive API management solutions simplify discovery and documentation of your interfaces and assets, provide flexible access
controls for different users, and deliver straightforward consumption billing and invoicing.

Who uses API management?

API management is ideal for teams that want to deliver services beyond their domain to other internal groups or external users.

Service mesh or API management? | 5

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

What is a service mesh?

Service meshes provide connectivity between application services and add capabilities like resiliency, security, observability, routing
control, and insights. They control how different parts of an application share data with one another. Unlike API management, a service
mesh is a dedicated infrastructure layer that runs alongside applications. This visible infrastructure layer can document how different
parts of applications interact, making it easier to improve communication and avoid application downtime.

Service meshes route requests from one service to the next, optimizing how all the moving parts work together. Within cloud-native
application development approaches, they allow you to assemble large numbers of discrete services into functional applications.
Service meshes also simplify development to increase productivity, speed, and quality:

► Distributed request tracing provides visibility into service connections, streamlining issue discovery and troubleshooting.

► Automatic request rerouting can avoid failed services, making applications more resilient.

► Performance metrics help you optimize communication in your runtime environments and improve your user experience.

Service mesh implementation is transparent to developers, allowing them to focus on creating valuable applications and features rather
than rebuilding or connecting standard underlying services like security and routing.

Service mesh

Microservice Sidecar

Service mesh or API management? | 6

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

How do service meshes work?

Service meshes take the logic and policies governing service-to-service communication out of individual services and abstract it to a
layer of infrastructure. To do this, service meshes are built into applications as an array of network proxies.

Requests are routed between microservices through these proxies. For this reason, the individual proxies that make up a service mesh
are sometimes called sidecars, since they run alongside each service rather than within them. Taken together, these proxies — decoupled
from each service — form a mesh network. As a result, they can be updated and changed independently of the services they support and
connect. Common proxy policies and functions include:

► Authentication.

► Authorization.

► Encryption.

► Security.

► Traffic management.

Service mesh infrastructure layers use control planes and data planes to manage services. The control plane allows you to define rules
and policies to govern your services. The data plane contains the actual proxies and applies the appropriate rules and policies to your
services at runtime.

Who uses service meshes?

Service meshes are ideal for development teams that need to access services through network interfaces and protocols.

Service mesh or API management? | 7

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Identify traffic direction

and domain boundaries

Identifying the direction of traffic between your services and interfaces is the first step in deciding whether to deploy an API manage-
ment or service mesh solution.

North-south traffic East-west traffic

North-south traffic patterns connect services and applica- East-west traffic patterns link individual microservices
tions with external clients. This traffic typically: to form complete applications. This traffic usually:

► Involves connections to service consumers beyond ► Involves multistage routing to orchestrate services
your enterprise boundary. within your enterprise boundary.

► Requires security, policy enforcement, access control, ► Requires mutual security and authorization controls
and analytics capabilities. and tracing and observability functions.

► Is governed by formal contracts between service ► Is governed by informal contracts between service
providers and service consumers. providers and service consumers, if needed.

► Scales to tens of service connection points. ► Scales to thousands of service interfaces.

Enterprise boundary

Client Service Service Service

Gateway Service Service

Enterprise boundary
Service Service Service

Service Service Service Service Service

Based on these key characteristics, north-south traffic patterns align well with the capabilities of API management solutions,
while east-west traffic patterns correspond more closely with service mesh solutions.

Service mesh or API management? | 8

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Introducing domain boundaries

Traffic direction provides a straightforward guide for when to choose API management or service mesh solutions. However, most orga-
nizations are not so simple. Typical organizations contain multiple groups that create and manage their own services and interact with
other teams and external parties.

Domain boundaries can help you divide your organization into smaller, more manageable areas. Much as your enterprise boundary
denotes the perimeter of your overall organization, domain boundaries designate the perimeters of groups within your organization.

Enterprise boundary

Application Application Application

Application Application Application

Domain boundary Intradomain connection Interdomain connection

Service mesh or API management? | 9

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Interdomain versus intradomain traffic

The same north-south and east-west traffic patterns that occur in relation to your enterprise boundary also apply to domain boundar-
ies within your organization. As a result, you should generally choose API management for interdomain traffic and service meshes for
intradomain traffic.

Interdomain traffic Intradomain traffic

Interdomain traffic crosses domain or enterprise Intradomain traffic stays within domain and enterprise
boundaries to connect services with consumers boundaries to link individual microservices. Intradomain
beyond your group or team. Interdomain traffic traffic typically conforms to east-west traffic patterns:
follows north-south traffic patterns:
► Non-hierarchical 1:1 connection structures
► Hierarchical 1:N connection structures
► Service providers and consumers within same team
► Separate service providers and service consumers
► Authentication required
► Authorization and authentication required
► Implicit or informal contracts, if any
► Formal use contracts needed
► Internal documentation within code
► Guided service discovery, accessible developer
portal, and formal documentation

Service Service Service Service

Service Service

Service Service Service

Service Service Service

Service Service Service Service Service

Service mesh or API management? | 10

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Deploy API management

and service mesh solutions

API management and service meshes can be used together to create a comprehensive
service management architecture within your organization. Get help from Red Hat
Red Hat can help you assess your
Use API management for north-south traffic patterns that
infrastructure and create a plan for
cross domain or enterprise boundaries and service meshes for moving forward. Our experts work
east-west traffic patterns that stay within those boundaries. with your organization to achieve
your goals using an integrated
This advice can help you choose the most efficient path forward in most circumstances.
approach that brings together people,
Even so, there are exceptions to this guidance. For example, your organization may
process, and technology.
already use platforms, technologies, or runtimes that are incompatible with service
mesh solutions, making it significantly easier to deploy API management for some east-
west traffic patterns.
Learn more
Be sure to consider your existing infrastructure, business goals, and available time
frame when planning your API management and service mesh solution strategy.

API consumers

Enterprise boundary

API product

Application Application

Domain boundary Intradomain/east-west traffic Interdomain/north-south traffic

Service mesh or API management? | 11

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Maximize your value through integration

The most effective service management architectures combine API management and service meshes to deliver the right capabilities
for the right traffic at the right time. When building your service management architecture, deploy API management and service meshes
according to these recommendations.

API management Service meshes

Use API management to administer relationships between Deploy service meshes when you need advanced traffic
exposed services and consumers. API management is control, security, resilience, and observability for micros-
best for: ervices and cloud-native applications. Service meshes are
best for:
► North-south traffic patterns.
► East-west traffic patterns.
► Interdomain traffic.
► Intradomain traffic.
► API-led development situations in which not all
platforms can access a service mesh. Avoid using service meshes in situations in which service
consumers require formal documentation, billing, applica-
In general, API management is not appropriate for tion use plans, and third-party authorization.
connecting services or microservices that are part
of the same business domain.

Service mesh or API management? | 12

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Find the right solutions for your organization

There are many API management and service mesh solutions available. Choosing the right solutions for your organization can signifi-
cantly impact the efficiency and value of your service management architecture.

API management solutions Service mesh solutions

Look for an API management solution that goes beyond Look for a service mesh solution that provides everything
a simple gateway and access controls to provide the you need to build and operate a microservices architecture:
functionality needed to implement a complete API strategy:
► DevOps tools. Microservices are a key element in
► Monetization. Monetization capabilities help you turn DevOps approaches. Adopt DevOps more easily with
your services into revenue. Create metric-based use solutions that include development kits, continuous
contracts for accessing your APIs and offer multiple integration/continuous deployment (CI/CD) tools, and
access and service level tiers for your customers. flexible automation capabilities.

► Developer portal options. Developer portals typically ► Developer support. Developers are most productive
provide API documentation and onboarding processes. when they have the right tools for their job. Offer
Help developers find and use your APIs more easily. multiple development languages, runtimes, and
databases to help your developers innovate faster.
► API life-cycle management. Like all IT assets,
APIs undergo multiple life-cycle stages. Simplify ► Cross-infrastructure support. Hybrid infrastructures
management of your APIs from initial design, through are becoming the norm for innovative organizations.
implementation, to retirement. Deploy your microservices across physical, virtualized,
and all types of cloud infrastructure to optimize
► Analytics. Analytics help you understand what’s going microservice performance, security, and costs.
on with your APIs. Learn which consumers or apps are
calling which APIs and how often, and gain insight into ► Microservice life-cycle management. Microservice
how many APIs have failed and why. management is critical to ensure cloud-native
applications run predictably and reliably. Independently
► Policies. Policies help you ensure your APIs are used scale microservices, control configurations, enforce
and secured appropriately. Define and enforce policies routing and security rules, and understand how traffic
for traffic management, security, and use to keep your flows between your services in near-real time.
API program operating in compliance.

Service mesh or API management? | 13

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Build a complete service

architecture with Red Hat

Red Hat offers integrated API management, service mesh, and infrastructure platform products to help you build a comprehensive
service management architecture. This architecture is divided into functional areas, providing targeted capabilities for multiple stake-
holders. We build each product in the architecture with these stakeholders in mind to deliver an efficient, user-friendly experience.

Red Hat 3scale API Management

Service Monetization Developer portal Analytics Authentication Authorization
owner

Traditional Microservices architecture

application
Application
architecture developer

Application
developer Red Hat OpenShift
Service Mesh
DevOps
Security Observability Traffic control Resiliency team

Red Hat OpenShift

Service discovery Resource management Monitoring Release management
Infrastructure
owner Security Configuration Elasticity Logging Load balancing Resiliency

Service mesh or API management? | 14

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Integrated products for service management architectures

Infrastructure foundation API management Service mesh

Red Hat can help you address the Red Hat offers modular, lightweight, Red Hat includes service mesh
inherent difficulties in managing and and comprehensive API management capabilities within Red Hat OpenShift,
supporting varied applications, ser- solutions that are open source, built on installed via a Red Hat OpenShift
vices, APIs, and microservices through open standards, and available on-site operator for simpler deployment.
the use of a container platform. or in the cloud.
Based on a set of open source
Red Hat® OpenShift® is a hybrid Red Hat 3scale API Management projects, Red Hat OpenShift Service
cloud, enterprise Kubernetes platform is an API management platform that Mesh provides a uniform way to
that helps IT development and oper- makes it easy to share, secure, dis- connect, manage, and observe micros-
ations teams work together to deliver tribute, control, and monetize your ervices-based applications. It includes:
and manage microservices-based interfaces. It includes everything
applications. It supports containerized, you need to implement an effective ► Istio, an open source project for
legacy, and cloud-native applications API program: integrating and managing traffic
and provides everything you need to between services.
build a microservices foundation: ► API traffic control
► Jaeger, an open, distributed
► Built-in infrastructure security ► API program management tracing system that track requests
and workload isolation as they move between services.
► Red Hat OpenShift integration
► Microservices configuration, ► Kiali, an open source project for
► Hybrid cloud support across viewing configurations, monitoring
discovery, load balancing,
all components traffic, and analyzing traces.
and management
► Comprehensive security ► Multiple networking interfaces.
► Monitoring and logging
► High availability and performance ► The Red Hat 3scale Istio plugin
► Infrastructure resource
management, resiliency, for integration with Red Hat 3scale
► Customizable developer portal
and elasticity API Management.

Try Red Hat OpenShift Service Mesh

at learn.openshift.com/servicemesh.

Gain flexibility through integration

Our platforms give you the flexibility needed to build an effective, efficient services architecture that meets your organization’s needs
today and adapts easily to future change.

Deploy a consistent foundation Continue using your preferred Start where you are today
for all of your microservices. tools, languages, and runtimes. and expand at your own pace.

Service mesh or API management? | 15

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Deploy API management and service mesh solutions together

Red Hat API management and service mesh products integrate to allow you to use them together more easily and effectively.

How does it work?

Red Hat OpenShift Service Mesh implements a service control plane using Istio and a service data plane using Envoy, an open source
edge and service proxy technology. The control plane is used to configure rules and policies that are applied at the microservice
runtime. The data plane controls communication between microservices according to these rules and policies.

The Red Hat 3scale Istio plugin, included with Red Hat OpenShift Service Mesh, connects the control plane to Red Hat 3scale API Man-
agement. During operation, policy and rule checks run from the data plane, through the control plane and plugin, to Red Hat 3scale API
Management to authorize API requests and report use. API policies are configured through Red Hat 3scale API Management and applied
via the plugin and service mesh control plane. This integration allows you to efficiently set up an API with a service mesh backend.

Service A Service A

Envoy Envoy

Policy and telemetry checks

Red Hat 3scale

Istio control plane
Istio plugin

Service mesh or API management? | 16

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Deliver a complete service using APIs and microservices

This section describes how to set up a complete service offering using Red Hat 3scale API Management and Red Hat OpenShift
Service Mesh. In this example, we construct a simple products rating API. Our goal is to create controlled access to a set of microser-
vices and traditional application services that provide information about a product. Users, developers, and applications will be able to
access details, reviews, and ratings for a particular product.

To accomplish these objectives, we will set up an API that provides access to a core product microservice, which can connect to other
services to provide product details, reviews, and ratings information.

Service mesh

Reviews Ratings
service service
Product Product
API service
Details
service

Microservice Traditional service

Service mesh or API management? | 17

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

This page shows a more detailed configuration for this service example. The product, review, and rating services are implemented as
microservices within Red Hat OpenShift Service Mesh. These services interact with each other within the same domain boundary. The
details service uses existing, traditional application architecture.

All of these services sit behind the product API, which is independent of the service implementation. The API is set up via Red Hat
3scale API Management, allowing formal rules and policies to be applied to its use.

Requests enter the service mesh through standard Istio ingress processes. At each ingress point, the request is checked against the
predefined policies via Envoy proxies and the Red Hat 3scale Istio plugin. If the request complies with all policies, it is routed forward
to the product service. The product service can then interact with the details, reviews, and ratings services. These interactions are also
governed by predefined policies applied via Envoy proxies. Finally outbound traffic is routed back to the requester via Envoy proxies and
the Red Hat 3scale Istio plugin.

This configuration provides managed access to product information for internal and external developers while preventing direct access
to the services themselves and maintaining detailed control over the back-end service implementation.

Service mesh

Reviews Ratings
API service service
API requests
consumers Istio Product Product
ingress API service
Details
service

Developer
applications Istio control plane

Red Hat 3scale Istio plugin

Envoy proxy Developer portal Admin portal

Service mesh or API management? | 18

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Take advantage of flexible deployment options

Red Hat makes it easier to build an integrated API management and service mesh architecture. You can start with either an API man-
agement or a service mesh solution and expand to incorporate the other at your own pace and with less effort.

Starting point: Starting point:

Red Hat 3scale API Management Red Hat OpenShift Service Mesh
If you already have Red Hat 3scale API Management, If you already have Red Hat OpenShift Service Mesh,
you can add Red Hat OpenShift Service Mesh to your you can add Red Hat 3scale API Management to your
environment using the Red Hat 3scale Istio plugin. environment using the Red Hat 3scale Istio plugin.

1. Enable the Red Hat 3scale Istio plugin. 1. Enable the Red Hat 3scale Istio plugin.

2. Activate Red Hat 3scale API Management 2. Activate Red Hat 3scale API Management
authorization for the services you wish to move authorization for the services you wish to
to your service mesh. administer as APIs.

3. Once the desired services are added to your 3. Configure API management policies and access
service mesh, deactivate authorization for controls through Red Hat 3scale API Management
them through Red Hat 3scale API Management for the nodes and services you wish to expose
APIcast gateways. as APIs.

Your existing API-based access controls operate Your existing service mesh operates without change.
without change. You can continue to use your current You can continue to develop, connect, and manage
rules and policies via Red Hat 3scale API Management microservices using Red Hat OpenShift Service Mesh
while moving the back-end service implementation while implementing certain microservices as APIs
to a service mesh. This configuration ensures traffic without no duplication in traffic control gateways.
control gateways are not duplicated.

Read the Read Hat OpenShift Container Platform documentation to learn more about using the Red Hat 3scale Istio plugin.

Service mesh or API management? | 19

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Discover success across industries

Amsterdam Airport Schiphol, Europe’s fourth-busiest airport, wanted to improve its

passenger experience and become the best digital airport. This goal includes providing
seamless journeys for passengers — for example, by minimizing the time spent on the “With [Red Hat] 3scale API
travel booking process — improving the cost-efficiency of its operations, and using the
latest technology to collaborate with airlines and other stakeholders Management, the learning
curve is small, and you can
To support this shift, Schiphol decided to migrate several of its IT systems to the
cloud to become more flexible, secure, and efficient. The airport deployed Red Hat
deploy APIs very quickly.”
OpenShift as the foundation for its hybrid cloud environment, supported by Red Hat Mechiel Aalbers
3scale API Management, Red Hat Middleware, and other Red Hat products to accel- Senior Technical Application Coordinator,
Amsterdam Airport Schiphol
erate development and deployment and improve API management. With help from
Red Hat Consulting, Schiphol deployed Red Hat OpenShift Dedicated in just 10 days.

With the new platform, Schiphol can more quickly add new services. Connecting its
on-premise environment to Red Hat OpenShift lets the airport easily exchange data
between its main systems and cloud APIs. In addition, by using its Airport Service Bus
platform to infuse data into its API services in Red Hat OpenShift, the airport’s IT teams
can develop new APIs 50% faster. Overall, the new Red Hat environment supports
Schiphol’s vision of agile, self-service processes and vendor flexibility that help its IT
teams quickly and efficiently develop and deploy new customer-facing services.

Launched a production Cut new service and API Deployed self-service capabilities
cloud platform in 10 days development time by 50% for increased agility

Read the success story

Service mesh or API management? | 20

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

Emirates NBD provides retail, wholesale, and corporate Lufthansa Technik, the world’s largest independent provider
financial services across the UAE and international markets. of airline maintenance, repair, and overhaul (MRO) services,
To increase the speed and flexibility of IT delivery while con- sought to create a digital platform for the aviation industry.
trolling costs, it began an ambitious multimillion-dollar initiative The solution, AVIATAR, would help material planners, engineers,
to transform its end-to-end technology infrastructure and and other end users better predict events and, as a result, save
practices. With a centralized private cloud platform built with time and money. To support its development and operation,
Red Hat container, integration, and API technologies, Emir- the company created a hybrid cloud infrastructure based on
ates NBD simplified collaboration with third-party partners, enterprise open source software from Red Hat. The AVIATAR
cut software development cycles by months, and launched team can now use agile DevOps approaches, automation,
innovative digital engagement capabilities to compete with internal and third-party integration, and self-service capabili-
cloud-native companies. Now, it can take advantage of emerg- ties to quickly iterate based on data and feedback. As a result,
ing technology to offer the services modern consumers in key Lufthansa Technik provides an innovative digital platform that
markets demand. helps the world’s airlines optimize their operations.

Simplified collaboration between Sped application workflows with

teams and with partners using APIs self-service, automation, and DevOps

Reduced app launch and update Gained flexibility through improved

cycles from 6-18 months to hours infrastructure and solution integration

Established a flexible, stable Expects to save airlines millions

foundation for private and hybrid cloud of euros on MRO services

Read the success story Read the success story

“To completely change our infrastructure and evolve toward microservices

and APIs, we had to create a new organizational structure. We now have
agile teams with product owners and business owners working together.”
Miguel Rio Tinto
Group CIO, Emirates NBD

Service mesh or API management? | 21

Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5

To support a population of 1.5 million people, the municipal Weathernews Inc., one of the world’s largest private weather
government of the City of Montevideo, Uruguay, employs information service companies, wanted to speed application
8,000 public administration officers. The city sought to and service development to meet an increase in demand
develop an IT platform that would integrate the municipality’s for weather information across industries and markets. The
infrastructure, services, and data to improve citizen satisfac- company sought to integrate various internal and external
tion. It used Red Hat OpenShift to create a microservices- and systems using standardized, centrally managed APIs. Weath-
Kubernetes container-based platform to integrate internal and ernews also needed to ensure its API environment was secure
third-party services and data. It also built a city service API and and reliable. By building its API management platform with
state web portal, MontevideoAPI, using Red Hat 3scale API Red Hat 3scale API Management, Weathernews has not only
Management to deliver valuable information — based on real- expanded internal use of APIs for more efficient development
time transportation data — to citizens and partner organizations. and faster service delivery to its customers but also gained
The city can now deliver improved traffic services to citizens. new, robust provisioning security capabilities.

Developed a bus tracking app used by Created a standard API platform to

more than 150,000 citizens per month support essential business functions

Integrated real-time data on private Improved API provisioning speed,

and public transportation doubling development productivity

Improved state decision-making and Gained robust access controls to

traffic services for citizens protect the platform and company data

Read the success snapshot Read the success story

“It was a great benefit of Red Hat 3scale API Management that we could
readily start on a small scale. The license provisioning, which had been
the biggest challenge, is now done quickly and safely with access control.”
Masaki Fukuda
Service Menu Development Group Leader, Weathernews

Service mesh or API management? | 22

Ready to get started?

A comprehensive service management architecture can help you increase speed,

agility, and efficiency. Red Hat offers integrated API management and service mesh
solutions that help you get the most from your APIs and microservices.

Learn more about deploying a service management architecture with Red Hat:
red.ht/service-mesh-api-mgt

Get started faster with Red Hat Services.

Work with Red Hat experts to deploy an effective service management architecture.
Red Hat offers consulting and training services to help your organization adopt API
management and service mesh solutions faster.

Schedule a complimentary discovery session:

redhat.com/consulting

Copyright © 2021 Red Hat, Inc. Red Hat, the Red Hat logo, and OpenShift are trademarks or registered trademarks of Red Hat, Inc.
or its subsidiaries in the United States and other countries.

F28474_0421_KVM