APIs enable companies to tap into digital assets to create new revenue streams, extend their value proposition through partner-delivered capabilities, and dramatically improve agility and responsiveness to new business opportunities. But APIs are no magical elixir. “Build it and they will come” may work in the movies, but in the universe of APIs, it couldn’t be further from the truth.
The success of an API hinges on adoption by the developer community –
When looking at options for your next generation integration platform, the development language of the underlying ESB should not be a primary concern. .NET teams in particular often constrain their search to only .NET-centric ESBs, ultimately leaving them few options. If you find yourself in this position, here are a few things to consider:
- At its core an ESB is all about interoperability.
While it has been commonplace (and well documented) for IT organizations to migrate Java EE applications initially developed on Apache Tomcat upward to commercial Java application servers, such as Oracle’s WebLogic, in recent years the trend has been reversing. There are a number of compelling reasons for creating new web applications using today’s deployment architectures on Tomcat instead of WebLogic, but perhaps even more interesting is the trend to migrate existing Java EE applications from WebLogic to Tomcat.