1 / 17

Frying your infrastructure

Frying your infrastructure. Are RDBMS really useful in a distributed realtime enterprise system ?. Overview. Quick SAP application infrastructure runthrough SAP application evolution: Enterprise Services & Smart Items Oops: frying the old infrastructure

quilla
Download Presentation

Frying your infrastructure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Frying your infrastructure Are RDBMS really useful in a distributed realtime enterprise system ?

  2. Overview • Quick SAP application infrastructure runthrough • SAP application evolution: Enterprise Services & Smart Items • Oops: frying the old infrastructure • Lessons from the Web Services rewrite • Conclusions and SAP Research ideas

  3. SAP: Lots and lots of business applications...

  4. ...on a common infrastructure • Portal (People, Roles, KM, Collaboration) • Exchange Infrastructure (Process Integration, Messaging) • Business Warehouse (Analytics) • APO (Planning, Optimization) • Search (TREX) • Web Application Server (Everything...) • (i.e. SAP takes a pretty broad definition of „application server“)

  5. Connectivity Layer Web Client Web Browser Internet Communication Manager (HTTP/SOAP/etc.) Integration Layer Presentation Layer (JSP/etc.) • Presentation Logic • Navigation • Interaction with Client • Integration Tools: • Java Connector • .NET Connector • XML/XSLT • SOAP • WSDL Proxies • BAPI/RFC • IDoc • etc. Dispatcher Dispatcher Business Layer (J2EE/ABAP) • Business Logic • Status Administration • Locking/Enqueue Dispatcher Persistence Layer Database Interface (JDBC/OpenSQL) Anatomy of a workhorse: SAP Web Application Server Web Application Server ABAP/J2EE Database Server

  6. Remarks on SAP Applications • SAP Web Application Server • Very robust, complete resource isolation (even for J2EE) • RDBMS (ab-) used as a persistence layer for almost everything • Not particularly lightfooted • Heavyweight sessions • Accrued portability layering over the years • SAP Application Design • Database transactions only used for error rollbacks • Locking mostly handled at AppServer level (Enqueues) • Isolation mostly handled at application level

  7. Global Industry Survey: The world in 2010 Interviewing more than 4000 executives and managers • The ability to adapt strategy and business models quickly will be a critical source of competitive advantage • Firms will focus increasingly on speed of innovation and customer retention to create long-term value • Market consolidation will continue, lots of mergers and splits • People are the biggest asset and the biggest cost factor

  8. Flexibility: From monolithic applications to Web Services Information Technology Solutions Process InnovationSolutions UI UI UI Composite Application Functionalcomponents SAP NetWeaver DB DB • 3 tier applications • Coded transactions • Best practices • Service-oriented applications • Model-driven applications • Best practices and platform

  9. Attaching the real world: Eliminating media breaks Manual data entry Voice input Barcodescanning Smart Items RFID • Digital world („Bits“): • Inter- and cross-company information systems (e.g.: ERP systems) • Local, regional and global communication networks (e.g.: Internet) • Physical world („Atoms“): • Human beings • Products • Production means State-of-the-art Next Generation Smart Items Degree of automation Source: M-Lab, 2001 (http://www.m-lab.ch/)

  10. Performance matters: Realtime Application Scenarios • Asset Tracking • Hospital inventory • Machines and parts • Supply Chains • Emergency Response • Vehicle dispatch & tracking • Workplace safety • Security • Behavior mining • Intrusion detection

  11. Putting it all together: Retail example Global Master Data Management (Exchange & Consolidation) Multi-Channel Sales Operations Store Operations Business Data Warehouse e-Commerce,Catalog &Call Center In-StoreCustomer Service CustomerLoyalty Mgmt StoreInventory Mgmt POS CustomerOrder Mgmt PersonalizedPromotions StoreWorkforce/Task Mgmt Demand Intelligence & Analytics Demand Forecast Collaborative Collaborative RevenuePlanning & Optimization Multi Echelon Inventory Planning & Optimization Merchandise & Assortment Planning & Optimization Workforce Planning & Optimization Collaborative Enterprise & Merchandise Operations RetailMaster Data InventoryMgmt EnterpriseOperations OperationalPurchasing Finance HumanResource … Sourcing Distribution Center Operations SupplyPlanning Supply ChainEvent Mgmt WarehouseManagement Product Design & Introduction Multi-ChannelOrderFulfillment Foreign TradeManagement TransportationManagement

  12. Infrastructure challenges • Event Rates • Hundreds of readers in a warehouse • Bursts of hundreds of events per reader per second • Reaction times on the order of seconds in some scenarios • Data Volumes • Billions of objects in a large organization (retail forecast & replenishment) • Some organizations are required to maintain history over 3 or more years • Analytics need to deal • Cost efficiency • Sometimes do this on a shoestring budget • Deal with unpredictable load patterns (the curse of business flexibility) • Keep it all manageable

  13. Net result: Frying your infrastructure • General purpose RDBMS no longer a good fit for these tasks • Good at • Transactions on a few records at a time • Search with well (pre-) designed queries • Not so good at: • Very long running transactions • Mass operations • Ad hoc analytics • Streams

  14. Business Process Platform: The big rewrite

  15. Observations from the Enterprise Services rewrite • You can do without distributed transactions for even very complex business systems • Database-based consistency can be replaced with message-based consistency • Extremely stylized use of DB • model generated • transaction design patterns • A lot of DB functionality factored out (by design): • No cross-component transactions (design rule) • Search (capturing updates allows for separate engine) • Analytics designed for separate engine

  16. SAP Enterprise Services • SAP comitted to Enterprise Services across the board • New design opens up lots of flexibility in the lower stack • Sufficiently coherent data replication in multiple special purpose engines possible • Web services semantics require application level recovery already, negating a lot of RDBMS „comforts“ • Special engines already (partly) there: • Search (TREX) • Analytics (EUCLID) • Planning/Optimization (APO)

  17. Research Idea: Special purpose engines for everything • Mass operations (prediction) • Computation -> Data (integrated processing, LiveCache) • Data -> Computation (mass data services, SAP Research) • Streams • Luckily, not yet a big problem for us (other than prediction) • SAP Research looking for partners • Very fast „simple“ RDBMS for the rest • Fast keyed search, update • Speaking of device evolution: Give me a few Mbyte of MRAM per machine

More Related