The new IBM Digital Commerce platform brings to the table a couple of key gems for developers and administrators. In my opinion, which may or may not mean much to you, the two primary pieces of this new platform that make it a first class eCommerce platform are Liberty and Docker.
The self-serve omni-channel cognitive eCommerce platform is here, welcome IBM Digital Commerce!
In this episode of Partner Connect I show the latest enhancements CoreMedia has implemented with a few Watson API’s. I show three cool integrations in this video: Watson Conversation Services, Watson Visual Recognition Services, and Watson Translation Services.
You have heard of “chat bots”, well, think of Watson Conversation as a chatbot on steroids. CoreMedia has done some really slick dialog in their studio to help users complete various tasks within their software. They then use Watson Visual Recognition to automatically suggest tags and even recommend if products were found in the image – which you can then create image maps and link them into your commerce catalog. Lastly, once your landing page or content is created you can then localize your content with a click of a button using Watson Translation services!
Since this video is so long I do a 3 minute overview in the beginning because the actual demonstration is about 15 minutes but well worth it!
Come hear yours truly pitch an end to end demonstration using the Watson Customer Engagement platform!
Retailers have five common business problems executing across multiple channels and their brick and mortar stores:
- Personalization across all channels leveraging company data
- Common user experience from unstructured content
- Full circle learning / input reintroduction
- Connected commerce and digital experience
- Online / in-store inventory execution & Supply Chain Management
In this video I tell a story about the Aurora company and walk through their new summer Albini dress campaign. The Aurora team uses the Watson Customer Engagement platform to drive a successful campaign. The story centers around Katie, an avid Aurora shopper, where the Aurora team has visibility into activity across all channels and drives customers into their brick and mortar stores to drive additional sales.
Watch how the Aurora team uses the Watson Customer Engagement platform to execute an email campaign and learn about their shoppers across their web site, mobile application, call center, and stores.
Working with REST services can be extremely error prone. You could have latency, network failures, or at worse case even total down time. I have been writing a lot of code as of late that requires extreme error handling and graceful failing when dealing with remote REST services and in general web calls – like parsing or loading external web sites for DOM evaluation as an example. The issue is you can’t trust the performance or even trust the service is even available and knowing what methods are failing or causing the bottlenecks could be extremely cumbersome. You could implement network profilers to capture what is going on, or, you could implement a CircuitBreaker design pattern and take control of your calls yourself.
Welcome the Circuit Breaker design pattern. This pattern allows you to monitor a specific function call and “break” gracefully if it has taken too long or even fails. This is usually symptomatic with asynchronous calls that may require calling other code on completion, fail, or timeout. Methods like jQueries ajax where you supply the various error, complete, and done methods work great and even languages like Swift and Java have similar callbacks but it lacks data around the calls. The CircuitBreaker design pattern will make your code easier to follow for race conditions and it can even track statistics around the calls…
If you are a Swift programmer you can check out the Swift CircuitBreaker project on GitHub. It has complete documentation and makes using this design pattern very easy and straightforward.
Now, what sets this package apart in my opinion is it also gives a large set of statistics around the calls. Capturing how long calls take (latency), how many successes, failures, and even average response times. From an SLA perspective this is great! You can then quickly identify what remote calls to “other” services are the primary bottlenecks or problems in your application.
We have several offerings spanning Marketing and Commerce and many more coming this year. As a developer, you can now sign up to be notified when products and API’s become available on the IBM marketplace. Bookmark it and sign up today for notifications.