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.

Key Use Cases for GraphQL APIs

GraphQL has become a preferred option when flexibility and efficiency are top priorities. GraphQL is also easy to integrate with existing applications, since implementations are available in JavaScript, Python, PHP, and several other languages. Here are three use cases where GraphQL shines. This article highlights three specific use cases where GraphQL shines.

Adapting Continuous API Management for Cloud Architecture

In his latest blog, Adam discusses best practices for Continuous API Management , including several significant ways that drives change when the API is operating on cloud architecture. API management, whether on the cloud or off, comes down to discovery, documentation, monitoring, alerting, and authentication/security. How well you implement best practices in these areas will make or break your service. In this article, we’ll summarize several considerations for adapting to the cloud.