Microservice Authorization with Open Policy Agent and Kuma
CEO of Styra Tim Hinrichs demonstrates how OPA and Kuma can be used for microservices API authorization.
Systems | Development | Analytics | API | Testing
Modern Software Development For Today's Systems & Applications
Authorizing Microservice APIs With OPA and Kuma
Many companies are leveraging DevOps, microservices, automation, self-service, cloud and CI/CD pipelines. These megatrends are changing how companies are building and running software. One thing that often slips through the cracks is security. With microservices, there’s an increase in the number of APIs companies have to protect. YouTube An error occurred. Try watching this video on www.youtube.com, or enable JavaScript if it is disabled in your browser.
Building Custom Servlets for C++ Microservices in Docker
In a previous post, C++ Microservices in Docker, we worked through the steps for creating a docker container that exposes a HydraExpress servlet container. We successfully deployed our HydraExpress server instance in Docker, however all that was available were the default example servlets. User application code wasn’t exposed. Let’s fix that and look at deploying custom C++ Servlet instances within the HydraExpress Docker container.
Picking up the pieces of your monolith breakdown
A decade ago, all developers could talk about was breaking down the monolith and event-driven architectures. Especially in the financial services industry, to become more nimble and accelerate their application delivery. They leveraged messaging systems to decouple the application, and specifically Apache Kafka has transitioned from being a data integration technology to the leading messaging system for microservices.
C++ Microservices in Docker
Microservices have become a popular way to architect applications, particularly those that compose functionality from a variety of loosely coupled systems and services. While there are a variety of frameworks and tools for implementing a microservice architecture, it isn’t always clear how to expose native code like C or C++ code within a wider microservice system. That’s where HydraExpress comes in.
The Complete Guide to Microservices
Microservices, also known as microservices architecture, refers to a method of designing and developing software systems. Microservice architecture is becoming increasingly popular as developers create larger and more advanced apps. The goal is to help enterprises become more Agile, especially as they adopt a culture of continuous testing. Here are the basic features of microservices.
Starting With a Monolith or Microservices: How New Technology Is Changing the Conventional View
Conventional wisdom says that new app development projects should begin as monolithic systems. This perspective suggests that you should wait until later to refactor the monolith into a microservices-based architecture — i.e., don’t use microservices until your use-case and scaling demands require them. But is this viewpoint still correct?
Communication Design Patterns for Microservices
In this session, we will explain the various communication design patterns for microservices running at scale.
Learnings from CNCF's Envoy and OPA Creators Matt Klein and Tim Hinrichs
Applications architected as microservices are becoming more prevalent every day, but just like their monolithic ancestors, microservice applications must adhere to organization-wide constraints around compliance, security, performance, etc. Authorization — controlling which people and machines can perform which actions — is a foundational security problem that requires new solutions in a microservice world because of changes in requirements around performance, availability and even where authorization gets enforced architecturally.
Microservice Authorization with Open Policy Agent and Kuma | Kong Summit
Applications architected as microservices are becoming more prevalent every day, but just like their monolithic ancestors, microservice applications must adhere to organization-wide constraints around compliance, security, performance, etc. Authorization, controlling which people and machines can perform which actions, is a foundational security problem that requires new solutions in a microservice world because of changes in requirements around performance, availability, and even where authorization gets enforced architecturally.