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 – 3rd party developers in the case of public APIs, your own developers in the case of internal APIs – and achieving adoption requires careful planning at the outset. If you’re looking to improve an existing API, launch a new API initiative or just drive more adoption of your APIs, take a look at MuleSoft’s latest whitepaper – “Secrets of a Great API”.
This whitepaper provides a set of guidelines to help you deliver winning API programs. In it you’ll learn what developers want, how to design for great user experience, proven strategies for driving developer adoption, and how to make your API stand out from the crowd. Get started by downloading the whitepaper today »
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.
A strong ESB will support a broad range of standards, protocols, and adapters, enabling integration of services and applications written in any language or platform. A Best of Breed ESB doesn’t care if the services it is connecting are written in Java or C#.
- A Best of Breed ESB will enable the majority of integration work to be done through tools that are easy to learn and provide visibility into what is happening in the ESB, rarely requiring developers to write or debug code.
- Java and C#, the predominant languages in the enterprise, are nearly identical in syntax.
So how should you choose the best ESB solution? As you begin the journey to evaluating your next generation integration platform there are critical components that will help you connect, implement, and deploy faster:
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.
MuleSoft has released a whitepaper that explore the reasons for migrating from WebLogic to Tomcat, considerations for making the decision, and techniques to be followed for a successful migration.