Api Management with Service Mesh

•

0 likes•108 views

In a world of disaggregated API-based architectures, developers are increasingly adopting microservices — and Service Mesh is being used to control many service-to-service communications. But Service Mesh is not addressing the concern of how the exploding number of APIs can be exposed in a controlled and secure manner to their API consumers. In this meetup, we will discuss how to augment service mesh functionality with API management capabilities, so you can create an end-to-end solution for your entire business functionality — from microservices to APIs, to end-user applications.

Technology

API Management with Service Mesh
Lakmal Warusawithana
@lakwarus

Agenda
● Evolution of Applications
● Why Microservice Architecture?
● Challenges with Microservices
● Why Service Mesh?
● Why API Management?
● Demo

Monolith to Microservice
● Easy to scale with customer
demands.
● Agility, ﬂexibility and speed to
market.
● Smaller teams, agile software
development life cycles.
● Freedom to use heterogeneous
technologies, early feedback
cycles

Microservices Challenges - Observability

Microservices Challenges - Risk of Code Releases

Service Mesh
A service mesh is a dedicated infrastructure layer that
controls service-to-service communication over a network.
It provides a method in which separate parts of an
application can communicate with each other.
source:techtarget.com

Istio is an open source service mesh implementation which
provides behavioral insights and operational control over
the service mesh as a whole, offering a complete solution
to satisfy the diverse requirements of microservice
applications.
Istio

Istio Architecture (source — https://istio.io/docs/concepts/what-is-istio/)

Type Service Mesh API Management
Routing • L3/L4 • HTTP, GRPC, GraphQL
Security • Service identity and mTLS • User/App Authentication
and Authorization (OAuth /
JWT)
Analytics • Service Operational Analytics • Business and Developer
focus Analytics
Rate Limiting • RPC level rate limiting • Business related rate
limiting
Personas and
Portal
• DevOps portals
• Publisher, Developer, CXO
portals

When is API Management required in a Service Mesh
● When users need to expose microservices to outside in
a secured and a controlled manner.
● When ﬁne grained security should be enforced on APIs
exposed.
● When stats need to be collected on API usage for
monetization and billing.
● When it is required to offer a marketplace for APIs for
easy discovery and adoption.

What's hot

The Aviatrix AVX Software-Defined Cloud Router establishes an abstraction layer between the public cloud provider’s networking primitives and the application to simplify the creation of logical cloud networks and services for hybrid connectivity, data security, multicloud connectivity, monitoring and troubleshooting. The solution consists of two components: Aviatrix Controller; and the Aviatrix Gateways, all of which are deployed in your VPCs or the on-premises environment.

Getting the Most Value from Your Aviatrix Controller & Gateways

Khash Nakhostin

Whether your cloud applications are multi-tenanted SaaS solutions or standalone instances hosted for individual customers, ensuring reliable and secure VPC connectivity poses a variety of challenges. Within minutes of signing up a new customer, your operations team will be expected to: Build IPsec tunnels to, for example, support API connectivity or secure data as it moves between an on-premises database and the hosted app Provision your customers’ administrative and end users with easy yet secure app access Ensure internal teams have secure access to perform maintenance and support

Securely Connecting Your Customers to Their Cloud-Hosted App – In Minutes

Khash Nakhostin

Secure Remote Access to AWS: Why OpenVPN & Jump Hosts Aren’t Enough

Khash Nakhostin

Microservices pattern for API Design

Debashish Maity

Understanding Service Mesh on Azure with HashiCorp Consul

Mitchell Pronschinske

Limitations of Existing Firewalls and AWS NAT Gateways There are legitimate reasons why AWS VPCs or Azure VNets need Internet access; for example, to receive software updates from vendors or integrate with native AWS services or third-party SaaS services. But this is substantially different from an on-premises use case, where traditional, full-featured firewalls are needed to filter co-mingled end-user traffic and application traffic. And while AWS provides a NAT gateway, it can be configured only on a per-VPC basis against a limited number of IP addresses.

Security Requirements and Tradeoffs for Controlling VPC-to-Internet Egress Tr...

Khash Nakhostin

ISTIO Deep Dive

Yong Feng

Microservices architecture

Mohamad Farhani

SpringOne Platform 2017 Ramiro Salas, Pivotal The concept of a service mesh represents a paradigm shift on application connectivity for distributed systems, with wide implications for analytics, policy and extensibility. In this talk, we will explain what a service mesh is, the power it brings to microservices, and its impact on Cloud Foundry and K8s, both separately and together. We will also discuss the implications for the traditional network infrastructure, and the shifting of responsibilities from L3/4 to L7, and our current thinking of using Istio to integrate all abstractions.

Connecting All Abstractions with Istio

VMware Tanzu

When someone reports an EC2 connectivity failure, what do you do? Open your Amazon VPC Console, launch an SSH session, and start typing CLI commands in search of clues. Common root causes include problems related to: Route table updates Phantom network ACLs Security policies Missing BGP routes Overfilling route tables or summarization mistakes Moreover, in many cases, networking is not an issue, but valuable time is lost eliminating the network as a cause before you can progress. Unfortunately, AWS does not natively provide the visibility and troubleshooting features needed by CloudOps and DevOps teams to identify and resolve problems quickly.

Network Troubleshooting in the Cloud: Tools, Techniques and Gotchas

Khash Nakhostin

Developing and managing hundreds (or maybe thousands) of microservices at scale is a challenge for both development and operations teams. We have seen over the last years the appearance of new frameworks dedicated to deliver ‘Cloud Native’ applications by providing a set of (out of box) building blocks. Most of these frameworks integrate microservices concerns at the code level. Recently, we have seen the emerging of a new pattern known as sidecar or proxy promoting to push all these common concerns outside of the business code and provides them on the edge by integrate a new layer to the underlying platform called Service Mesh. Istio is one of the leading Service Mesh implementing sidecar pattern. We will go during the presentation throw the core concepts behind Istio, the capabilities that provides to manage, secure and observe microservices and how it gives a new breath for both developers and operations. The presentation will be guided by a sequence of demo exposing Istio capabilities.

Managing microservices with Istio Service Mesh

Rafik HARABI

Anatomy of the modern application stack

Boyan Dimitrov

Clean up this mess - API Gateway & Service Discovery in .NET

Marcin Tyborowski

Microservices at Netflix

Katharina Probst

Api gateway : To be or not to be

Jaewoo Ahn

Poc ppt nthadi

Narayana Reddy Thadi

Modern application architectures are embracing public clouds, microservices, and container schedulers like Kubernetes and Nomad. These bring complex service-to-service communication patterns, increased scale, dynamic IP addresses, ephemeral infrastructure, and higher failure rates. These changes require a new approach for service discovery, configuration, and segmentation. Service discovery enables services to find and communicate with each other. Service configuration allows us to dynamically configure applications at runtime. Service segmentations lets us secure our microservices architectures by limiting access. In this talk, we cover these challenges and how to solve them with Consul providing as a service mesh.

Consul: Service Mesh for Microservices

ArmonDadgar

Today’s enterprise networks are expected to operate according to three tenets; security, reliability, and performance. This is why implementing a comprehensive method of ensuring network compliance is important to every organization. Network compliance ensures that every network device and service is properly configured and adheres to a clearly defined standard. This builds confidence in the network’s ability to operate optimally and creates a foundation of trust for further network automation. Today’s modern network spans the both on-prem and multi-cloud environments, which poses a new challenge for network teams who must ensure compliance for all areas of the network. Traditional tools for delivering compliance only work with on-premises, CLI-based networks and lack any support for cloud network services that are managed though APIs. Network teams need a fresh solution for this challenge, so join Glenn Gray and Rich Martin for part 3 of Itential’s Modern Network Compliance series where they will discuss how to achieve network compliance in a hybrid and multi-cloud network environment. In this webinar, we will dive into: • Understanding the complexity of cloud networks. • Uncovering the methods of delivering compliance to cloud networks. • Achieving on-prem and cloud network compliance with a demo of Itential’s Configuration Manager.

Modern Network Compliance: Achieving Compliance in a Hybrid, Multi-Cloud World

Itential

Microservices

Nebiyou Tibebu

In this talk we discuss key architecture patterns for designing authentication and authorization solutions in complex microservices environments. We focus on the key advantages and capabilities of AWS Cognito User Pools and Federated Identities and explore how this service can address the challenges of implementing client to service, service to service and service to infrastructure auth. In addition, we discuss patterns and best practices around building a highly available and resilient decentralised authorization solution for microservices environments based on OIDC. We present a simple RBAC implementation together with fine-grained permissions and end to end automation.

Complex architectures for authentication and authorization on AWS

Boyan Dimitrov

What's hot (20)

Getting the Most Value from Your Aviatrix Controller & Gateways

Securely Connecting Your Customers to Their Cloud-Hosted App – In Minutes

Secure Remote Access to AWS: Why OpenVPN & Jump Hosts Aren’t Enough

Microservices pattern for API Design

Understanding Service Mesh on Azure with HashiCorp Consul

Security Requirements and Tradeoffs for Controlling VPC-to-Internet Egress Tr...

ISTIO Deep Dive

Microservices architecture

Connecting All Abstractions with Istio

Network Troubleshooting in the Cloud: Tools, Techniques and Gotchas

Managing microservices with Istio Service Mesh

Anatomy of the modern application stack

Clean up this mess - API Gateway & Service Discovery in .NET

Microservices at Netflix

Api gateway : To be or not to be

Poc ppt nthadi

Consul: Service Mesh for Microservices

Modern Network Compliance: Achieving Compliance in a Hybrid, Multi-Cloud World

Microservices

Complex architectures for authentication and authorization on AWS

Similar to Api Management with Service Mesh

APIdays Paris 2019 - Cloud native API Management for Microservices on a Servi...

apidays

[APIdays Paris 2019] API Management in Service Mesh Using Istio and WSO2 API ...

WSO2

[APIdays Singapore 2019] API Management in a Istio Service Mesh with WSO2 API...

WSO2

[WSO2 API Day Dallas 2019] Extending Service Mesh with API Management

WSO2

[WSO2 API Day Toronto 2019] Extending Service Mesh with API Management

WSO2

[WSO2 API Day Chicago 2019] Extending Service Mesh with API Management

WSO2

APIdays Helsinki 2019 - Impact of Microservices Architecture on API Managemen...

apidays

Enterprise Integration in Cloud Native Microservices Architectures

Crishantha Nanayakkara

Design-Based Microservices AKA Planes, Trains & Automobiles

Matt McLarty

Microservices

Gyanendra Yadav

Understand the Microservices Architecture concepts Understand Event Sourcing and CQRS Understanding Domain Driven Design Understanding Functional Reactive Programming Understanding Distributed Transaction Management Understanding Microservices Messaging Setting up Micro services Infrastructure (API Gateway, Service Discovery, Load Balancer, Circuit Breaker) https://github.com/meta-magic/microservice_workshop

Microservices Part 3 Service Mesh and Kafka

Araf Karsh Hamid

A Guide on What Are Microservices: Pros, Cons, Use Cases, and More

Simform

Microservices Design Principles.pdf

Simform

On-demand recording: https://www.nginx.com/resources/webinars/istio-move-to-microservices-service-mesh/ About the webinar NGINX is widely known, used, and trusted for a variety of purposes. NGINX works as a reliable, high-performance web server, reverse proxy server, and load balancer. NGINX is also a widely used microservices hub, an Ingress controller for Kubernetes, and a sidecar proxy in the Istio service mesh. In this webinar, we’ll describe the move to microservices, the crucial role that NGINX has already played, and a range of architectural options that organizations have for their microservices apps, including three progressively complex models in the NGINX Microservices Reference Architecture. We’ll then introduce the emergence of Kubernetes as a container orchestration framework, the use of service mesh architectures, and the design of Istio. We’ll finish by showing how NGINX Open Source and NGINX Plus can be used as the sidecar proxy in an Istio service mesh, bringing greater reliability and capability to your service mesh application.

NGINX, Istio, and the Move to Microservices and Service Mesh

NGINX, Inc.

Introduction to Microservices

Fayçal Bziou

12월 16일 Meetup [Deep Dive] Microservice 트래픽 관리를 위한 Istio 알아보기 | 강인호 컨설턴트, 오라클

Oracle Korea

The elegant way of implementing microservices with istio

Inho Kang

Migrating application architectures to microservices is considered a key area of transformation in the IT world. Modernizing legacy applications to Kubernetes-based microservices can prove to be very challenging if not planned correctly, taking into consideration the right technologies and enablers. This session explains how Istio can be used as an enabler for modernizing legacy monolithic applications to microservices. Topics covered in the presentation will include: 1- Advantages of migrating to microservices and service mesh 2- Designing a microservice application based on splitting an existing monolithic application 3- Implementing microservices iteratively as a strangler fig application with Istio

Istio as an Enabler for Migrating Monolithic Applications to Microservices v1.3

Ahmed Misbah

A proper Microservice is designed for fast failure. Like other architectural style, microservices bring costs and benefits. Some development teams have found microservices architectural style to be a superior approach to a monolithic architecture. Other teams have found them to be a productivity-sapping burden. This material start with the basic what and why microservice, follow with the Felix example and the the successful strategies to develop microservice application.

Why Microservice

Kelvin Yeung

Do microservices force us to look differently at the way we lay down and evolve our integration architecture, or are they purely about how we build applications? Are microservices a new concept, or an evolution of the many ideas that came before them? What is the relationship between microservices and other key initiatives such as APIs, SOA, and Agile. In this session, we will unpick what microservices really are, and indeed what they are not. We will consider whether there is something unique about this particular point time in technology that has enables microservice concepts to take hold. Finally, we will look at if, when, where and how an enterprise can take on the benefits of microservices, and what products and technologies are applicable for that journey.

Microservices: Where do they fit within a rapidly evolving integration archit...

Kim Clark

Similar to Api Management with Service Mesh (20)