Native and Non-Native SAP HANA Application Architecture
Native and Non-Native SAP HANA Application Architecture Non-native SAP HANA Application Architecture
Popular posts from this blog
SAP HANA ARCHITECTURE
SAP HANA DATABASE ARCHITECTURE Ø It is more than a DB-it's a true platform Ø Converged OLTP + OLAP Ø It supports Transactions, analytics, predictive, spatial processing transformed for real-time business operations, etc. Ø It supports any application, I mean .Net, java, ABAP, PHP developers can make hana as their db by replacing their existing db Ø It is http-based UI, no External app server Ø UI rendering is completely in the client side Ø Server-side procedural logic in JavaScript Ø 60% of SAP HANA use cases are outside the SAP landscape
Column Store vs Row Store
E.g.: If you want to select country as JP and product is Alpha then traditional db with row store will read all the rows one by one and reach our query what we want. but with column store it won't read all the rows in sequence manner instead it selects the particular column. by this way we will get our result faster with in less time. Why data comes faster from RAM? Take an example if you play songs from your hard drive it takes less time instead of playing songs from DVD drive , external disks or pen drive, because it takes time to read from disk . If data present in RAM then we will access to reports within seconds by columnar hana db and calculations can be done on fly.
Comments
Post a Comment