Skip to main content

Is SAP really taking any real advantage of Hadoop

By Desk Editor

There have been numerous enterprise projects which have been taken up with Hadoop ecosystem offerings. One of the grey areas however remains integration with commercial ERP like SAP. There have been a few good integrations but has there been a pure Hadoop implementation exploiting the raw power of MapReduce beyond just data collection. Do you know of any such successful implementation? If so, do send in your comments.





Meanwhile let us explore Zettaset’s SAP HANA integration offering. Zettaset offers a wide range of enterprise solutions for Hadoop and its integration catalogue features the Who’s Who of the industry.

But we are not talking about the company here in this post, just about SAP integration <period>.

Let us run through the offering charts to understand ‘what’ and ‘how’ of the offering – and if you say ‘over-engineering’ or ‘over-kill’ while reading through, just come up with something more exciting.






Labels:

Comments

  1. The charts definitely demonstrate a good integration architecture but also expose wide disconnect between the efficient Hadoop and comprehensive SAP ecosystems. What SAP HANA is being used for in the architecture seems to be like using F1 car technology for a golf cart.

    A large part of the murmured reason for disconnect remains non feasibility in re-aligning SAP architecture per the custom architect and developer needs. While this may suit the needs of licensing regime and proprietary software needs of a commercial software maker, it also limits innovation options. So at best, we have an integration option which limits what can be done and leaves a whole black box world to what cannot be done. We still need to see beyond the charts of marketing seminars…

    ReplyDelete

Post a Comment

Popular posts from this blog

In-memory data model with Apache Gora

By Sachin Ghai
Open source in-memory data model and persistence for big data framework Apache Gora™ version 0.3, was released in May 2013. The 0.3 release offers significant improvements and changes to a number of modules including a number of bug fixes. However, what may be of significant interest to the DynamoDB community will be the addition of a gora-dynamodb datastore for mapping and persisting objects to Amazon's DynamoDB. Additionally the release includes various improvements to the gora-core and gora-cassandra modules as well as a new Web Services API implementation which enables users to extend Gora to any cloud storage platform of their choice. This 2-part post provides commentary on all of the above and a whole lot more, expanding to cover where Gora fits in within the NoSQL and Big Data space, the development challenges and features which have been baked into Gora 0.3 and finally what we have on the road map for the 0.4 development drive.
Introducing Apache Gora Although there are var…
4 comments
Read more

Amazon DynamoDB datastore for Gora

By Sachin Ghai
What was initially suggested during causal conversation at ApacheCon2011 in November 2011 as a “neat idea”, would soon become prime ground for Gora's first taste of participation within Google's Summer of Code program. Initially, the project, titled Amazon DynamoDB datastore for Gora, merely aimed to extend the Gora framework to Amazon DynamoDB. However, it seem became obvious that the issue would include much more than that simple vision.

The Gora 0.3 Toolbox We briefly digress to discuss some other noticeable additions to Gora in 0.3, namely: Modification of the Query interface: The Query interface was amended from Query<K, T> to Query<K, T extends Persistent> to be more precise and explicit for developers. Consequently all implementors and users of the Query interface can only pass object's of Persistent type. Logging improvements for data store mappings: A key aspect of using Gora well is the establishment and accurate definitio…
1 comment
Read more

Data deduplication tactics with HDFS and MapReduce

By Desk Editor
As the amount of data continues to grow exponentially, there has been increased focus on stored data reduction methods. Data compression, single instance store and data deduplication are among the common techniques employed for stored data reduction.
Deduplication often refers to elimination of redundant subfiles (also known as chunks, blocks, or extents). Unlike compression, data is not changed and eliminates storage capacity for identical data. Data deduplication offers significant advantage in terms of reduction in storage, network bandwidth and promises increased scalability.
From a simplistic use case perspective, we can see application in removing duplicates in Call Detail Record (CDR) for a Telecom carrier. Similarly, we may apply the technique to optimize on network traffic carrying the same data packets.
Some of the common methods for data deduplication in storage architecture include hashing, binary comparison and delta differencing. In this post, we focus on how MapReduce and…
Post a Comment
Read more