Archaic 6-12 month development cycles are becoming non-existent, as the traditional development landscape has faded away in favor of agile on-demand operations. On-demand cloud platforms (Platform-as-a-Service) have been introduced, able to securely integrate with existing on-premise backend systems. It is now commonplace for development cycles of less than 90 days, and as such developers must adapt and react on a daily basis to changes.
30. Thank You!
Steven Taylor
HANA Cloud Platform Evangelist
email : steven.taylor@sap.com
Twitter : @hashneo
Linked-In : Steven Taylor
Notas do Editor
Initial goal was to create standard software for real-time data processingConvert tape based systems to disk based mainframes utilizing databases.
R/3 Is the base platformABAP is the core language
All Proprietary
What doesthe enterprise look like? -Brief overview. - ERP - CRM - SCM - Tend to be massive. 50+ productive landscapes.“Do not disturb” - Regulatory requirements. - Small changes on backend impact front end processes. - Could shut down manufacturing Applications never seem to “retire” - Stifles Innovation. - Apps have a 20+ year lifespan.Integration between systems. - Sharing of data between systems - Performance degrades with more complexity.Not modular. - Difficult to update / patch.Customization -Affects upgrading.Mergers - Example airline booking systems. - Non compatible technologies, protocols. Global companies - Geo Distribution. - Localization. - Currencies. - Cultures.
To Restrictive - You had no control over the system - Very little customization
Way too flexible - You had to de everything
Seems to have found the middle ground - PaaS is IaaS + Services
Where did all all those development requirements docs go? - Times are heavily compressed - Prototyping to production - fail fast, fail often - Developers have to get it right the first time.Purpose Driven Apps are coming back (Mid-Late 90's). - Applications are becoming commodities.Running Applications in the Cloud - Amazon VMs - PaaSDevOps Developers run what they write.Mobile firstApplications are built for mobile vs desktop More and more business users are mobileREST is the new IPC. - Think API before anything.-No longer are we thinking only about SOAP. - Discovery services. - Session handling is heavily reduced. - Applications servers do not hold paging data.APIs’
Lots more open sourceFar more layered, compacting stacks into single nodes
SAP HANA Cloud is a coherent, modern, services-based platform; showcasing a database and platform as a service optimized for the widest audience of developers building cloud applicationsThe platform consists of:SAP HANA DBServicesis a database-as-a-service offering HANA in the cloudSAP HANA AppServicesis an platform-as-a-service that provides native HANA and other development environment services. Additionally, it provides access to:Cloud Enablement Services provide access to commonly used services for tenant management, administration and monitoring etc.Shared Services enable cloud applications to build portals, collaboration, commercial services to connect to sap store etc.SAP HANA Cloudaggregates a subset of services from the major component blocks to deliver application platform services for Java today and other languages in the near future
Revise based on new architectureLet’s start with a high-level overview on the SAP HANA Cloud Connectivity service. There is the on-demand side, the data centers operated by SAP Cloud, on the upper part of the picture. On the lower part you can see the customer network, i.e. the on-premise side. So at the top we have the SAP hosted platform, at the bottom we have the customer, and in between there is the Internet. In the cloud, SAP HANA Cloud , the Java-based Platform-as-a-Service is running, while on the customer side there are all types of customer backends, like a SAP ERP system, NetWeaver Gateway, CRM systems, Enterprise Portal, or other non-SAP systems. The question is how you can provide an on-demand application running on Neo which makes use of the existing customer system, and by this allows to leverage the made investments on the on-premise side to new on-demand applications? This is where the Neo Connectivity Service comes into play: SAP HANA Cloud provides the SAP Cloud Connector as the connectivity component on the on-premise side which allows to connect to SAP HANA Cloud on the cloud via a point-to-point SSL tunnel. On the on-demand side, there is the SAP Cloud Connector On-Demand as counterpart to the on-premise component, but this is completely transparent for a consumer (it is operated by Neo in the cloud). Right now, this infrastructure is used for SAP HANA Cloud only, however it is the goal to extend the use case as following: The SAP Cloud Connector On-Demand should serve as single exit point for all SAP On-Demand applications, while the SAP Cloud Connector serves as single entry point to all customer backend systems. This means that we want to extend the usage of the Neo Connectivity service also for other SaaS or PaaS offerings hosted in the SAP data centers. The Neo connectivity service provides API which can be used by the applications to make calls to on-premise systems. This API is the destination API. It makes an HTTPS call to the SAP Cloud Connector On-Demand, where it is sent via the SSL tunnel to the SAP Cloud Connector on the customer side. Here, additional checks like whether the current request is allowed to access the backend are performed. If the tests succeed, the request is forwarded via HTTPS to the targeted backend system.
CMIS is an OASIS standard that is widely supported by the ECM industry. It defines an abstraction layer for controlling diverse document management systems and repositories using Web protocols. CMIS defines a domain model and Web services and Restful AtomPub (RFC5023) bindings that can be used by applications. Apache CheMIStry provides open source implementations of the Content Management Interoperability Services (CMIS)
Review with Svetoslav
Opening up the Enterprise market to developers - Traditionally a closed marketProviding the tools / platforms - Reusing standard tools which the Java community understands and usesProvide the store for developer to monetize their solutions - Allow the selling of apps to SAP customers.