CIOs and IT departments have one common goal: to increase efficiency through technology. One way to reach this goal is by investing in the employee experience. When companies invest in a better digital workplace, their employees become more productive and ultimately drive 30% more revenue growth. Sounds pretty good, right?
But delivering a connected employee experience is hard. Enterprises need to develop applications that are both highly functional and fueled by data.
When EDI first came into use, supply chains were simpler, with a limited number of suppliers. Now, thanks to globalization and specialized manufacturing, there might be hundreds of suppliers in a supply chain. And, as prices change, businesses move overseas, and market conditions evolve, these suppliers change as well.
As mentioned in my first post in this blog series, one of the 10 largest banks in the world found itself burdened with a complex, tightly coupled technology environment, leading to operational inefficiencies, a risk of missing out on new sources of revenue, and losing market share to its competitors.
Tic:Toc, an Australian fintech company, has been working to create a fully automated online home loan application system since its conception in 2015. By removing inefficiencies in the home loan approval and fulfillment process, the company launched its platform in July 2017, enabling customers to easily submit loan applications online to receive instant decisions on their applications.
An architecture needs to bend, not break, as new innovations, best practices, and needs emerge. In this post, I’ll explore the broader landscape we are traveling to support that agility.
SAP ERP is notoriously challenging to integrate with other systems. Thus, SAP integration requires not only the right technology and strategic approach but also a means of enabling your organization to achieve success.
Regardless of how customized your SAP instance(s) may be, or how mismatched the object models may be between SAP and third-party solutions, Anypoint Platform is purpose-built to abstract the complexity of any system and its proprietary language. This results in obviating the need to build with custom code by leveraging an API-led approach.
In the intro to this blog series, I promised to reconcile the apparent incongruence of strategic business objectives (move fast) with traditional IT must have paradigms (be safe). In the last post, we chugged away at the surrounding ecosystem that’s needed to support the velocity promised by the former. In this post, I pause at the pre-production station to discuss some of those system safety properties that we can’t leave behind.
