Kong in 1.x Territory
•
0 likes•721 views
Kong 1.0 reached maturity with the addition of L4 proxying, service mesh capabilities using mTLS, and blue/green upgrade paths. Kong 1.1 introduced declarative configuration using a YAML file for DB-less deployments and importing configurations into databases. It also added tags for filtering entities. Upcoming versions will focus on performance, gRPC support, and Kong Enterprise features while continuing to consolidate the platform.
Report
Share
Report
Share
Download to read offline
Recommended
A Kong retrospective: from 0.10 to 0.13
A short introductory talk given as part of the April 2018 Kong meetup "Introducing Kubernetes Ingress Controller for Kong".
This talk covers the new features and improvements made to Kong from 2017 to 2018, including the groundwork conducted by Kong Inc. and open source contributors that allowed for the development of the Kong Ingress Controller for Kubernetes.
The Kong Ingress Controller for Kubernetes was then announced during the meetup:
https://github.com/Kong/kubernetes-ingress-controller
A Cassandra driver from and for the Lua community
This document discusses a Cassandra driver for Lua called lua-cassandra. It was created to provide a pure Lua implementation of Cassandra for the Lua and OpenResty communities. The driver supports features like cluster awareness, load balancing policies, retries, and SSL connections. It was created as a fork of an earlier Cassandra driver called lua-resty-cassandra to add support for Cassandra 3.x and improve interoperability with OpenResty. The driver is well tested and documented to make it easy for others to use.
Developing a user-friendly OpenResty application
Talk given at OpenResty Con 2017 in Beijing.
Kong (https://getkong.org) is a widely-adopted open source API Gateway built with OpenResty. It aims at helping secure, manage, and extend microservices-based architectures with minimal effort from the user, while ensuring platform agnosticism.
In this talk, we will explore the challenges we encountered developing such an OpenResty application, and how we overcame many of them by way of libraries and contributions back to the OpenResty community. We will cover topics such as clustering OpenResty nodes, inter-workers communication, DNS resolution, typical pitfalls OpenResty developers should avoid, and much more.
Logs/Metrics Gathering With OpenShift EFK Stack
This document summarizes a presentation about logs and metrics gathering with the OpenShift EFK stack. It introduces the OpenShift logging team and their objectives of collecting distributed logs in a common data model with security and scalability. It describes the main components of Fluendt for collection and normalization and Elasticsearch for storage. It provides examples of using the logging stack with OpenShift, OpenStack, and oVirt and advice for custom application logging.
gRPC: The Story of Microservices at Square
Back in 2015, Square and Google collaborated to launch gRPC, an open source RPC framework backed by protocol buffers and HTTP/2, based on real-world experiences operating microservices at scale. If you build microservices, you will be interested in gRPC.
This webcast covers:
- a technical overview of gRPC
- use cases and applicability in your stack
- a deep dive into the practicalities of operationalizing gRPC
Flink Forward Berlin 2017: Patrick Lucas - Flink in Containerland
Apache Flink, a powerful distributed stateful stream processing framework, is an especially good fit for deployment on a containerization platform: its storage requirement is primarily external (e.g. HDFS or S3), clusters often share the lifetime of the jobs that run on them, and the flexibility of allocating resources on such a platform allows for scaling jobs up and down as necessary. In this talk I will give a brief introduction to Apache Flink, then describe the journey to making it a first-class citizen of the container world. I will cover my experience preparing to publish the “official repository” of Flink images on Docker Hub, the challenges of fitting a Flink deployment in a Kubernetes-shaped box, and the rough edges of Flink itself that were exposed by this process.
Flink Forward Berlin 2017: Jörg Schad, Till Rohrmann - Apache Flink meets Apa...
Apache Mesos allows operators to run distributed applications across an entire datacenter and is attracting ever increasing interest. As much as distributed applications see increased use enabled by Mesos, Mesos also sees increasing use due to a growing ecosystem of well integrated applications. One of the latest additions to the Mesos family is Apache Flink. Flink is one of the most popular open source systems for real-time high scale data processing and allows users to deal with low-latency streaming analytical workloads on Mesos. In this talk we explain the challenges solved while integrating Flink with Mesos, including how Flink’s distributed architecture can be modeled as a Mesos framework, and how Flink was integrated with Fenzo. Next, we describe how Flink was packaged to easily run on DC/OS.
Virtual Flink Forward 2020: Build your next-generation stream platform based ...
As organizations are getting better at capturing streaming data and the data velocity and volume are ever-increasing, the traditional messaging queues or log storage systems are suffering from scalability or operational and maintenance problems. Apache Pulsar is a multi-tenant, high-performance distributed pub-sub messaging system. Pulsar includes multiple features, such as native support for multiple clusters in a Pulsar instance, seamless geo-replication of messages across clusters, very low publishing and end-to-end latency, seamless scalability to over a million topics, and guaranteed message delivery with persistent message storage provided by Apache BookKeeper. In this talk, I will use one of the most popular stream processing engines, Apache Flink, as an example, to share our experience in building a stream processing and storage stack. Some of the traits are: * How to ensure end-to-end exactly-once semantics based on Pulsar's durable and replayable storage as well as Pulsar transaction. * How to implement Pulsar topics as infinite tables based on Pulsar's schema. * How to efficiently store stream states in Pulsar based on Pulsar's layered storage API. * A usage scenario that chaining all functionalities in the streaming platform.
Recommended
A Kong retrospective: from 0.10 to 0.13
A short introductory talk given as part of the April 2018 Kong meetup "Introducing Kubernetes Ingress Controller for Kong".
This talk covers the new features and improvements made to Kong from 2017 to 2018, including the groundwork conducted by Kong Inc. and open source contributors that allowed for the development of the Kong Ingress Controller for Kubernetes.
The Kong Ingress Controller for Kubernetes was then announced during the meetup:
https://github.com/Kong/kubernetes-ingress-controller
A Cassandra driver from and for the Lua community
This document discusses a Cassandra driver for Lua called lua-cassandra. It was created to provide a pure Lua implementation of Cassandra for the Lua and OpenResty communities. The driver supports features like cluster awareness, load balancing policies, retries, and SSL connections. It was created as a fork of an earlier Cassandra driver called lua-resty-cassandra to add support for Cassandra 3.x and improve interoperability with OpenResty. The driver is well tested and documented to make it easy for others to use.
Developing a user-friendly OpenResty application
Talk given at OpenResty Con 2017 in Beijing.
Kong (https://getkong.org) is a widely-adopted open source API Gateway built with OpenResty. It aims at helping secure, manage, and extend microservices-based architectures with minimal effort from the user, while ensuring platform agnosticism.
In this talk, we will explore the challenges we encountered developing such an OpenResty application, and how we overcame many of them by way of libraries and contributions back to the OpenResty community. We will cover topics such as clustering OpenResty nodes, inter-workers communication, DNS resolution, typical pitfalls OpenResty developers should avoid, and much more.
Logs/Metrics Gathering With OpenShift EFK Stack
This document summarizes a presentation about logs and metrics gathering with the OpenShift EFK stack. It introduces the OpenShift logging team and their objectives of collecting distributed logs in a common data model with security and scalability. It describes the main components of Fluendt for collection and normalization and Elasticsearch for storage. It provides examples of using the logging stack with OpenShift, OpenStack, and oVirt and advice for custom application logging.
gRPC: The Story of Microservices at Square
Back in 2015, Square and Google collaborated to launch gRPC, an open source RPC framework backed by protocol buffers and HTTP/2, based on real-world experiences operating microservices at scale. If you build microservices, you will be interested in gRPC.
This webcast covers:
- a technical overview of gRPC
- use cases and applicability in your stack
- a deep dive into the practicalities of operationalizing gRPC
Flink Forward Berlin 2017: Patrick Lucas - Flink in Containerland
Apache Flink, a powerful distributed stateful stream processing framework, is an especially good fit for deployment on a containerization platform: its storage requirement is primarily external (e.g. HDFS or S3), clusters often share the lifetime of the jobs that run on them, and the flexibility of allocating resources on such a platform allows for scaling jobs up and down as necessary. In this talk I will give a brief introduction to Apache Flink, then describe the journey to making it a first-class citizen of the container world. I will cover my experience preparing to publish the “official repository” of Flink images on Docker Hub, the challenges of fitting a Flink deployment in a Kubernetes-shaped box, and the rough edges of Flink itself that were exposed by this process.
Flink Forward Berlin 2017: Jörg Schad, Till Rohrmann - Apache Flink meets Apa...
Apache Mesos allows operators to run distributed applications across an entire datacenter and is attracting ever increasing interest. As much as distributed applications see increased use enabled by Mesos, Mesos also sees increasing use due to a growing ecosystem of well integrated applications. One of the latest additions to the Mesos family is Apache Flink. Flink is one of the most popular open source systems for real-time high scale data processing and allows users to deal with low-latency streaming analytical workloads on Mesos. In this talk we explain the challenges solved while integrating Flink with Mesos, including how Flink’s distributed architecture can be modeled as a Mesos framework, and how Flink was integrated with Fenzo. Next, we describe how Flink was packaged to easily run on DC/OS.
Virtual Flink Forward 2020: Build your next-generation stream platform based ...
As organizations are getting better at capturing streaming data and the data velocity and volume are ever-increasing, the traditional messaging queues or log storage systems are suffering from scalability or operational and maintenance problems. Apache Pulsar is a multi-tenant, high-performance distributed pub-sub messaging system. Pulsar includes multiple features, such as native support for multiple clusters in a Pulsar instance, seamless geo-replication of messages across clusters, very low publishing and end-to-end latency, seamless scalability to over a million topics, and guaranteed message delivery with persistent message storage provided by Apache BookKeeper. In this talk, I will use one of the most popular stream processing engines, Apache Flink, as an example, to share our experience in building a stream processing and storage stack. Some of the traits are: * How to ensure end-to-end exactly-once semantics based on Pulsar's durable and replayable storage as well as Pulsar transaction. * How to implement Pulsar topics as infinite tables based on Pulsar's schema. * How to efficiently store stream states in Pulsar based on Pulsar's layered storage API. * A usage scenario that chaining all functionalities in the streaming platform.
Ingress controller present, past and future
This document discusses Kubernetes Ingress Controllers. It provides an overview of Kubernetes nodes, services, and service architecture. It then discusses the benefits and limitations of Ingress Controllers, providing examples. It notes that Ingress Controllers allow external access to cluster services and that different implementations have varying features. The document concludes by discussing the future of Ingress, including new classes and path matching, as well as the new Gateway API.
Fluentd Project Intro at Kubecon 2019 EU
Fluentd is a streaming data collector that can unify logging and metrics collection. It collects data from sources using input plugins, processes and filters the data, and outputs it to destinations using output plugins. It is commonly used for container logging, collecting logs from files or Docker and adding metadata before outputting to Elasticsearch or other targets. Fluentbit is a lightweight version of Fluentd that is better suited for edge collection and forwarding logs to a Fluentd instance for aggregation.
OSDC 2018 - Distributed monitoring
Modern software development is increasingly taking a “microservice” approach that has resulted in an explosion of complexity at the network level. We have more applications running distributed across different datacenters. Distributed tracing, events, and metrics are essential for observing and understanding modern microservice architectures.
This talk is a deep dive on how to monitor your distributed system. You will get tools, methodologies, and experiences that will help you to realize what your applications expose and how to get value out from all these information.
Gianluca Arbezzano, SRE at InfluxData will share how to monitor a distributed system, how to switch from a more traditional monitoring approach to observability. Stay focused on the server’s role and not on the hostname because it’s not really important anymore, our servers or containers are fast moving part and it’s easy to detach it from the right in case of trouble than call the server by name as a cute puppet. How to design a SLO for your core services and now to iterate on them. Instrument your services with tracing using tools like Zipkin or Jaeger to measure latency between in your network.
Performance is not an Option - gRPC and Cassandra
This is the slide deck from my June 2016 presentation on using gRPC and Cassandra to build high performance web services in an IoT enviroment
Flink Connector Development Tips & Tricks
A look at some of the challenges and techniques for developing a connector for Apache Flink, covering the different types of connectors, lifecycle, metrics, event-time support, and fault tolerance.
Presentation video: https://www.youtube.com/watch?v=ZkbYO5S4z18
Fluentd and Distributed Logging at Kubecon
This document discusses distributed logging with containers using Fluentd. It notes the challenges of logging in container environments where logs need to be collected from ephemeral containers and transferred to storage. It introduces Fluentd as a flexible data collection tool that can collect logs from containers using various plugins and methods like log drivers, shared volumes, and application libraries. The document discusses deployment patterns for Fluentd including using it for source-side aggregation to buffer and transfer logs more efficiently and for destination-side aggregation to scale log storage.
InfluxDB 2.0: Dashboarding 101 by David G. Simmons
InfluxDB 2.0 has some new dashboarding and querying capabilities that will make using a time series database even easier. This InfluxDays NYC 2019 presentation presented by David G. Simmons (Senior Developer Evangelist at InfluxData), walks you through how to set up your first dashboard.
Flink Forward San Francisco 2018: Steven Wu - "Scaling Flink in Cloud"
Over 109 million subscribers are enjoying more than 125 million hours of TV shows and movies per day on Netflix. This leads to massive amount of data flowing through our data ingestion pipeline to improve service and user experience. They are powering various data analytic cases like personalization, operational insight, fraud detection. At the heart of this massive data ingestion pipeline is a self-serve stream processing platform that processes 3 trillion events and 12 PB of data every day. We have recently migrated this stream processing platform from Samza to Flink. In this talk, we will share the challenges and issues that we run into when running Flink at scale in cloud. We will dive deep into the troubleshooting techniques and lessons learned.
OSMC 2018 | Distributed Tracing FAQ by Gianluca Arbezzano
Microservices, containers and more in general distributed systems have opened a different point of view on our system and applications. We need to understand how a single event or requests cross our app jumping over networks, containers, virtual machines and sometime clod provider. There is a specific practice called distributed tracing to increase observability of systems like that. After this talk, you will have a solid idea around what tracing means, how you can instrument your applications and you will be ready to trace your application across many languages using open source technologies like OpenTracing, OpenCensus, Zipkin, Jaeger, InfluxDB. You will ask yourself how you survived until today!
'Scalable Logging and Analytics with LogStash'
Rich Viet, Principal Engineer at Cloud Elements presents 'Scalable Logging and Analytics with LogStash' at All Things API meetup in Denver, CO.
Learn more about scalable logging and analytics using LogStash. This will be an overview of logstash components, including getting started, indexing, storing and getting information from logs.
Logstash is a tool for managing events and logs. You can use it to collect logs, parse them, and store them for later use (like, for searching).
Reactive database access with Slick3
The document discusses Reactive Slick, a new version of the Slick database access library for Scala that provides reactive capabilities. It allows parallel database execution and streaming of large query results using Reactive Streams. Reactive Slick is suitable for composite database tasks, combining async tasks, and processing large datasets through reactive streams.
gRPC: Beyond REST
This document discusses gRPC, an open-source high performance RPC framework created by Google. It provides benefits over REST such as binary encoding which allows for higher performance, as well as a contract-first approach using protocol buffers to define services. Protocol buffers can generate code for multiple platforms and allow flexible evolution of structures. gRPC uses HTTP/2 for a single connection with header compression. While REST is still necessary for some use cases, gRPC provides higher performance for internal APIs and microservices.
Snabb Switch: Riding the HPC wave to simpler, better network appliances (FOSD...
By Katerina Barone-Adesi.
Driven by the needs of scientific computing, rapid rises in memory bandwidth have made it possible to implement high-performance network functions in a radically simpler way. Snabb Switch rides this wave, bypassing the kernel to process network packets in terse Lua, leaving the programmer free to focus on the essence of their problem. This talk presents our experiences delivering a carrier-grade implementation of "lightweight 4 over 6", an IPv4-as-a-service architecture that tunnels access to the IPv4 internet through specialized Snabb appliances.
We report on our recent experience implementing a carrier-grade virtualized network function, with observations on what it is like to build real-world, high-performance Snabb applications. (and kernel bypass). Each instance runs at essentially line speed on two ten-gigabit Ethernet cards.
Lightweight 4-over-6 (lw4o6) defines an IPv4-as-a-service architecture that allows ISPs to internally operate an IPv6-only network, tunneling IPv4 connections between lw4o6-aware endpoints installed at the customer's site (e.g. in OpenWRT) and an internet-facing "lwAFTR". Lw4o6 was specified in 2015 as RFC 7596 and has the architectural advantage that the carrier-side lwAFTR only needs per-customer state, not per-flow state. An lw4o6 system can also be configured to share IPv4 addresses between multiple customers as part of an IPv4 exhaustion strategy. It allows IPv4 networks to interoperate smoothly, while a carrier between them runs a pure-IPv6 network.
Igalia has built an open source "lwAFTR" implementation that is ready to deploy in production. We describe the joys of hacking with Snabb, giving a quick intro to Snabb, modern x86, and lw4o6 along the way.
(c) 2016 FOSDEM VZW
CC BY 2.0 BE
https://archive.fosdem.org/2016/
Flink Forward Berlin 2017: Mihail Vieru - A Materialization Engine for Data I...
In Zalando's microservice architecture, each service continuously generates streams of events for the purposes of inter-service communication or data integration. Some of these events describe business processes, e.g. a customer has placed an order or a parcel has been shipped. Out of this, the need to materialize event streams from the central event bus into persistent cloud storage evolved. The temporarily persisted data is then integrated into our relational data warehouse. In this talk we present a materialization engine backed by Apache Flink. We show how we employ Flink’s RESTful API, custom accumulators and stoppable sources to provide another API abstraction layer for deploying, monitoring and controlling our materialization jobs. Our jobs compact event streams depending on event properties and transform their complex JSON structures into flat files for easier integration into the data warehouse.
Building Microservices with Spring Cloud and Netflix OSS
Source code:
https://github.com/semihhakkioglu/spring-cloud-microservice-example
https://github.com/semihhakkioglu/spring-cloud-microservice-config
The Patterns of Distributed Logging and Containers
The presentation at CloudNativeCon Europe 2017, about how to design logging platform in container and microservices based computing platforms.
NATS in action - A Real time Microservices Architecture handled by NATS
The document describes an architecture for managing infrastructure and platforms using microservices that communicate over NATS. Key points:
- Ernest is an IAAS+PAAS hybrid cloud platform that uses microservices and NATS to manage infrastructure resources, deploy applications, and automate scaling across multiple cloud providers.
- NATS is used as the central communication system between Ernest microservices to process user-defined workflows for building environments.
- Workflows define things like networks, virtual machine instances, configuration, and can deploy and provision applications. This allows Ernest to automate the creation and management of environments.
Fluentd 101
Fluentd is an open source data collector that provides a unified logging layer between data sources and backend systems. It decouples these systems by collecting and processing logs and events in a flexible and scalable way. Fluentd uses plugins and buffers to make data collection reliable even in the case of errors or failures. It can forward data between Fluentd nodes for high availability and load balancing.
Introduction to Kong API Gateway
This document provides an overview of Kong, an open-source API gateway. It discusses that Kong is a cloud-native, scalable middleware between clients and APIs, and supports features like authentication, security, traffic control, and analytics. The document also summarizes the Community and Enterprise editions of Kong, including that the Enterprise edition provides additional capabilities like an admin GUI, API analytics, and support. It concludes with an example of using Kong to expose an API and discusses benefits and concerns of Kong.
Scaling 100PB Data Warehouse in Cloud
Introduction about Pinterest's data architecture and how we handle our infrastructure at ~100PB scale in cloud.
B2B Integration in the Cloud
Driven by new business processes and regulation, the need for data exchange between organisations is heavily increasing. As 'Trading Partners', companies exchange data using electronic messages or 'events'. The automation of this B2B communication is very different compared to the use of Enterprise Service Buses within an organisation.
This presentation will show different insights in protocols and message formats which are being used in business, from file transfer and EDI until AS2 with different XML dialects. Also security and integration with 'endpoints' are explained.
Another Day, Another Billion Packets
In this session, we walk through the Amazon VPC network presentation and describe the problems we were trying to solve when we created it. Next, we walk through how these problems are traditionally solved, and why those solutions are not scalable, inexpensive, or secure enough for AWS. Finally, we provide an overview of the solution that we've implemented and discuss some of the unique mechanisms that we use to ensure customer isolation, get packets into and out of the network, and support new features like VPC endpoints.
More Related Content
What's hot
Ingress controller present, past and future
This document discusses Kubernetes Ingress Controllers. It provides an overview of Kubernetes nodes, services, and service architecture. It then discusses the benefits and limitations of Ingress Controllers, providing examples. It notes that Ingress Controllers allow external access to cluster services and that different implementations have varying features. The document concludes by discussing the future of Ingress, including new classes and path matching, as well as the new Gateway API.
Fluentd Project Intro at Kubecon 2019 EU
Fluentd is a streaming data collector that can unify logging and metrics collection. It collects data from sources using input plugins, processes and filters the data, and outputs it to destinations using output plugins. It is commonly used for container logging, collecting logs from files or Docker and adding metadata before outputting to Elasticsearch or other targets. Fluentbit is a lightweight version of Fluentd that is better suited for edge collection and forwarding logs to a Fluentd instance for aggregation.
OSDC 2018 - Distributed monitoring
Modern software development is increasingly taking a “microservice” approach that has resulted in an explosion of complexity at the network level. We have more applications running distributed across different datacenters. Distributed tracing, events, and metrics are essential for observing and understanding modern microservice architectures.
This talk is a deep dive on how to monitor your distributed system. You will get tools, methodologies, and experiences that will help you to realize what your applications expose and how to get value out from all these information.
Gianluca Arbezzano, SRE at InfluxData will share how to monitor a distributed system, how to switch from a more traditional monitoring approach to observability. Stay focused on the server’s role and not on the hostname because it’s not really important anymore, our servers or containers are fast moving part and it’s easy to detach it from the right in case of trouble than call the server by name as a cute puppet. How to design a SLO for your core services and now to iterate on them. Instrument your services with tracing using tools like Zipkin or Jaeger to measure latency between in your network.
Performance is not an Option - gRPC and Cassandra
This is the slide deck from my June 2016 presentation on using gRPC and Cassandra to build high performance web services in an IoT enviroment
Flink Connector Development Tips & Tricks
A look at some of the challenges and techniques for developing a connector for Apache Flink, covering the different types of connectors, lifecycle, metrics, event-time support, and fault tolerance.
Presentation video: https://www.youtube.com/watch?v=ZkbYO5S4z18
Fluentd and Distributed Logging at Kubecon
This document discusses distributed logging with containers using Fluentd. It notes the challenges of logging in container environments where logs need to be collected from ephemeral containers and transferred to storage. It introduces Fluentd as a flexible data collection tool that can collect logs from containers using various plugins and methods like log drivers, shared volumes, and application libraries. The document discusses deployment patterns for Fluentd including using it for source-side aggregation to buffer and transfer logs more efficiently and for destination-side aggregation to scale log storage.
InfluxDB 2.0: Dashboarding 101 by David G. Simmons
InfluxDB 2.0 has some new dashboarding and querying capabilities that will make using a time series database even easier. This InfluxDays NYC 2019 presentation presented by David G. Simmons (Senior Developer Evangelist at InfluxData), walks you through how to set up your first dashboard.
Flink Forward San Francisco 2018: Steven Wu - "Scaling Flink in Cloud"
Over 109 million subscribers are enjoying more than 125 million hours of TV shows and movies per day on Netflix. This leads to massive amount of data flowing through our data ingestion pipeline to improve service and user experience. They are powering various data analytic cases like personalization, operational insight, fraud detection. At the heart of this massive data ingestion pipeline is a self-serve stream processing platform that processes 3 trillion events and 12 PB of data every day. We have recently migrated this stream processing platform from Samza to Flink. In this talk, we will share the challenges and issues that we run into when running Flink at scale in cloud. We will dive deep into the troubleshooting techniques and lessons learned.
OSMC 2018 | Distributed Tracing FAQ by Gianluca Arbezzano
Microservices, containers and more in general distributed systems have opened a different point of view on our system and applications. We need to understand how a single event or requests cross our app jumping over networks, containers, virtual machines and sometime clod provider. There is a specific practice called distributed tracing to increase observability of systems like that. After this talk, you will have a solid idea around what tracing means, how you can instrument your applications and you will be ready to trace your application across many languages using open source technologies like OpenTracing, OpenCensus, Zipkin, Jaeger, InfluxDB. You will ask yourself how you survived until today!
'Scalable Logging and Analytics with LogStash'
Rich Viet, Principal Engineer at Cloud Elements presents 'Scalable Logging and Analytics with LogStash' at All Things API meetup in Denver, CO.
Learn more about scalable logging and analytics using LogStash. This will be an overview of logstash components, including getting started, indexing, storing and getting information from logs.
Logstash is a tool for managing events and logs. You can use it to collect logs, parse them, and store them for later use (like, for searching).
Reactive database access with Slick3
The document discusses Reactive Slick, a new version of the Slick database access library for Scala that provides reactive capabilities. It allows parallel database execution and streaming of large query results using Reactive Streams. Reactive Slick is suitable for composite database tasks, combining async tasks, and processing large datasets through reactive streams.
gRPC: Beyond REST
This document discusses gRPC, an open-source high performance RPC framework created by Google. It provides benefits over REST such as binary encoding which allows for higher performance, as well as a contract-first approach using protocol buffers to define services. Protocol buffers can generate code for multiple platforms and allow flexible evolution of structures. gRPC uses HTTP/2 for a single connection with header compression. While REST is still necessary for some use cases, gRPC provides higher performance for internal APIs and microservices.
Snabb Switch: Riding the HPC wave to simpler, better network appliances (FOSD...
By Katerina Barone-Adesi.
Driven by the needs of scientific computing, rapid rises in memory bandwidth have made it possible to implement high-performance network functions in a radically simpler way. Snabb Switch rides this wave, bypassing the kernel to process network packets in terse Lua, leaving the programmer free to focus on the essence of their problem. This talk presents our experiences delivering a carrier-grade implementation of "lightweight 4 over 6", an IPv4-as-a-service architecture that tunnels access to the IPv4 internet through specialized Snabb appliances.
We report on our recent experience implementing a carrier-grade virtualized network function, with observations on what it is like to build real-world, high-performance Snabb applications. (and kernel bypass). Each instance runs at essentially line speed on two ten-gigabit Ethernet cards.
Lightweight 4-over-6 (lw4o6) defines an IPv4-as-a-service architecture that allows ISPs to internally operate an IPv6-only network, tunneling IPv4 connections between lw4o6-aware endpoints installed at the customer's site (e.g. in OpenWRT) and an internet-facing "lwAFTR". Lw4o6 was specified in 2015 as RFC 7596 and has the architectural advantage that the carrier-side lwAFTR only needs per-customer state, not per-flow state. An lw4o6 system can also be configured to share IPv4 addresses between multiple customers as part of an IPv4 exhaustion strategy. It allows IPv4 networks to interoperate smoothly, while a carrier between them runs a pure-IPv6 network.
Igalia has built an open source "lwAFTR" implementation that is ready to deploy in production. We describe the joys of hacking with Snabb, giving a quick intro to Snabb, modern x86, and lw4o6 along the way.
(c) 2016 FOSDEM VZW
CC BY 2.0 BE
https://archive.fosdem.org/2016/
Flink Forward Berlin 2017: Mihail Vieru - A Materialization Engine for Data I...
In Zalando's microservice architecture, each service continuously generates streams of events for the purposes of inter-service communication or data integration. Some of these events describe business processes, e.g. a customer has placed an order or a parcel has been shipped. Out of this, the need to materialize event streams from the central event bus into persistent cloud storage evolved. The temporarily persisted data is then integrated into our relational data warehouse. In this talk we present a materialization engine backed by Apache Flink. We show how we employ Flink’s RESTful API, custom accumulators and stoppable sources to provide another API abstraction layer for deploying, monitoring and controlling our materialization jobs. Our jobs compact event streams depending on event properties and transform their complex JSON structures into flat files for easier integration into the data warehouse.
Building Microservices with Spring Cloud and Netflix OSS
Source code:
https://github.com/semihhakkioglu/spring-cloud-microservice-example
https://github.com/semihhakkioglu/spring-cloud-microservice-config
The Patterns of Distributed Logging and Containers
The presentation at CloudNativeCon Europe 2017, about how to design logging platform in container and microservices based computing platforms.
NATS in action - A Real time Microservices Architecture handled by NATS
The document describes an architecture for managing infrastructure and platforms using microservices that communicate over NATS. Key points:
- Ernest is an IAAS+PAAS hybrid cloud platform that uses microservices and NATS to manage infrastructure resources, deploy applications, and automate scaling across multiple cloud providers.
- NATS is used as the central communication system between Ernest microservices to process user-defined workflows for building environments.
- Workflows define things like networks, virtual machine instances, configuration, and can deploy and provision applications. This allows Ernest to automate the creation and management of environments.
Fluentd 101
Fluentd is an open source data collector that provides a unified logging layer between data sources and backend systems. It decouples these systems by collecting and processing logs and events in a flexible and scalable way. Fluentd uses plugins and buffers to make data collection reliable even in the case of errors or failures. It can forward data between Fluentd nodes for high availability and load balancing.
Introduction to Kong API Gateway
This document provides an overview of Kong, an open-source API gateway. It discusses that Kong is a cloud-native, scalable middleware between clients and APIs, and supports features like authentication, security, traffic control, and analytics. The document also summarizes the Community and Enterprise editions of Kong, including that the Enterprise edition provides additional capabilities like an admin GUI, API analytics, and support. It concludes with an example of using Kong to expose an API and discusses benefits and concerns of Kong.
Scaling 100PB Data Warehouse in Cloud
Introduction about Pinterest's data architecture and how we handle our infrastructure at ~100PB scale in cloud.
What's hot (20)
InfluxDB 2.0: Dashboarding 101 by David G. Simmons
InfluxDB 2.0: Dashboarding 101 by David G. Simmons
Flink Forward San Francisco 2018: Steven Wu - "Scaling Flink in Cloud"
Flink Forward San Francisco 2018: Steven Wu - "Scaling Flink in Cloud"
OSMC 2018 | Distributed Tracing FAQ by Gianluca Arbezzano
OSMC 2018 | Distributed Tracing FAQ by Gianluca Arbezzano
Snabb Switch: Riding the HPC wave to simpler, better network appliances (FOSD...
Snabb Switch: Riding the HPC wave to simpler, better network appliances (FOSD...
Flink Forward Berlin 2017: Mihail Vieru - A Materialization Engine for Data I...
Flink Forward Berlin 2017: Mihail Vieru - A Materialization Engine for Data I...
Building Microservices with Spring Cloud and Netflix OSS
Building Microservices with Spring Cloud and Netflix OSS
The Patterns of Distributed Logging and Containers
The Patterns of Distributed Logging and Containers
NATS in action - A Real time Microservices Architecture handled by NATS
NATS in action - A Real time Microservices Architecture handled by NATS
Similar to Kong in 1.x Territory
B2B Integration in the Cloud
Driven by new business processes and regulation, the need for data exchange between organisations is heavily increasing. As 'Trading Partners', companies exchange data using electronic messages or 'events'. The automation of this B2B communication is very different compared to the use of Enterprise Service Buses within an organisation.
This presentation will show different insights in protocols and message formats which are being used in business, from file transfer and EDI until AS2 with different XML dialects. Also security and integration with 'endpoints' are explained.
Another Day, Another Billion Packets
In this session, we walk through the Amazon VPC network presentation and describe the problems we were trying to solve when we created it. Next, we walk through how these problems are traditionally solved, and why those solutions are not scalable, inexpensive, or secure enough for AWS. Finally, we provide an overview of the solution that we've implemented and discuss some of the unique mechanisms that we use to ensure customer isolation, get packets into and out of the network, and support new features like VPC endpoints.
Another Day, Another Billion Packets
In this session, we walk through the Amazon VPC network presentation and describe the problems we were trying to solve when we created it. Next, we walk through how these problems are traditionally solved, and why those solutions are not scalable, inexpensive, or secure enough for AWS. Finally, we provide an overview of the solution that we've implemented and discuss some of the unique mechanisms that we use to ensure customer isolation, get packets into and out of the network, and support new features like VPC endpoints.
Distributed Virtual Transaction Directory Server
This document provides an overview of DVTDS (Distributed Virtual Transaction Directory Server), a new LDAP directory server solution from TeraCortex.
Key points:
- DVTDS uses a distributed architecture to partition data across multiple servers for high performance and availability. It supports data replication and distributed transactions.
- It provides data model virtualization through views and mappings to present different application-specific views of the underlying data.
- Benchmarking shows it significantly outperforms existing directory solutions in throughput tests, scaling linearly with additional resources. TeraCortex aims to release a free demo version in 2014.
ENT303 Another Day, Another Billion Packets
In this session, we will walk through the Amazon VPC network presentation and describe the problems we were trying to solve when we created it. Next, we will discuss how these problems are traditionally solved, and why those solutions are not scalable, inexpensive, or secure enough for AWS. Finally, we will provide an overview of the solution that we've implemented and discuss some of the unique mechanisms that we use to ensure customer isolation, get packets into and out of the network, and support new features like VPC endpoints.
another day, another billion packets
- The document describes Amazon's design of virtual private clouds (VPCs) which allow customers to define virtual networks within the AWS cloud.
- VPCs use a mapping service and virtual networking to make customer IP addresses and subnets appear isolated within AWS while being hosted on any physical server.
- This approach allows VPCs to automatically scale without constraints of physical network hardware and provides customers flexibility and control over their cloud networks.
Another day, another billion packets - Toronto
In this session, we walk through the Amazon VPC network presentation and describe the problems we were trying to solve when we created it. Next, we walk through how these problems are traditionally solved, and why those solutions are not scalable, inexpensive, or secure enough for AWS. Finally, we provide an overview of the solution that we've implemented and discuss some of the unique mechanisms that we use to ensure customer isolation, get packets into and out of the network, and support new features like VPC endpoints.
ENT303 Another Day, Another Billion Packets
In this session, we will walk through the Amazon VPC network presentation and describe the problems we were trying to solve when we created it. Next, we will discuss how these problems are traditionally solved, and why those solutions are not scalable, inexpensive, or secure enough for AWS. Finally, we will provide an overview of the solution that we've implemented and discuss some of the unique mechanisms that we use to ensure customer isolation, get packets into and out of the network, and support new features like VPC endpoints.
Another Day, Another Billion Packets
In this session, we walk through the Amazon VPC network presentation and describe the problems we were trying to solve when we created it. Next, we walk through how these problems are traditionally solved, and why those solutions are not scalable, inexpensive, or secure enough for AWS. Finally, we provide an overview of the solution that we've implemented and discuss some of the unique mechanisms that we use to ensure customer isolation, get packets into and out of the network, and support new features like VPC endpoints.
Chapter3 transport
The document provides an overview of Chapter 3 from the textbook "Computer Networking: A Top Down Approach" by Jim Kurose and Keith Ross. It discusses the goals and outline of the chapter which covers transport layer services, multiplexing and demultiplexing, UDP, principles of reliable data transfer, TCP, and congestion control. Specifically, it describes transport layer services, multiplexing and demultiplexing of data between applications, UDP as a connectionless transport protocol, and outlines the topics to be covered related to reliable data transfer and TCP.
Name Based Net Architectures
1. The document discusses IPNL, a proposed NAT-extended Internet architecture that aims to improve IPv4's scalability while maintaining its key properties. IPNL utilizes FQDNs and a new IPNL address format consisting of a middle realm number, realm number, and end host ID.
2. IPNL routing works by including optional FQDN and global address headers. Hosts know their FQDN/IP mappings and nearby routers know routing information. Experiments show IPNL introduces minimal latency overhead.
3. While IPNL maintains IPv4 properties like long addresses and robustness, it enables greater address scalability through realm-based addressing and isolation of site networks.
Name Based Net Architectures
The document discusses network architecture and name-based networks. It introduces the concepts of names, addresses, routes, and name-address bindings in networks. It discusses issues like mobility, address reuse, and updates when hosts change locations. Various approaches are described, including using the DNS, routing injections, tunneling, and triangle data flow to perform global server load balancing. A new proposed technique called Virtual Block Injection is described, which aims to address some limitations of other approaches.
(NET403) Another Day, Another Billion Packets
In this session, we walk through the Amazon VPC network presentation and describe the problems we were trying to solve when we created it. Next, we walk through how these problems are traditionally solved, and why those solutions are not scalable, inexpensive, or secure enough for AWS. Finally, we provide an overview of the solution that we've implemented and discuss some of the unique mechanisms that we use to ensure customer isolation, get packets into and out of the network, and support new features like VPC endpoints.
ENT303 Another Day, Another Billion Packets
In this session, we will walk through the Amazon VPC network presentation and describe the problems we were trying to solve when we created it. Next, we will discuss how these problems are traditionally solved, and why those solutions are not scalable, inexpensive, or secure enough for AWS. Finally, we will provide an overview of the solution that we've implemented and discuss some of the unique mechanisms that we use to ensure customer isolation, get packets into and out of the network, and support new features like VPC endpoints.
16.) layer 3 (basic tcp ip routing)
If the number of spine switches were to be merely doubled, the effect of a single switch failure is halved. With 8 spine switches, the effect of a single switch failure only causes a 12% reduction in available bandwidth. So, in modern data centers, people build networks with anywhere from 4 to 32 spine switches. With a leaf-spine network, every server on the network is exactly the same distance away from all other servers – three port hops, to be precise. The benefit of this architecture is that you can just add more spines and leaves as you expand the cluster and you don't have to do any recabling. Intuition Systems will also get more predictable latency between the nodes.
As a trend, disaggregation seems to be most useful for very large companies like Facebook and Google, or cloud providers. The technology does not necessarily have significant implications for small or medium sized businesses. Historically, however, technology has a way of trickling down from the pioneering phases of existing only within large companies with tremendous resources, to becoming more standardized across the board.
PLX Technology Company Overview
PLX Technology provides PCI Express switches and bridges that connect various components within servers, storage systems, networking equipment, and other devices. They have over 70% market share in PCI Express switches and are focused on growing their business connecting components within data centers and cloud computing environments. Their ExpressFabric technology uses PCI Express as a converged fabric to connect servers, storage, and networking within a data center rack in order to reduce costs and power consumption compared to using multiple traditional networking protocols.
Cilium - API-aware Networking and Security for Containers based on BPF
Cilium provides network security and visibility for microservices. It uses eBPF/XDP to provide fast and scalable networking and security controls at layers 3-7. Key features include identity-based firewalling, load balancing, and mutual TLS authentication between services. It integrates with Kubernetes to apply network policies using standard Kubernetes resources and custom CiliumNetworkPolicy resources for finer-grained control.
Profile_Prateek
This document provides a summary of Prateek's professional experience in software development for telecom and networking. Over 9.5 years, he has worked on projects involving optical networking, load balancing servers, protocol development, and customer support. His responsibilities have included technical lead roles, individual development work, design, testing, and system integration. He has strong skills in C, C++, Linux, networking protocols, data structures, and development tools like version control systems. His work experience includes roles at NEC Technology, Brocade Communication, Juniper Networks, and Huawei Technology where he contributed to projects involving network security, load balancing, network address translation, and more.
Cilium - Network security for microservices
The document discusses how BPF and XDP are revolutionizing network security and performance for microservices. BPF allows profiling, tracing, and running programs at the network driver level. It also enables highly performant networking functions like DDoS mitigation using XDP. Cilium uses BPF to provide layer 3-7 network security for microservices with policies based on endpoints, identities, and HTTP protocols. It integrates with Kubernetes to define network policies and secure microservice communication and APIs using eBPF programs for filtering and proxying.
Another Day, Another Billion Packets
In this session, we walk through the Amazon VPC network presentation and describe the problems we were trying to solve when we created it. Next, we walk through how these problems are traditionally solved, and why those solutions are not scalable, inexpensive, or secure enough for AWS. Finally, we provide an overview of the solution that we've implemented and discuss some of the unique mechanisms that we use to ensure customer isolation, get packets into and out of the network, and support new features like VPC endpoints.
Similar to Kong in 1.x Territory (20)
Cilium - API-aware Networking and Security for Containers based on BPF
Cilium - API-aware Networking and Security for Containers based on BPF
Recently uploaded
Modelling Up - DDDEurope 2024 - Amsterdam
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
Preparing Non - Technical Founders for Engaging a Tech Agency
Preparing non-technical founders before engaging a tech agency is crucial for the success of their projects. It starts with clearly defining their vision and goals, conducting thorough market research, and gaining a basic understanding of relevant technologies. Setting realistic expectations and preparing a detailed project brief are essential steps. Founders should select a tech agency with a proven track record and establish clear communication channels. Additionally, addressing legal and contractual considerations and planning for post-launch support are vital to ensure a smooth and successful collaboration. This preparation empowers non-technical founders to effectively communicate their needs and work seamlessly with their chosen tech agency.Visit our site to get more details about this. Contact us today www.ishtechnologies.com.au
How to write a program in any programming language
How to write a program in any programming language
Using Query Store in Azure PostgreSQL to Understand Query Performance
Microsoft has added an excellent new extension in PostgreSQL on their Azure Platform. This session, presented at Posette 2024, covers what Query Store is and the types of information you can get out of it.
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
Microservice Teams - How the cloud changes the way we work
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS ...
Presented at NLJUG's J-Spring 2024.
UI5con 2024 - Bring Your Own Design System
How do you combine the OpenUI5/SAPUI5 programming model with a design system that makes its controls available as Web Components? Since OpenUI5/SAPUI5 1.120, the framework supports the integration of any Web Components. This makes it possible, for example, to natively embed own Web Components of your design system which are created with Stencil. The integration embeds the Web Components in a way that they can be used naturally in XMLViews, like with standard UI5 controls, and can be bound with data binding. Learn how you can also make use of the Web Components base class in OpenUI5/SAPUI5 to also integrate your Web Components and get inspired by the solution to generate a custom UI5 library providing the Web Components control wrappers for the native ones.
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
Presentation from Ghazal Aakel and Eric Jochum at the GSD Community Stage Meetup on June 6th, 2024
Oracle 23c New Features For DBAs and Developers.pptx
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
Energy consumption of Database Management - Florina Jonuzi
Presentation from Florina Jonuzi at the GSD Community Stage Meetup on June 06, 2024
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
The Key to Digital Success_ A Comprehensive Guide to Continuous Testing Integ...
In today's business landscape, digital integration is ubiquitous, demanding swift innovation as a necessity rather than a luxury. In a fiercely competitive market with heightened customer expectations, the timely launch of flawless digital products is crucial for both acquisition and retention—any delay risks ceding market share to competitors.
Webinar On-Demand: Using Flutter for Embedded
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdf
Salesforce Healthcare CRM, implemented by VALiNTRY360, revolutionizes patient management by enhancing patient engagement, streamlining administrative processes, and improving care coordination. Its advanced analytics, robust security, and seamless integration with telehealth services ensure that healthcare providers can deliver personalized, efficient, and secure patient care. By automating routine tasks and providing actionable insights, Salesforce Healthcare CRM enables healthcare providers to focus on delivering high-quality care, leading to better patient outcomes and higher satisfaction. VALiNTRY360's expertise ensures a tailored solution that meets the unique needs of any healthcare practice, from small clinics to large hospital systems.
For more info visit us https://valintry360.com/solutions/health-life-sciences
Mobile App Development Company In Noida | Drona Infotech
Drona Infotech is a premier mobile app development company in Noida, providing cutting-edge solutions for businesses.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
Recently uploaded (20)
YAML crash COURSE how to write yaml file for adding configuring details
YAML crash COURSE how to write yaml file for adding configuring details
Preparing Non - Technical Founders for Engaging a Tech Agency
Preparing Non - Technical Founders for Engaging a Tech Agency
How to write a program in any programming language
How to write a program in any programming language
Using Query Store in Azure PostgreSQL to Understand Query Performance
Using Query Store in Azure PostgreSQL to Understand Query Performance
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
Microservice Teams - How the cloud changes the way we work
Microservice Teams - How the cloud changes the way we work
J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS ...
J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS ...
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
Oracle 23c New Features For DBAs and Developers.pptx
Oracle 23c New Features For DBAs and Developers.pptx
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
Energy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina Jonuzi
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
The Key to Digital Success_ A Comprehensive Guide to Continuous Testing Integ...
The Key to Digital Success_ A Comprehensive Guide to Continuous Testing Integ...
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdf
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdf
Mobile App Development Company In Noida | Drona Infotech
Mobile App Development Company In Noida | Drona Infotech
Kong in 1.x Territory
- 3. Kong’s biggest milestone yet Kong 1.0 release candidate being announced at Kong Summit in Sept 2018
- 5. Kong 1.0 - Reaching maturity L4 proxying Service Mesh and mTLS Blue/Green upgrade path
- 6. L4 proxying Kong HTTP/1 HTTP/2 HTTP Service MySQL/PostgreSQL/ Redis/MongoDB/... proxy_listen stream_listen TCP stream_listen = 0.0.0.0:7000
- 9. Blue/Green upgrade paths Kong 0.14 Kong 0.14 PostgreSQL / Cassandra # 1.0 node $ kong migrations up upgrading from 0.14, bootstrapping database... migrating core on database 'kong'... core migrated up to: 000_base (executed) … 22 migrations processed 13 executed 9 pending Kong 1.0
- 14. Blue/Green upgrade paths Kong 1.0 Kong 1.0 Kong 1.0 PostgreSQL / Cassandra # 1.0 node $ kong migrations finish migrating core on database 'kong'... core migrated up to: 001_14_to_15 (executed) … 9 migrations processed 9 executed
- 15. ● L4 plugins preread ● ● ● ● Recognizing 4 years of production mileage Kong 1.0 - Other achievements
- 17. Kong 1.1 - Declarative Config DB-less deployments DB Import Tags
- 18. $ kong config init $ ls kong.conf kong.yml Kong 1.1 - Declarative Config kong.conf kong.yml Node config Entities config _format_version: "1.1" services: - name: service-1 url: https://svc1 routes: - paths: - /path1 - /path2 plugins: - name: key-auth - name: service-2 url: https://svc2
- 19. Kong 1.1 - Declarative Config kong.conf kong.yml Node config Entities config database = off declarative_config = ./kong.yml
- 20. Kong 1.1 - DB Import kong.yml PostgreSQL / Cassandra $ kong config db_import ./kong.yml parse successful, beginning import import successful
- 21. Kong 1.1 - DB-import Kong 1.1 Kong 1.1 Kong 1.1 Service Service Service PostgreSQL / Cassandra $ kong start Kong started
- 22. Kong 1.1 - DB-less $ kong start Kong 1.1 kong.yml Kong started
- 23. Kong 1.1 - DB-less Kong 1.1 Kong 1.1 Kong 1.1 Service Service Service PostgreSQL / Cassandra
- 24. Kong 1.1 - DB-less Kong 1.1 Kong 1.1 Kong 1.1 Service Service Service kong.yml
- 25. Kong 1.1 - Tags $ curl -XPOST https://kong:8001/services -d name=service-1 -d url=https://svc1 -d 'tags[]=foo' -d 'tags[]=bar' # kong.yml services: - name: service-2 url: https://svc2 tags: - foo - bar Or
- 26. $ curl -XGET 'http://kong:8001/services?tags=foo/baz' { "next": null, "data": [ { "name": “service-1”, "host": "svc1", "tags": [ "foo", "bar" ] }, { "name": “service-2”, "host": "svc2", "tags": [ "foo", "bar" ] } ] } Kong 1.1 - Tags
- 27. Kong 1.1 - Other achievements ● /config ○ ● New plugin: K8S sidecar injector ● ●
- 30. Kong 1.2 - Consolidation & performance ● ● ● ● ○ ○ ○ ○
- 31. Kong 1.3+ - Upcoming work ● gRPC ● ● ● ● ●
- 32. Kong - Upcoming work ● Kong Enterprise ● ● Envoy proxy
- 33. Join the discussion on Kong Nation https://discuss.konghq.com