Posts Tagged: microservices

6 Tips to Become a Master Microservice Gardener

The art of providing an API is extremely interesting, largely due to the dichotomy of opposing requirements. On the one hand, an API must be innovative, quick to change, and ever evolving. On the other, consumers demand stability, and with it, the security that comes with proven solutions. Read more

The Benefits of a Serverless API Backend

Imagine if your backend had no infrastructure. No permanent server, nowhere for your API to call home. Sounds a bit bleak, doesn’t it? As it turns out, serverless backends could be the next big thing for implementing truly scalable cloud architecture. Read more

How to Handle Batch Processing with OAuth 2.0

Recently on the Nordic APIs channel we’ve had a few people ask — how do you handle batch processes that are secured with OAuth 2.0? Batch requests are ones executed automatically or programmed to repeat recurringly.

Usually we use OAuth to confirm user identity for API calls, but the problem is that OAuth 2.0 isn’t really designed for batch processing. Read more

Leverage Public APIs

Leverage Public APIs to Make Your System Better

The software world has moved in many ways towards the idea of modularity rather than the archetypal monolith — services and systems are continually developed in chunks rather than as a single system. This has spilled over into many aspects of the API space, and represents a powerful opportunity for developers to not only simplify the development cycle, but to leverage modularity to make their own offerings more powerful. Read more

How to Handle the Continuous Delivery of Microservices

How to Handle the Continuous Delivery of Microservices

The world of API architecture and development is tricky in many ways. Unfortunately, there is no such thing as a “perfect” solution, and with every new implementation or solution, new problems are bound to crop up.

It is important to remember, then, that even the most positive, powerful decisions in API architecture could have significant issues in the long run that, if not recognized in the hazy glow of post-adoption euphoria, could easily interfere with the success of an API or collection of APIs. Read more