Skip to main content

Is SAP really taking any real advantage of Hadoop


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.






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

Low latency SQL querying on HBase

HBase has emerged as one of the most popular NoSQL database offering distributed, versioned, non-relational tables hosted on commodity hardware. However, with a large set of users coming from a relational SQL world, it made sense to bring the SQL back in this NoSQL. With Apache Phoenix, database professionals get a convenient way to query HBase through SQL in a fast and efficient manner. Continuing our discussion with James Taylor, the founder of Apache Phoenix, we focus on the functional aspects of Phoenix in this second part of interaction.
Although Apache Phoenix started off with distinct low latency advantage, have the other options like Hive/Impala (integrated with HBase) caught up in terms of performance?
No, these other tools such as Hive and Impala have not invested in improving performance against HBase data, so if anything, Phoenix's advantage has only gotten bigger as our performance improves.  See this link for comparison of Apache Phoenix with Apache Hive and Cloudera Im…

Data deduplication tactics with HDFS and MapReduce

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…

Pricing models for Hadoop products

A look at the various pricing models adopted by the vendors in the Hadoop ecosystem. While the pricing models are evolving in this rapid and dynamic market, listed below are some of the major variations utilized by companies in the sphere.
1) Per Node:Among the most common model, the node based pricing mechanism utilizes customized rules for determining pricing per node. This may be as straight forward as pricing per name node and data node or could have complex variants of pricing based on number of core processors utilized by the nodes in the cluster or per user license in case of applications.
2) Per TB:The data based pricing mechanism charges customer for license cost per TB of data. This model usually accounts non replicated data for computation of cost.
3) Subscription Support cost only:In this model, the vendor prefers to give away software for free but charges the customer for subscription support on a specified number of nodes. The support timings and level of support further …