WSO2 is helping enterprise retail organizations fulfill their vision of digital transformation and connect their business to the world across both digital and brick and mortar channels. WSO2 is pioneering how the Industrial Internet of Things, Big Data, API-centric architecture, and Cloud services augment digital business strategy and facilitate execution.
Retail industry companies are evolving their 1.0 eCommerce platforms to embrace 3rd party channels, recommendation engines, social media, and user analytics. APIs enable secure, controlled, and timely access to the aforementioned business capabilities delivered by partners. By integrating 3rd party capabilities, rather than building and hosting the capability internally, retailers are able to tap into an extended ecosystem of best-of-breed analytics, customer preference repositories, social sentiment, and business capabilities (i.e. payment, digital marketing, shipment expeditors). Some retailers are adopting APIs to tap into a channel of mobile application developers, external suppliers, and 3rd party digital storefronts. Mobile application developers can connect the retailer with mobile app customers and extend the reach and exposure of retail goods (especially in ‘flash sale’ or ‘sale liquidation’ scenarios). Retailers tightly integrated with external suppliers can use APIs to gauge product demand across the supply chain and enhance product availability. Retailers may also use APIs to integrate with 3rd party retailers and vendors who desire to offer a white-label digital storefront on the retailers digital property. Similar to a department store allocating floor space and advertising to a specific vendor.
WSO2 technology is solving the biggest challenges retail companies face in scaling their transaction volumes (billions per day), lowering security risk, enhancing customer experience, and enabling new digital commerce channels.
eBay routes billions of transactions per day using WSO2’s Enterprise Service Bus. AAA Motor Club of Ohio delivers timely point of interest information to motorists via APIs secured using the WSO2 platform. StubHub deploys WSO2 API Manager to connect their ticket platform with 3rd party mobile applications and expand their new digital commerce opportunities. John Keells Holding captures Point of Sale information using mobile devices and augments their customer database using WSO2 Message Broker. A retailer uses WSO2 Business Activity Monitor (based on lambda architecture and complex event processing) to merge historical and real-time information, analyze temporal shopping patterns, rapidly adapt offers (product recommendations, prices, promotions, and assistance) to the customer’s context. WSO2 Enterprise Mobility Manager and WSO2 Device Manager reduces point of sale provisioning time and satisfies risk assurance mandates.
Do you have a digital platform that can drive your digital business forward across a connected world?
Politics is all about power. Whether in Washington DC, Brussels, or Beijing, individuals jockey for advantage using the political process. The politics of APIs centers on ‘knowledge being power’ and ‘data content being power’. Individuals and corporations gain a powerful advantage in the API economy by enforcing content ownership, access privileges, and distribution rights to their advantage.
Choosing appropriate API security options will help you gain developer trust, increase API adoption, and build an effective API ecosystem. While APIs are the ‘coolest’ and most effective mechanism to expose business functionalities out towards the outside world and inward to other teams, API security requires learning new technologies (i.e. OAuth, MAC token profiles, and JSON Web Token [JWT]) and retrofitting existing identity management architecture with token chaining and identity brokering.
Many mobile application developers and architects find API security and identity options are arcane, jargon-filled, and confusing. They frequently ask whether selecting one choice over another is appropriate – and you need to cautiously identify and isolate tradeoffs. A robust API security platform can help guide you in the right direction.
API Security Basics
Security is not an afterthought. Incorporate security as an integral part of any application development project. The same approach applies to API development as well. API security has evolved significantly in the past five years. The recent standards growth has been exponential. OAuth and bearer tokens are the most widely adopted standard, and are possibly now the de-facto standard for API security.
What API security decisions should you consider?
During the SOA craze days in the past, proponents pitched SOA’s lofty benefits from both business and technical perspectives. The benefits are real, yet sometimes very difficult to obtain. Surprisingly, today’s API proponents target similar benefits, but with an execution twist.
While everyone acknowledges API and Service Oriented Architecture (SOA) are best practice approaches to solution and platform development, the learning curve and adoption curve can be steep. To gain significant business benefits, teams must understand their IT business goals, define an appropriate SOA & API mindset, describe how to implement shared services and popular APIs, and tune governance practices.
The crew in the Home Port Lighthouse spotted a few interesting posts were spotted. Here are the links and my sighting report:
Location: CloudBees Cloud App Development Platform Available on Verizon Cloud
WSO2 App Factory is an Open Source PaaS offering functionality similar to CloudBees. The DevOps PaaS delivers Jenkins, continuous delivery, enterprise governance, and DevOps best practices.
Location: Harnessing the Power of APIs
Are you publishing Naked APIs, or Managed APIs? A managed API is:
- Actively advertised and subscribe-able
- Available with an associated, published service-level agreement (SLA)
- Secured, authenticated, authorized and protected
- Monitored and monetized with analytics
When creating an API Management program, consider including these five steps:
- Step 1 Embrace the Managed API
- Step 2 Establish a Monetization Model
- Step 3 Make APIs Easy for Developers to Access
- Step 4 Employ Governance
- Step 5 Monitor API Use
Location:Cloud Spending Spikes, Here’s Where to Invest
- Excellent distinction by Dave when parsing Cloud’s momentum and investment drivers. “That’s not new money, just moved money.”
- ” focus on the specific aspects and the value they bring to your business — that’s where you want to align your own investments.”
When DevOps Meets ALM in the Cloud, teams can follow a three step PaaS performance metrics adoption plan:
๏Step 1: Foundational value metrics focus on Time to Market
๏Step 2: Optimization value metrics focus on Portfolio Efficiency
๏Step 3: Transformational value metrics focus on Productivity
The SOA perspective is reverberating into an API echo. During past SOA craze days (2003-2008), proponents pitched SOA’s lofty benefits from both business and technical perspectives. The benefits are real, yet sometimes very difficult to obtain. Surprisingly, today’s API proponents target similar benefits, but with an execution twist.
When crafting an API strategy and proposing API benefits, consider whether your organization is pursuing an API-Access Mindset or and API-centric Enterprise Mindset. These API approaches are similar to recognized Big SOA / Small SOA or Top-down SOA / Bottoms-up SOA approaches.