All API & Microservices Content

Apidays NYC 2022: Friends Don’t Let Friends Centralize Authorization Enforcement

Achieving an identity-centric security model is no small feat. The composable enterprise needs to be secured across multiple clouds, while providing end-users with delightful experiences, yet still maintain high levels of assurance. Oh yea… it has to scale too. This presentation shares lessons learned from our journey towards automating the distributed enforcement of access control rules, and how leveraging a symbiotic relationship between identity management and runtime API security infrastructure enables an identity mesh that spans across applications.

Three Questions for API Change Management

Adam’s latest blog discusses API Change management and how it allows us to create a process or a set of rules that shapes the way the API grows as more endpoints are added and as existing functionality changes. He then discusses the three factors to consider whenever making changes to an API.

Anti-patterns in Microservices (Don’t Do These)

Microservices are a popular approach to software architecture that aim to break up monolithic code into maintainable chunks. These discrete chunks allow for continuous delivery of a service while developing on top of what is in production. That flexibility is exciting in an agile environment, but rushing into deploying your code as a suite of microservices can put you at risk of incorporating anti-patterns that may cause significant problems down the line. In this blog, Adam discusses four common pitfalls as you start building your own microservices. 

What are API Anti-Patterns?

Software design patterns are the solutions used to tackle common software development problems. Design Patterns aren’t strictly required for running code but they are essential to avoiding problems in your code. In this article, Adam takes a look at the other side – anti-patterns – a sneaky but common poor software development technique.