APIWorld 2016 There was a packed room at APIWorld 2016 last week, where I presented on a topic I feel that does not get discussed much. APIs are fast becoming the currency for integration and inventing new business models. Their adoption has been exponential and continues to grow. A lot of companies are gearing towards an “API first” approach to building new capabilities. However, there is very little attention given to create API as a first class capability within an Enterprise.
When Rewriting applications is the only option
Not surprisingly, the most popular way to experiment with containers and experience the full cycle of development and delivery with them is to write an application or two and experiment. However, a lot of developers get trapped in this dichotomy and only want to pursue this path to adopt containers and not consider other options. Maybe because it is much easier to get started this way and perhaps they get an empty canvas to create the next masterpiece.
How to incrementally modernize from legacy?
Sometimes fiddling with critical business applications is not an immediate choice. Maybe because: There aren’t enough people around who know the details, There are too many touch points that will make it fragile to touch the code for even slightest of modifications, There is a lot of business logic in stored procedures or There aren’t good test harnesses that provide enough coverage for us to know that modification in one (or few) part or component doesn’t break something else.