Scylla Summit 2018: Kong & Cassandra/Scylla for distributed APIs and Microservices

•Download as PPTX, PDF•

1 like•1,577 views

The way we build APIs and connect our services is changing. The components of a single application can be written in different languages, have different architectures, run on different infrastructure, and still need to talk to each other. In this hybrid world, propagating state across different systems is one of the biggest challenges to overcome. Kong has become the most widely adopted open-source API Platform in the tech industry because of its ability to connect disparate APIs at scale. It is able to do this because it is itself a stateless application that leverages Apache Cassandra or Scylla to propagate routing configuration, security tokens and other state across multiple nodes in complex API and Microservices use-cases. In this talk learn how Kong uses Cassandra or Scylla to reach an eventually consistent state across all its nodes. In this session we will explore: - Major industry trends that are transforming how we build APIs and Microservices - Understanding what is Kong and why it's being adopted - How Kong leverages Cassandra/Scylla to propagate state across large distributed enterprise deployments

Software

Kong & Cassandra/Scylla
for Distributed APIs
and Microservices
Marco Palladino
CTO Kong Inc.

Marco Palladino
Co-Founder / CTO at Kong
@subnetmarco

Data is in motion
180 ZB
Data created
annually by 2025*
25%
Data will be
real-time*
Trending away from stagnant data
lakes to in-flight information streams
* https://www.seagate.com/www-content/our-story/trends/files/Seagate-WP-DataAge2025-March-2017.pdf
TREND 1

Microservices: The
future is distributed
Distributed architecture causes east-
west traffic beyond edge gateway
TREND 2

Run applications
Anytime, Anywhere
ON-PREM
IOT
EDGE COMPUTING
CONTAINERS
PRIVATE/PUBLIC CLOUD
SERVERLESS
APIs need to run where
applications run
TREND 3
HYBRID

Hybrid
Languages
Containers
Services
Protocols
Clouds
Architectures
Teams
Organizations
Platforms

Monolith Services
Microservices/
Service Mesh
Serverless/FaaS Emerging Patterns

Services
Services Microservices/ Service Mesh
Infrastructure
Monolith Serverless/FaaS
Service Control Platform

Kong and Kong Enterprise
● Open-Source
● 45M+ Downloads since 2015
● Built on top of NGINX
● 18,000+ Stars in GitHub
Millions of Kong downloads across multiple
platforms.
● 110+ Contributors
● 100+ Meetups
● 10K+ Community Members

45M Downloads
72,000 instances running per day

Thank You
Any Questions ?
Please stay in touch
marco@konghq.com
@subnetmarco

What's hot

A brief overview of the significance of API Gateways in microservices architecture by providing Kong as an example. Slide 2: Monolith Vs Microservices Monolith: Pros- Simple to implement Less integration test - easy to test Easy to ship Fast development Cons- Violates Open-Close principle Nightmare when it comes to managing the code Difficult to enhance Bigger artifacts Hard to replace individual components like DB, Logger etc. Microservices- Pros- Easy to manage One reason to change Dynamic scaling Single responsibility Cons- Multiple points of failure Hard to test - rich integration tests required Heterogeneity in infrastructure Slide 3: API Gateway Pattern It is microservices design pattern. An API gateway is a service which is the entry point into the application from the outside world. It’s responsible for request routing, API composition, and other functions, such as authentication. There are a lot of issues when client is talking to multiple components to get the job done. These include multiple proxies at client side, different logic to handle different calls, client needs to know the implementation details of server. A much better approach is for a client to make a single request to what’s known as an API gateway. An API gateway is a service which is the single entry-point for API requests into an application. It’s similar to the Facade pattern from object-oriented design. Like a facade, an API gateway encapsulates the application’s internal architecture and provides an API to its clients. It might also have other responsibilities, such as authentication, monitoring, and rate limiting. These are also termed as BFF - Backend For Frontend Slide 4: API Gateway in Action It acts as a “backend for the frontend”. The clients do not know which services they are talking to. They communicate with a single interface - API Gateway. The gateway resolves the client requests and distributes them to respective services. Slide 7: Kong Architecture Kong is a cloud-native, fast, scalable, and distributed Microservice Abstraction Layer (also known as an API Gateway, API Middleware or in some cases Service Mesh). Made available as an open-source project in 2015, its core values are high performance and extensibility. Actively maintained, Kong is widely used in production at companies ranging from startups to Global 5000 as well as government organizations.

Api gateway in microservices

Kunal Hire

About the webinar The use of an API gateway and the move to microservices are two of the most important trends in application development. But are they similar, or different; complementary, or contradictory? In this webinar, we discuss the advantages of an API gateway, the advantages of microservices development, and how and when they can work together. The NGINX Microservices Reference Architecture (MRA) uses three different network architectures, with service mesh as a fourth. We describe how an API gateway relates to each of these network architectures and how to reduce rework if your application needs to evolve from one architecture to another. Speakers: Charles Pretzer, Technical Architect, NGINX, Inc. Floyd Smith, Director of Content Marketing, NGINX, Inc.

Using an API Gateway for Microservices

API Gateway study

Kong API Gateway

Kong API

API Gateway report

OSGi Community Event 2016 Presentation by Christian Schneider (Talend) Microservices and their frameworks like spring boot allow to start fast but can easily produce ugly monoliths or tangled webs of fine grained dependencies. OSGi on the other hand provides great modularity but is regarded as more complex than spring boot and alike. This Talk shows how to create lean and modular microservices using OSGi, maven, bndtools and Apache Karaf. The build result is a runnable jar or docker image and nicely fits microservice deployments. See how OSGi allows the flexibility to deploy each microservice on its own and let them communicate over (REST) remote calls or deploy them together and talk using OSGi services locally using the same business code bundles.

Lean Microservices with OSGi - Christian Schneider

mfrancis

Ambassador Kubernetes-Native API Gateway

Ambassador Labs

Service mesh with istio

WisnuPrabowo20

Microservice: starting point

inovia

Microservices & API Gateways

Kong Inc.

Modern cloud applications today are built as distributed microservices. These microservices talk to each other over L7 protocols: HTTP, gRPC, Redis, Kafka, and more. In this world, L7 proxies have assumed a crucial role in managing and observing L7 protocols. In this talk, I’ll discuss the evolution of service architectures, the role L7 proxies play in this world, and how there is now a battle raging between Envoy Proxy, HAProxy, and NGINX. I’ll wrap by talking about why we chose Envoy Proxy as the anchor of our Ambassador API Gateway and show how that has enabled a number of new capabilities.

The rise of Layer 7, microservices, and the proxy war with Envoy, NGINX, and ...

Ambassador Labs

TADSummit Dangerous demo: Oracle Presented by Doug Tait, Oracle at TADSummit Lisbon 18th November 2015 WebRTC Client connect to an HTML application deployed on OCSG over HTPP(s). The app use: OCSG Authentication REST API oneAPI SMS REST service exposed by OCSG to send SMS WebRTC API SDK deployed on WSC Once connected, the webRTC endpoint create a conference room and then: open a websocket connection to WSC using WSC SDK Can send an SMS an SMS to a mobile device with the link to the conference leveraging the SMS API It then use WSC API to make a call to a mobile user or to another webRTC Endpoint Chat message are sent via Datachannel RTP stream goes through WSC

TADSummit Dangerous demo: Oracle

Alan Quayle

Microservice API Gateways with NGINX Slides from talk given on Tuesday August 2nd, 2017 at the Denver Open Source Users Group (DOSUG). (NGINX is pronounced "engine x".) Microservices are a popular architectural solution. Clients of microservices may experience some difficulty keeping track of the various instances and endpoints they have to call. An API gateway can help manage large numbers of microservices and hide the infrastructure complexity from your clients. We will review a microservice architecture before and after the addition of an API gateway. An API gateway is a reverse proxy. A reverse proxy handles incoming requests from clients and calls a service to get the data to satisfy that request. The reverse proxy returns that data to the client. Many developers write these proxies by hand in custom code, not realizing there better solutions available. We will mention a number of popular solutions, some open source and some cloud-based services. For this talk, we will focus on NGINX, a popular open source reverse proxy and API Gateway. (NGINX also sells an enterprise offering, NGINX Plus, but this talk will only cover the features available in the open-source version.) We will show how to set up NGINX as an API Gateway. We will dive into the configuration and operation of NGINX.

Microservice API Gateways with NGINX

Geoffrey Filippi

Services are at the core of modern software architecture. Deploying a series of modular, small (micro-)services rather than big monoliths gives developers the flexibility to work in different languages, technologies and release cadence across the system; resulting in higher productivity and velocity, especially for larger teams. With the adoption of microservices, however, new problems emerge due to the sheer number of services that exist in a larger system. Problems that had to be solved once for a monolith, like security, load balancing, monitoring, and rate limiting need to be handled for each service. Istio, announced at GlueCon 2017, addresses these problems in a fundamental way through a service mesh framework. With Istio, developers can implement the core logic for the microservices, and let the framework take care of the rest – traffic management, discovery, service identity and security, and policy enforcement. Better yet, this can be also done for existing microservices without rewriting or recompiling any of their parts. Istio uses Envoy as its runtime proxy component and provides an extensible intermediation layer which allows global cross-cutting policy enforcement and telemetry collection.

An Open-Source Platform to Connect, Manage, and Secure Microservices

DoiT International

Getting traffic into a Kubernetes cluster should be simple, but it’s not. Richard Li explains how software architectures have evolved to take advantage of Kubernetes and discusses the implications that these changes have on ingress. Richard then covers some of the nuances of modern ingress, including authentication, resilience, and observability at the edge, explores how Kubernetes handles ingress today, with NodePorts, LoadBalancers, and ingress controllers, and shares his experience and lessons learned from using several real-world implementations of ingress on Kubernetes.

The Simply Complex Task of Implementing Kubernetes Ingress - Velocity NYC

Ambassador Labs

Ingress gateways are a quick and easy way to enable external clients to communicate with a service mesh. To demonstrate this, we implemented a powerful ingress gateway with a reliable ingress controller in an auto-healing, scalable platform. In this talk, we will demo several use cases, including service-to-service authorization with mTLS, service segmentation, and connectivity of services running on any platform to the service mesh. The solution we will share is built using HashiCorp Consul Ingress Gateway with Kong Ingress Controller on a Kubernetes platform with Consul Envoy proxy.

A Better Way for Applications to Communicate With Your Mesh

OlyaSurits

Service meshes are all the buzz in cloud-native world. How come only yesterday we didn't know such a thing existed and now everybody seems to want one? If you're already running a microservice-based system or only starting out with one — you may be asking yourself: "Do I also need a mesh?" In this session we'll try to answer what the mesh is good for, what problems it solves, what new questions it poses. More specifically we will: explore the SMI Spec; understand why everybody wants a mesh; see how the mesh helps with progressive delivery; discuss if it's time for you to get into the mesh.

WTF Do We Need a Service Mesh?

Anton Weiss

Kubernetes + netflix oss

Cristiano Altmann

What's hot (19)

Api gateway in microservices

Using an API Gateway for Microservices

API Gateway study

Kong API Gateway

Kong API

API Gateway report

Lean Microservices with OSGi - Christian Schneider

Ambassador Kubernetes-Native API Gateway

Service mesh with istio

Microservice: starting point

Microservices & API Gateways

The rise of Layer 7, microservices, and the proxy war with Envoy, NGINX, and ...

TADSummit Dangerous demo: Oracle

Microservice API Gateways with NGINX

An Open-Source Platform to Connect, Manage, and Secure Microservices

The Simply Complex Task of Implementing Kubernetes Ingress - Velocity NYC

A Better Way for Applications to Communicate With Your Mesh

WTF Do We Need a Service Mesh?

Kubernetes + netflix oss

Similar to Scylla Summit 2018: Kong & Cassandra/Scylla for distributed APIs and Microservices

Steve Robinson discusses how clients are taking advantage of cloud and cognitive computing to build a new generation of apps and services that are deepening the way people interact with technology. Learn more by visiting our Bluemix Hybrid page: http://ibm.co/1PKN23h Speakers Steve Robinson (General Manager, Cloud Platform Services, IBM Cloud) Cognitive Demo Ram Vennam (IBM Bluemix Developer Advocate) Damion Heredia (VP of Product Management and Design, IBM Bluemix and Marketplace)

IBM Relay 2015: Opening Keynote

IBM

APIdays Paris 2018 - API Management is Dead, Augusto Marietti, CEO and Co-Fou...

apidays

Accelerating a Path to Digital with a Cloud Data Strategy

MongoDB

Deep-dive into Microservices Patterns with Replication and Stream Analytics Target Audience: Microservices and Data Architects This is an informational presentation about microservices event patterns, GoldenGate event replication, and event stream processing with Oracle Stream Analytics. This session will discuss some of the challenges of working with data in a microservices architecture (MA), and how the emerging concept of a “Data Mesh” can go hand-in-hand to improve microservices-based data management patterns. You may have already heard about common microservices patterns like CQRS, Saga, Event Sourcing and Transaction Outbox; we’ll share how GoldenGate can simplify these patterns while also bringing stronger data consistency to your microservice integrations. We will also discuss how complex event processing (CEP) and stream processing can be used with event-driven MA for operational and analytical use cases. Business pressures for modernization and digital transformation drive demand for rapid, flexible DevOps, which microservices address, but also for data-driven Analytics, Machine Learning and Data Lakes which is where data management tech really shines. Join us for this presentation where we take a deep look at the intersection of microservice design patterns and modern data integration tech.

Microservices Patterns with GoldenGate

Jeffrey T. Pollock

Shaun Walsh, senior vice president of marketing and corporate development, speaks on this topic at SNW Europe on 10/29/13: IT is migrating to a new model of computing and business alignment that is not just about the cloud, not just about bring your own device (BYOD), but a new way of thinking about how the building blocks of IT are developed, purchased and assembled to achieve business goals. We will explore the great migrations in the IT world, starting with the new IT strategy (hybrid everywhere), expanding users’ expectations (going beyond instantaneous), new technology models (software defined computing), defining new core building blocks, (everything has to be a platform) and how selling to IT will change (re-definable value vs. ROI positioning). During this presentation, we will look beyond the hype curve and buzzword compliance to identify the most influential IT migrations that will change the way we work, partner and profit for the next decade.

The Great IT Migration

Emulex Corporation

Independent of the source of data, the integration of event streams into an Enterprise Architecture gets more and more important in the world of sensors, social media streams and Internet of Things. Events have to be accepted quickly and reliably, they have to be distributed and analyzed, often with many consumers or systems interested in all or part of the events. Dependent on the size and quantity of such events, this can quickly be in the range of Big Data. How can we efficiently collect and transmit these events? How can we make sure that we can always report over historical events? How can these new events be integrated into traditional infrastructure and application landscape? Starting with a product and technology neutral reference architecture, we will then present different solutions using Open Source frameworks and the Oracle Stack both for on premises as well as the cloud.

Internet of Things and Big Data

Swiss Data Forum Swiss Data Forum

Cisco Connect Halifax 2018 Understanding Cisco's next generation sd-wan sol...

Cisco Canada

FIWARE Global Summit - Building Production Grade IoT Platform Leveraging FIWARE

FIWARE

Open Standards Enabling Digital Transformation

Solace

IDC Insights Awards 2018 - What is an Event Mesh?

Solace

Solace Singapore User Group: Sumeet Puri

Solace

Cisco Connect Toronto 2018 sd-wan - delivering intent-based networking to t...

Cisco Canada

IoT and Edge Integration with Open Source Frameworks: Internet of Things (IoT) and edge integration is getting more important than ever before due to the massively growing number of connected devices year by year. This session shows open source frameworks built to develop very lightweight microservices, which can be deployed on small devices or in serverless architectures with very low resources and wire together all different kinds of hardware devices, APIs and online services. The focus of this session lies on showing open source projects such as Eclipse Kura, Node-RED or Flogo, which offer a framework plus zero-code environment with web IDE for building and deploying integration and data processing directly onto connected devices using IoT standards such as MQTT, WebSockets or CoaP, but also other interfaces such as Twitter feeds or REST services. The end of the session discusses the relation to other components in a IoT architecture including cloud IoT platforms and big data respectively streaming analytics solutions (such as Apache Storm, Flink, Spark Streaming, Samza, StreamBase, Apama).

IoT Open Source Integration Comparison (Kura, Node-RED, Flogo, Apache Nifi, S...

Kai Wähner

Cisco connect winnipeg 2018 understanding cisco's next generation sdwan sol...

Cisco Canada

Microsoft IT committed to move the integration workload into Azure. The workload covers the messaging platform for business to business as well as app to app communication at Microsoft. The integration service deals with thousands of business process flows that interact with hundreds of applications and partners across the globe and touches virtually every part of the business at Microsoft. Attend this session to learn the motivation for its move, approach Microsoft has taken, business drivers, planning for hybrid integration as well as the challenges in the implementation. You will come out equipped and inspired to get your Organization on to Azure!

Investing in Cloud Integration at Microsoft IT

BizTalk360

WWT IWAN Technical Presentation

World Wide Technology

Cloud Seeding

Trish McGinity, CCSK

Creating Scalable IoT Strategies for Manufacturing, Transportation, Utilities...

Solace

Enabling the Future of Work with SD-WAN

Xylos

Cloud Computing and the Promise of Everything as a Service

Lew Tucker

Similar to Scylla Summit 2018: Kong & Cassandra/Scylla for distributed APIs and Microservices (20)

IBM Relay 2015: Opening Keynote

APIdays Paris 2018 - API Management is Dead, Augusto Marietti, CEO and Co-Fou...

Accelerating a Path to Digital with a Cloud Data Strategy

Microservices Patterns with GoldenGate

The Great IT Migration

Internet of Things and Big Data

Cisco Connect Halifax 2018 Understanding Cisco's next generation sd-wan sol...

FIWARE Global Summit - Building Production Grade IoT Platform Leveraging FIWARE

Open Standards Enabling Digital Transformation

IDC Insights Awards 2018 - What is an Event Mesh?

Solace Singapore User Group: Sumeet Puri

Cisco Connect Toronto 2018 sd-wan - delivering intent-based networking to t...

IoT Open Source Integration Comparison (Kura, Node-RED, Flogo, Apache Nifi, S...

Cisco connect winnipeg 2018 understanding cisco's next generation sdwan sol...

Investing in Cloud Integration at Microsoft IT

WWT IWAN Technical Presentation

Cloud Seeding

Creating Scalable IoT Strategies for Manufacturing, Transportation, Utilities...

Enabling the Future of Work with SD-WAN

Cloud Computing and the Promise of Everything as a Service

More from ScyllaDB

See where an RDBMS-pro’s intuition leads him astray – and learn practical tips for the data modeling transition ScyllaDB has the potential to deliver impressive performance and scalability. The better you understand how it works, the more you can squeeze out of it. However, developers new to high-performance NoSQL intuitively shoot themselves in the foot with respect to things like table design, query design, indexing, and partitioning. Watch where our experienced Postgres developer intuitively falls into traps that hurt performance and scalability. And learn with him as our database performance expert offers friendly guidance on navigating all the unexpected behaviors that tend to trip up RDBMS experts. This webinar focuses on common data modeling and querying mistakes that occur when developers move from SQL to NoSQL. For example: - Understanding query first design principles - Planning for schema evolution - Steering clear of common pitfalls and anti-patterns - Assessing data access patterns This isn’t “Death-by-Powerpoint.” We’ll walk through problems encountered while migrating a real application from Postgres to ScyllaDB – and try to fix them live as well.

Developer Data Modeling Mistakes: From Postgres to NoSQL

Scylla Summit 2018: Kong & Cassandra/Scylla for distributed APIs and Microservices

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Similar to Scylla Summit 2018: Kong & Cassandra/Scylla for distributed APIs and Microservices

Similar to Scylla Summit 2018: Kong & Cassandra/Scylla for distributed APIs and Microservices (20)

More from ScyllaDB

More from ScyllaDB (20)

Recently uploaded

Recently uploaded (20)

Scylla Summit 2018: Kong & Cassandra/Scylla for distributed APIs and Microservices