API, Microservices and integration

As with all software development it is crucial to implement a solid test framework to verify and adopt when implementing Microservices. And a solid test framework might be even more important when you implement a Microservices strategy. Why? Because an important objective behind the initiative often is to decrease time from development to production and to do this you have to minimize the requirement for manual testing.

”Det ska vara lätt att göra rätt är en devis man ser i allt fler offentliga verksamheters visioner. Nu blir visionerna verklighet för några av våra myndigheter i digitaliseringens framkant.” Det säger Henrik Gavelli, CEO på Redpill Linpro – företaget som underlättar samhällsnytta genom system och tjänster för öppna API:er.

A new strategy to develop software, should be followed by a new strategy to deploy software. And a Microservices initiative constitutes an excellent opportunity to also implement a DevOps approach to hosting and deployment of software, some even say that in order to be successful with a Microservices initiative you will require DevOps. In this blog post we will exploit why this is so and how a DevOps way of thinking can be implemented alongside your Microservices initiative.

What would a Microservice be without means to communicate with it? How do you control who/what communicates with your Microservice and uses its resources? How do you analyze patterns and usage? This is where APIs and API Management comes into play.

For many, this is when it gets really interesting. Based on our experiences and challenges with Microservices, we have put together a number of components and areas that you will need in order to support your initiative.

Create simple guidelines and live by them to successfully implement and maintain your Microservices.

Your great API is finally published – but is it really being used and by whom?

There are few things worse than publishing a new strategy based on APIs just to find out that the tech solution is failing and the way to avoid this is simply - thorough testing.

Can the organisation really have an impact on your Microservices initiative?

Making your corporate data (or parts of it) available to your partners and customers is a matter of balance between openness and security. You want to improve your business by inviting selected participants to interact with you, but what you don't want is to create undesired access to potential trade secrets or material that can be used against you.