API14 articles

RFC 7807 helps API implementors as it provides quick guidelines to avoid reinventing the wheel on every project.

Let’s use a very simple e-commerce use-case to demo how to implement the Backend-for-Frontend with and without the help of Apache APISIX.

Most modern infrastructures are dynamic – servers are cattle, not pets. In this article, I describe how to implement a dynamic node registry based on a YAML file.

The idea behind BFF is to move logic from each microservice to a dedicated deployable endpoint.

It is more beneficial to use sealed and value class instead of enumerations in Kotlin; let’s find out why.

Almost all Java developers are familiar with logging frameworks like Log4j and the facade SLF4J, but not the System.Logger that has been available since java 9. Let’s learn about the standard.

Learn how to improve the API provided by third-party libraries by combining Kotlin extension functions and delegation.

Serverless data offers benefits, but market offerings are limited. What serverless data can, should, or could do isn’t always understood.

I’d like to describe how to add new behavior to an existing object/type. I won’t use any reactive type to make it more general.

The JVM ecosystem is mature and offers plenty of libraries, so you don’t need to reinvent the wheel. Basic – and not so basic – functionalities are just a dependency away. Sometimes, however, the dependency and your use-case are slightly misaligned.

The correct way to fix this would be to create a Pull Request. But your deadline is tomorrow: you need to make it work now! It’s time to hack the provided API.

In this article, we are going through some alternatives that allow you to make third-party APIs behave in a way that their designers didn’t intend to.