I recently visited Switzerland and needed to get to a city in France. To find the best route by train, I used a site called Rome2Rio.com. I like this site because the user experience is intuitive and simple. You just enter in your starting point and destination, and the site quickly provides train, bus, car, and other transportation options with routes and timetables.
It’s really all the information you need to make the best decisions about how to get from point A to B.Back to Switzerland and France. Using Rome2Rio, I entered my current location and destination, selected my route, then clicked on the convenient link to buy my ticket.
It sounds simple enough. But that’s because I was happily oblivious to the complex transactions going on behind the scenes. The journey that the site automatically mapped out for me involved first traveling on the SBB Swiss train, and then changing in Geneva to board SNCF, a train line in France.
Eternally inquisitive, I wondered to myself, how do “they” (SBB and SNCF) work out who gets paid what? What cut does Rome2Rio get for leading the transaction, and how do they get paid? How does Rome2Rio get access to train schedules from multiple vendors and line them up for my desired travel time? How many silos are actually involved here? Don’t forget that these are government train systems, so undoubtedly there are a lot of security concerns, policies, and other compliance hoops to jump through.
On top of that, not only was my Visa card taken to pay for the travel, an extra “certified by Visa” validation process was required. Whew! Like I said, all of the heavy lifting required to plan my journey and make the transaction was hidden from me.
This is the beauty of abstraction. (There is also immense satisfaction in getting exactly what you want.) But because I do this kind of stuff for a living, I knew that to implement the complexity behind the abstraction required integration with multiple silos of train system APIs, commerce APIs, databases, and perhaps CRM and ERP systems, not to mention authentication and authorization layers.
Just like a conductor in a symphony is required to orchestrate beautiful music, a software orchestration was required to integrate multiple data silos and security, all within an easy-to-understand user interface. That’s how I made it from Zurich, Switzerland to Grenoble, France.
Orchestrate silos without the complexity.
Silos of data and services are a reality in the business world and are here to stay. But they need to be orchestrated in order to give your end users exactly what they need. That’s what’s so remarkable about Skuid. With Skuid, you can do just that, but it’s abstracted, so that you don’t have to see the heavy lifting, and neither do your users.
With Skuid, you can create a stunning user experience while integrating data and services silos, without having to actually be an expert in the silos. Because you are configuring apps instead of hand-coding, the velocity of implementation and iteration is off the charts. That’s the magic of Skuid. It almost sounds too good to be true, until you see it for yourself.
The top enterprises in the world are using Skuid to orchestrate their most complex and mission-critical use cases. If you have not tried Skuid yet, I encourage you to consider it as a key layer in your enterprise IT stack.
Your developers will fly through their backlogs and your users will love the experience, happily unaware of the silos you are easily orchestrating behind the scenes to create impactful outcomes. Ready to test the waters with Skuid? Get a free trial now and start integrating your silos today.
