Cloud computing is the new normal in software development.
Whether you’re shifting application workloads to the Cloud, building new Cloud Native apps, extending to Mobile or embracing the future of Intelligent Chatbots, this book includes contribution from Oracle partners and experts, offering tips and opinions based on their professional experiences with their customers, on how to successfully embrace the new normal in the cloud.
There are many reasons to develop and test in the cloud, driven in part by the need to
deliver software solutions faster and more cost effectively. The so-called Digital
Transformation is enabled by a handful of processes and technologies, like continuous
integration, DevOps, application release automation, continuous delivery, and Agile and
Lean.
The time to adopt these agile processes, tools, and technologies is now. This handbook
will help the audience understand what they are, why they provide value, and why Oracle
Cloud is a key enabler to anchor your strategy related to digital transformation.
Oracle provides a comprehensive and integrated cloud platform, including IaaS, PaaS, and
SaaS. This architectural approach significantly differentiates Oracle from other cloud
platforms by allowing customers to leverage each layer of the cloud stack to maximize
the strengths of every other layer.
The key challenge with mobile is to write APIs that are mobile optimized and that allow you to use different clients with them. For example, you access an on-premise SOAP API that you need to transform to REST and JSON to be useful with mobile. This is what you do with custom API (API A) in MCS. However, MAX has a different requirement to an API than JET (and I think ABCS has it as well). So you will create a MAX (Express) API (API B) and build it on top of the custom API (API A) you built to access the SOAP API. This then allows you to optimize for MAX and ABCS. JET could work directly with API A unless you find a reason that requires API shaping for JET. If you add bots to the picture then you would build another custom API (API C) that you base on top of API A. Since Oracle ADF REST consumption works best with ADF BC REST style, you could imagine a custom API (API D) that also sits on top of API A to transform it to the ADF BC style.
The key challenge with mobile is to write APIs that are mobile optimized and that allow you to use different clients with them. For example, you access an on-premise SOAP API that you need to transform to REST and JSON to be useful with mobile. This is what you do with custom API (API A) in MCS. However, MAX has a different requirement to an API than JET (and I think ABCS has it as well). So you will create a MAX (Express) API (API B) and build it on top of the custom API (API A) you built to access the SOAP API. This then allows you to optimize for MAX and ABCS. JET could work directly with API A unless you find a reason that requires API shaping for JET. If you add bots to the picture then you would build another custom API (API C) that you base on top of API A. Since Oracle ADF REST consumption works best with ADF BC REST style, you could imagine a custom API (API D) that also sits on top of API A to transform it to the ADF BC style.