Hi [[ session.user.profile.firstName ]]

Demystifying Service Mesh: New Pattern or New Technology?

In a short period of time, service APIs went from being primarily an edge interface connecting developers outside of the organization with internal systems to the glue that binds those internal systems (microservices) into a functioning whole. Consequently, one of the unavoidable results of microservice-oriented architectures is that internal communication within the data center will increase. Service mesh arose as a potential solution to the challenges that arise from increased East-West traffic by providing a different framework for deploying existing technology.

However, most of what service mesh introduces has been provided for many years by API Management products. Features such as observability, network error handling, health-checks, etc. are hallmarks of API management. These features don’t constitute anything novel in themselves, but as a pattern, service mesh introduces a new way of deploying those features within our architecture.

Join Kong CTO and Co-Founder Marco Palladino as he walks attendees through the architectural changes that have led to the rise of service mesh and why legacy API management solutions born before the advent of containers can’t keep up.

Webinar takeaways:

- Service mesh as an architecture pattern, not a technology
- The implications of adopting microservices-oriented architectures
- Why traditional API management solutions can’t keep up
Recorded Dec 7 2018 64 mins
Your place is confirmed,
we'll send you email reminders
Presented by
Marco Palladino, CTO & Co-Founder, Kong
Presentation preview: Demystifying Service Mesh: New Pattern or New Technology?

Network with like-minded attendees

  • [[ session.user.profile.displayName ]]
    Add a photo
    • [[ session.user.profile.displayName ]]
    • [[ session.user.profile.jobTitle ]]
    • [[ session.user.profile.companyName ]]
    • [[ userProfileTemplateHelper.getLocation(session.user.profile) ]]
  • [[ card.displayName ]]
    • [[ card.displayName ]]
    • [[ card.jobTitle ]]
    • [[ card.companyName ]]
    • [[ userProfileTemplateHelper.getLocation(card) ]]
  • Channel
  • Channel profile
  • Microservices: The Journey and 3 Challenges You Will Uncover Along the Way Dec 18 2018 6:00 pm UTC 45 mins
    Marcelo da Cruz Pinto, Principal Engineer, McAfee; Paul Dickens, Product Manager, Kong
    Almost four years ago, McAfee embarked in the transition towards microservices. They needed an API platform that could integrate with a very complex infrastructure built using multiple languages and methodologies. Additionally, they required this solution to be able to scale or contract with services, and the team to be able to integrate and build custom capabilities on top of it.

    Kong is now a critical element of McAfee’s infrastructure, enabling its microservices journey and supporting it as it becomes the largest cyber security solutions provider across the globe.

    During its journey, the team at McAfee identified three challenges that are common to microservices architectures. Marcelo da Cruz Pinto, Principal Engineer at McAfee, shares the strategies he implemented to manage and minimize these challenges.

    Join Marcelo, and Paul Dickens, Principal Product Manager at Kong while they discuss McAfee’s journey and strategies to manage the challenges that arise with microservices architectures.

    Webinar Takeaways:

    - Insights into the microservices journey at McAfee
    - Three strategies to manage challenges that typically arise when deploying microservices architectures
    - The true benefits of microservices
  • Kong 1.0 and Beyond: Preparing for a Cloud-Native World Recorded: Dec 13 2018 49 mins
    Marco Palladino, CTO & CO-Founder, Kong; Cooper Marcus, Director of Ecosystem, Kong
    With Kong 1.0, we confirm that Kong is a proven, robust, stable, and production-ready API management platform. Kong stands poised as an API gateway, service mesh, and the basis for a control platform that will serve users faithfully as their information exchange needs, and those of the industry, change.

    As the amount of data and services explodes, enterprises must prepare for a cloud-native world that enables them to free and scale their architectures.

    In this presentation, Kong CTO & Co-Founder, Marco Palladino, and Director of Ecosystem, Cooper Marcus, walk us through the journey towards Kong 1.0 and share the vision that positions Kong as a service control platform for all of your data flows, regardless of your chosen architecture or deployment patterns.

    Webinar takeaways:

    - Learn about the three forces leading us towards cloud-native first architectures
    - Understand how we got here – the milestones marking the maturity of Kong
    - Gain visibility into the future of APIs and the implications for your architecture – Cloud-Native First, but hybrid while you get there.
    - Why you need a solution that can support all of your deployment patterns.
  • Demystifying Service Mesh: New Pattern or New Technology? Recorded: Dec 7 2018 64 mins
    Marco Palladino, CTO & Co-Founder, Kong
    In a short period of time, service APIs went from being primarily an edge interface connecting developers outside of the organization with internal systems to the glue that binds those internal systems (microservices) into a functioning whole. Consequently, one of the unavoidable results of microservice-oriented architectures is that internal communication within the data center will increase. Service mesh arose as a potential solution to the challenges that arise from increased East-West traffic by providing a different framework for deploying existing technology.

    However, most of what service mesh introduces has been provided for many years by API Management products. Features such as observability, network error handling, health-checks, etc. are hallmarks of API management. These features don’t constitute anything novel in themselves, but as a pattern, service mesh introduces a new way of deploying those features within our architecture.

    Join Kong CTO and Co-Founder Marco Palladino as he walks attendees through the architectural changes that have led to the rise of service mesh and why legacy API management solutions born before the advent of containers can’t keep up.

    Webinar takeaways:

    - Service mesh as an architecture pattern, not a technology
    - The implications of adopting microservices-oriented architectures
    - Why traditional API management solutions can’t keep up
  • Essentials of Microservices API Management for the Enterprise Recorded: Nov 29 2018 62 mins
    Aaron Miller, Senior Solutions Engineer, Kong Inc.; Cooper Marcus, Principal Product Manager, Kong Inc.
    Transitioning to a microservices architecture?

    As microservices become an evermore mission-critical component of your enterprise architecture, there are a few challenges that will become increasingly salient. The need for scalability, high performance, and flexibility will make you think about APIs differently.

    In this webinar, Aaron Miller and Cooper Marcus discuss the peculiar challenges of microservices architectures. They also demonstrate how Kong meets these challenges by being lightweight, super fast, and infrastructure agnostic.
Kong
Kong

Embed in website or blog

Successfully added emails: 0
Remove all
  • Title: Demystifying Service Mesh: New Pattern or New Technology?
  • Live at: Dec 7 2018 5:00 pm
  • Presented by: Marco Palladino, CTO & Co-Founder, Kong
  • From:
Your email has been sent.
or close