APIs are the new websites, or so says Roberto Medrano, EVP of SOA Software. This being the case, API management has grown to include a widening array of business operations. As APIs are increasingly externalized through Web and mobile applications, and the development process opens up to outside business partners, governance becomes a key factor in security maintenance and lifecycle management. “There are too many cooks and not a good way of predicting who is supposed to be doing what,” Medrano explains. The basic challenge for the enterprise is in finding a set of business requirements that convert to development requirements and ultimately correlate with their API’s deployment — all while maintaining speed, quality and security standards. Too many cooks, indeed.
Furthermore, Medrano pointed out that analytics and, by extension, monetization come into play once the API is deployed. At this point, critical questions need to be asked: What specific aspects of the API are getting used? Which are not? Which are the ones that are generating more revenue? Luckily, these are all issues that SOA Software works to address. This company, a 2013 Gartner Magic Quadrant player in Application Services Governance, developed the Lifecycle Manager to help enterprises automate and manage the development of an API, from design to deployment and, ultimately, to retirement.
Security and compliance are also major concerns, particularly in larger companies where APIs need to support a lot of security protocols. This is where SOA Software’s API Manager comes into play, offering such security features as authentication, cryptography and an authentication server that allows enterprises to manage and operate off of their existing security systems. This is likely why Gartner inc. positioned SOA Software as a leader in their new quadrant category: application services governance. “We have been a leader in SOA governance because of our strength in governing and managing and securing all the stages of the SOA development cycle,” Medrano says. Visibly, the line between API management and SOA governance is blurry. Medrano himself discusses the topic as if they were two sides of the same coin. As companies continue to externalize applications through APIs, the line will likely become murkier still, and SOA Software seems very well positioned to guide companies through the transition.
For more information, please visit SOA Software’s resource center.
What do you think is the biggest challenge facing API management? Let us know what questions you have and what problems you face. We’re here to find you answers.
Global business infrastructure provider Software AG announced its acquisition of JackBe on Thursday, along with the release of its webMethods Intelligent Business Operations Platform (IBO).
In a statement, Software AG said JackBe will serve as the foundation of webMethods IBO, which was developed to “offer customers high visibility and insights into dynamic operations.”
Software AG’s Chief Technology Officer Wolfram Jost said the purchase was designed to help the company keep up with the growing need to handle large volumes of data quickly.
“The amount of produced data is growing exponentially,” Jost said. “Consequently, the analysis and visualization of huge data volumes in real time will become more and more the basis for fast and intelligent business decisions. With the capabilities of JackBe, we will develop further innovative solutions for our customers in order to support their evolution towards the digital enterprise.”
Michael Ogrinz, a principal architect for global markets at Bank of America, shared with SearchSOA the following thoughts on the buyout:
“Software AG’s acquisition follows Kofax’s recent purchase of Kapow Technologies. Both JackBe and Kapow were early leaders in the mashup space before re-branding towards business intelligence, content migration, and real-time analytics. JackBe and Kapow have unique approaches in the areas of data acquisition, analysis, and visualization and this has clearly not gone unnoticed by some of the industry’s big players. With the advent of big data and the new challenges and opportunities it presents, it’s not surprising that both of these companies would be snatched up.”
Software AG purchased webMethods in 2007. After two years of development, Software AG released webMethods 8.0 and integrated a Business Service Repository.
Are enterprises jumping on the mobile application bandwagon? The answer may depend on who you ask. StackMob’s CEO Ty Amell says yes. So much so his company recently engaged in several partnerships in order to bolster its offerings towards the market segment.
Tom Nolle, president of strategic consulting firm CIMI Corp., is skeptical. “I would say this [enterprises adopting mobile applications] is still very much in its infancy,” said Nolle, who believes enterprises are becoming more interested in what he refers to as “point of activity empowerment.” He used this term to describe users getting information they need via a mobile device quickly, whenever, wherever.
What could be fueling this movement? Nolle believes companies, not as an objective, are moving towards a mobile environment. “Companies are trying to make workers more productive and in their drive to do so, they are certainly more than willing to consider adopting practices that are mobile specific,” said Nolle.
Amell’s company is betting on geolocation, custom analytics, and distribution functions to be big with clients. Could such feature adoption be necessary to forge ahead? Nolle isn’t sold, saying the benefits of things like geolocation are highly dependent on the type of organization.
The fact that there isn’t a lot out there for mobile at this time, might be what is ultimately hindering adoption. “The challenge for companies at this point is that there is no convenient way to integrate mobile devices into their current application and worker empowerment practices because the mobile devices of today don’t consistently expose their features though browsers so that they are accessible applications,” Nolle said.
“What we are seeing is that an improved coupling of device features through the browser rather than custom APIs is making mobile device information more accessible, that is facilitating the development of fusion apps and that is probably going to be the driver to expansion and point of activity empowerment.”
Enterprise mobile applications are stepping into the spotlight, seriously catching the eyes of clients looking to gain more insight into their consumers, according to StackMob, a cloud-based backend for mobile applications.
“We’ve seen a drastic upset over the last few months in terms of enterprise clients,” said StackMob’s CEO Ty Amell. “I think you are seeing the shift of enterprise from discovery mode to more of a buying mode.”
The company recently joined forces with Keen IO, GeoLoqal, and Carrot, Inc., to meet the needs of the burgeoning market. Keen IO specializes in helping developers build custom analytics while GeoLoqal allows for geolocation functionality. Carrot is designed to facilitate distribution.
Amell said the move was made in response to feedback StackMob was receiving from its developer ecosystem both in retail and enterprise. The three main issues, he said, that have been echoed across the board are those the aforementioned companies cater to.
“It’s really important for any business to understand what their funnel looks like and a custom analytics mechanism, like Keen, will allow you to do that,” said Ammell. “That is what we’ve heard the most, the ability to keep track of and understand their funnel. There are a lot of services out there for the Web, but not a lot out there for mobile.”
Geolocation is a way for merchandisers to better reach, and understand, consumers on the fly. “If you are retailer X and you know someone is in a mall that has one of your stores, and if you know they like you, why not give them a message and entice them to come into the store to buy something?” said Amell. “That is a lot of the geo stuff we are seeing.”
Another area many companies are struggling with is distribution. If you think about the number of applications there are, standing out and being chosen can be an uphill battle for any developer, said Amell.
Migration efforts can seem daunting, but upgrading legacy databases isn’t an impossible task. During the “Mainframe and Database Legacy Modernization” session at Red Hat Summit 2013 in Boston, Red Hat services delivery manager Emily Brand likened the process to peeling an onion.
“Every layer you pull off, try to remove the layers of the legacy,” she said Wednesday morning.
To get started, Brand recommended people begin with analyzing their current infrastructure and then think about the ultimate mission they are trying to accomplish. This is how one begins to map out a plan to make their goals a reality.
Brand said, “Ask yourself, what does your environment look like? Is it monolithic or do you have a bunch of scattered databases and applications?” She noted it’s difficult to move a project forward when there are multiple versions of everything.
Throughout her session, Brand touted the benefits of enterprise data services (EDS), saying the platform makes it easier to move to more modern middleware. She said an EDS can be a layer above databases that can integrate multiple data services or just be a layer between them.
It’s also important for people to standardize databases to the version they want, choosing as few as possible. Middleware, programming languages and SOA governance also need to be standardized, Brand said. The more stringent one is with frameworks and languages, the more agile developers can be within an organization.
There are, however, times when flexibility is key. By allowing for exceptions, one can maximize IT infrastructure, Brand noted, “Instead of being a maintenance machine, you can be a development machine.”
There are several benefits to modernizing legacy databases that make taking on what may initially seem like a scary migration effort worthwhile, even from an ROI perspective. Brand said some of them include:
- - Decoupled business applications from several sources
- - Isolated data layer
- - Companywide semantics
Don’t just work with the present in mind, perform work anticipating future needs. Everything should be able to talk everything else in a way that can easily be tracked, Brand said. This is because ambiguity can lead to unnecessary headaches. “Think 10 years down the road,” she said, elaborating that new employees will be forced to deal with the ramifications of whatever decisions are currently be made.
Enterprise demand for Mobile Backend as a Service (MBaaS) has been gaining traction, according to StackMob, a back-end technology stack for mobile applications. BaaS has been touted as an inexpensive method to improve scalability, flexibility, and security by the technology’s advocates.
StackMob recently teamed up with Rackspace, an open cloud company, to help capitalize on the trend.
“Enterprise for the first time is completely rethinking how they are developing applications, which is very exciting because as far as I’m concerned, this hasn’t happened before,” said StackMob CEO Ty Amell in an interview with SearchSOA.
Amell likened the innovation and growth in the mobile ecosystem to the Industrial Revolution.
“If you look at what happened back in the Industrial Revolution, there were standardizations and factories that allowed people to build things like never before,” said Amell. “Fast forward to today and we have a Tech Revolution… we have all of these BaaS providers with niche services, all providing great services and then we have APIs allowing systems to talk to each other. For the first time we have a standard service.”
Furthermore, Amell said the movement is something that won’t take several years to catch on and more to implement, rather he foresees it as a fast-moving market.
The growth should come as no surprise given that data from Strategy Analytics indicates that over the next five years, revenue associated with mobile workers using enterprise business apps will nearly double.
“Mobile workers have moved beyond just mobile email and messaging to include other collaboration apps such as conferencing, productivity apps such as content authoring, and business process apps such as CRM and even ERP,” said Strategy Analytics director of business cloud strategies Mark Levitt in a statement.
Do It Yourself (DIY) television shows have proven popular with audiences, but the same “I can save myself money by doing it on my own,” mentality that makes for good entertainment, may not be so amusing when it comes to OSGi server runtimes.
During his lecture, Ward talked about how those who enjoy DIY projects will like OSGi because it’s all about modularity. “It’s very easy to build a server runtime from a freely available piece,” he said. “OSGi makes it simple to reuse components, but do you want to do this?”
If an application architect decides to go the DIY route, there are several options to choose from. Among the platforms are: Eclipse, Apache, Aries, JBoss, GlassFish and IBM Websphere, explained Ward.
There isn’t a cut-and-dry answer to what features should be used. Just like the many aforementioned platforms, each scenario needs to be looked at independently.
Ward advised session attendees to ask themselves, “What do you want from your runtime?,” he asked. “You need to answer this question first. Is it a development stack for playing around with?”
Ward also advised people to consider the following:
– Do you want to learn? You’ll gain the most knowledge if you build it yourself;
– What kind of time do you have? You’ll make the fastest progress using a pre-built offering;
– Is it a small/medium reduction system with a small feature set?
Even though each situation has its own circumstances, there are some general rules to follow. Ward suggested that for those creating an application that needs a lot of features, building their own runtime isn’t a wise decision. He asserted that in such a scenario, developers should save themselves time and pick a pre-built runtime that offers the necessary services.
Another situation where building a runtime can also be a poor use of resources is when an application needs to run on three or more nodes. Again, Ward said this is a scenario where it’s better to fork over some cash. The combination of deployment, management, and monitoring will be big issues.
Ward’s closing piece of advice was this, “Mostly, pick an option that’s designed for your requirements. The number of people who don’t do this is crazy!”
For enterprise architects, taking an “out with the old, in with the new” mentality can be tempting when modularizing large legacy Java applications, but that could be a mistake. That’s according to Vineet Sinha of Cambridge, Mass. –based Architexa.
During a EclipseCon 2013 session March 26 in Boston, Sinha cited some pretty staggering statistics. Among them was one he attributes to IBM, which says up to 90% of a developer’s productive time is spent trying to understand code.
Devoting even half your time unraveling a mess of code can be daunting, admitted Sinha, but that doesn’t mean developers should try to reinvent the wheel. Rewriting code can be costly and time consuming. Instead, he offered some pragmatic advice that starts with building architectural maps. It’s not uncommon for team members to have different pictures of a project’s main components.
“Even if you have 100 developers, get the team leads into the same room,” Sinha suggested. Armed with old-fashioned paper, the participants should document the top components and connections between the components. “I’m essentially saying; try to get them to merge their ideas.”
This exercise helps make sure everyone is on the same page. “The first time we did it we split the things we agreed upon,” said Sinha. “We had a whole list of things we needed to think about the next time. One hour and we had that.”
Writing on a whiteboard may also prove beneficial in helping people understand a system. Sinha noted how people in his organization began to plan around what they saw on the board.
With everything clearly documented, the team will have a more central view and will have an easier time obtaining necessary information down the road. “If you are writing any new code, you are not putting it in the wrong place,” said Sinha.
While untangling the web of code implemented by someone else may seem like a thankless task, it’s important to remember what you are doing can be extremely difficult. Setting aside time on a regular basis, whether it be at the personal or team level, for fixing is also important.
Sinha offered another commonsense tip: celebrate your successes. Even the smallest victories are meaningful as they can be used as stepping stones towards long-term goals.
Want a challenge? Add the avalanche of enterprise mobile applications to DevOps teams’ already-daunting integration workload, Paul Kopacki says. He’s Sencha’s vice president of marketing, which just released a mobile app integration tool for developers.
Last week, Sencha Inc. of Redwood, Calif., released upgrades to its product line designed to make HTML5 development more simplistic. The company’s core offerings–Sencha Architect, Sencha Ext JS and Sencha Touch–have been enhanced to make it easier to quickly build HTML5 applications for any platform. A new touch bundle for mobile developers was also launched.
Among the key upgrades to the Sencha ExtJS product is a big-data grid. “There are many more data points people want to build into their applications,” Kopacki said in an interview. “Big-data grids are one of the things customers are asking for and we are delivering in this release.”
Financial data companies are among those who rely on the technology on a daily basis. One Sencha client used the technology to build an app for bond traders. The client company, which tracks a great deal of information, needed greater capacity to take the data and share it with its bond traders in a faster pace.
Online accounting software company Xero has also embraced the technology. The company’s CTO, Craig Walker, said a few years ago that he realized Xero wasn’t delivering a positive mobile experience. “Our experience had been with native development and we wanted to move to Android, etc. The mobile touch framework delivers a lot of functionality up front,” he said during an interview. “What would have normally taken us six to nine months took us three.”
While there has been some debate over HTML5, Sencha has a clear stance on the technology: It’s a big proponent. In fact, the company recently developed a copy of the Facebook app to show that developers, not HTML5, were the issue when Mark Zuckerberg abandoned the markup language last fall.
“Some people come to HTML5 from a web perspective and fail to see the power of HTML5,” said Kopacki. “If you come at it from an application development perspective, you use the right tools so that HTML5 is powerful, especially for business applications.”
While the debate over HTML5 is sure to rage on, at least for now, some companies are banking on its ability to quickly aid programmers as they integrate old systems with new technology.
Running through the history of computing is a quest for modularity. We curse it when it doesn’t work; we take it for granted when it does. Long ago, software engineers began to seek the equivalent of Lego bits, software modules that could be swapped much like bus boards on a hardware backplane. It’s been a long strange trip.
Modularity has gone through various stages in the modern era, with objects, components and, then, services, coming to take the place of Lego pieces in the software world. But, even in one of their (somewhat) recent iterations – that is, the services-oriented OSGi Service Platform – the mechanics software module interaction is not easy for developers or architects to master.
“Java Application Architecture” (Prentice Hall, 2012) by Kirk Knoernschild is one of the more probing books you are likely to find on this subject. Before the year past is very far past, I would like to take some time to discuss the book , as it is one of the better ones I have read lately.
The book has a straightforward principle, which is to provide guidance for those who might set out to design modular software. In Knoernschild’s terms, it looks at ways you can “minimize dependencies between modules while maximizing a module’s potential reuse.” This is, one, a major goal of middleware; and two, a long-time holy grail of software development.
While much of the book portrays garden-variety java problems, a fair amount of “Java Application Architecture” which is subtitled ‘Modularity Patterns with Examples Using OSGi’ also has a helping of OSGi know-how.
A conversation with Knoernschild disclosed that the book arose from an initial interest in uncovering how to leverage different layers of abstraction – to reach a deeper understanding of software architecture, and gain ease of maintenance. Composition of “Java Application Architecture” happened over many years, and there were discoveries.
“Along the way, the book morphed based on me learning more about how to design large software systems based on the Java system, with JAR files as the principle unit of modularity. Then, in the 2006 time frame, I discovered OSGi,” said Knoernschild, “I started digging into OSGi.”
He said he found the ideas of OSGi meshed with his own ideas about Java modularity in general. OSGi, for example looks at JAR files as the main means of re-use, treating a JAR file as a first class citizen. In the book, he explains how to take a monolithic application, modularize it and eventually bring it under the control of OSGi.
At heart, the issues Knoernschild addresses in “Java Application Architecture” are about dealing with complexity. Like Fredrick Brooks’ work, you could say Knoernschild’s effort is to separate the accidental complexity from the essential complexity. His thoughtful look at Java modularity is more than just tools and tricks – it is a foundational framework for thinking about problems of software architecture.
“Designing software is hard. It’s hard because breaking up the systems is so difficult,” said Knoernschild. OSGi’s detractors still argue that it, in itself, in fact, is too difficult. But experience tells us things are hard for a reason, and while the general drive of software is to make things easier, it is a daily battle to effectively simplify the complex. Knoernschild’s book, fights the good fight, and could become a valued companion at many developers’ bench tops. All and all, it is a brilliant breakdown on modularity.