API, Microservices and integration
At this years WSO2 EU Con there were a lot of talks on how organic cells are similar to self servicing development teams. An interesting analogy that I thought worth elaborating on. Maybe this is the way forward to further increase development speed and agility, for sure the tools are already there...
Recent analyst reports from Scandinavia and North America, continue to enforce the notion of IT departments being squeezed between resource availability and business expectations. According to feedback from IT decision makers, the discrepancy in expectations from the business and what IT really can deliver continues to grow. This growing discrepancy paired with new phenomenon introduced on the market calls for a revamped view on the future IT strategy and the partners/SIs organisations choose to implement it.
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.