Implementing Microservices as an alternative to a heavy, monolithic architecture is an exciting IT trend that’s gaining momentum amongst Digital Commerce customers and vendors worldwide. At the Adobe Summit in March, Adobe’s Senior Product Manager Martin Buergi shared that 36% of Adobe Marketing Cloud customers surveyed have at least “several [microservices] projects live,” and 64% are getting started, or have microservices on their roadmaps. (Yes, that means no respondents had no interest in microservices!)
Microservices are also catching the attention of leading analyst firms, including Gartner. The Gartner Magic Quadrant is an annual report that thoroughly evaluates leading technology vendors within a given space. Gartner’s Magic Quadrant reports have earned the respect and trust of business and IT leaders for their rigorous selection process, inclusion and exclusion criteria, and evaluation based on the context of current technology trends and forecasts.
We believe the 2018 Magic Quadrant for Digital Commerce recognizes the market’s demand for a modern API-oriented, modular and flexible solutions from enterprise-grade digital commerce leaders.
The Internet Retailer Conference and Exhibition (IRCE) is arguably one of the largest and influential ecommerce conferences in the industry. The conference will take place next week in Chicago and we’ll be there.
Digital Commerce 360 says it’s “a conference like no other” and includes breakout sessions, networking events, and of course, swag and vendor parties. Conferences, similar to IRCE, provide immense opportunity to learn from your peers and ecommerce experts, how commerce and technology are evolving, and the consumer trends that you need to keep up with.
Skava is excited to be attending IRCE this year to showcase the latest 7.5 version of the Skava Commerce platform and how we’ve integrated voice to our microservice.
Product design has many phases ranging in scope and complexity across the spectrum, but even the minor phases are essential to the overall success of the project. In this post, I’m focusing on one of these smaller phases: Design Handoff, and specifically, the Remote Handoff. This is when UX and visual design are finished and the creative assets are transferred to the implementation team in a different time zone — a scenario becoming more and more common as resources are becoming more distributed.
Design Handoff seems like such an insignificant part of the larger picture. However, a bad handoff can have cascading problems affecting multiple teams and timelines, and could ultimately jeopardize your project.
You’ve probably heard some variation of the phrase, “Just throw it over the fence.” This is something that happens when teams decide to handoff hastily. They bundle up assets and send links to the dev team hoping for the best. Of course, “the best” is rarely the result, and this is not the developer’s fault.
Why are business leaders increasingly moving away from legacy platforms and architecture in favor of more nimble environments?
In today’s “anything can transact” world, the pressure is on to accommodate new customer journeys and touchpoints, as well as maintain and improve internal systems to suit the unique needs of the business across channels.
Monolithic platforms are simply too difficult to accommodate the requirements of a modern digital business. Microservices offer the flexibility and efficiency that businesses need to rapidly shift strategies, continually evolve their commerce experiences, and continuously improve core business processes.
Barbie Girl by Aqua. IBM Net.Commerce 2.0. Princess Diana’s Funeral. ATG eCommerce 4.1. The first Mars Pathfinder lands successfully. Intershop Online is available on CD with a 30 day trial.
Customer expectations have evolved considerably since 1997, even as many commerce packages are still mired in architectural choices made two decades ago. Looking back, we can see three major waves of architectural choices:
The Monolith – 1995 – 2010
Most existing commerce applications were developed in the 1990s, and their architecture reflect the best practices of that time – a single monolithic application with a tightly coupled front end and back end. As digital commerce has evolved, it’s proven challenging and time-consuming to keep pace with customer expectations. Changes in any area of the application require extensive testing, and as the application gets older, it gets more brittle as more and more functions are glued into it.
In today’s digital commerce age where new customer journeys, routes to market, digital touchpoints, business models and technologies rule, there remains a chasm between customer expectations and what an enterprise can deliver with legacy systems.
Customers don’t care that something’s difficult, costly or risky to build and deliver. They don’t appreciate that your IT group works on quarterly release cycles. They don’t understand how much technical debt you’re drowning in, or how much refactoring and regression testing your organization is not willing to do. They just feel the pain of their experience gap (that company B seems to handle just fine).
SAN FRANCISCO, May 2, 2018 /PRNewswire/ –Skava, a leading provider of cloud microservices for ecommerce, has announced its joining the Adobe Exchange partner program at the Community level.
“Skava is very excited to be part of Adobe Experience Cloud’s growing ecosystem. We look forward to offering unique digital shopping experiences with Adobe and integrating our modern ecommerce microservices to power these experiences,” said Arish Ali, CEO of Skava.
Skava Commerce, a microservices-based, ecommerce platform, is built to meet and exceed customer expectations in today’s hyper-competitive, mobile-first world and empower brands to go to market faster and innovate continuously.
By bringing together Skava’s leadership in microservices for ecommerce with Adobe Experience Manager’s leadership in experience management, brands can explore new ways to capture shoppable moments and discover synergies.
Microservices are becoming an important part of an enterprise strategy. Brands can no longer afford to be held back by rigid, outdated technologies that require redundant processes and expensive resources. They must be disruptive.
Many enterprise brands have started with a monolithic ecommerce platform to power customer-facing experiences. Now, digital disruptors, such as Amazon, Netflix, and Uber have paved the way to building and embracing a microservices-based architecture and deliver consistent brand experiences across all channels.
In a previous blog post, What are microservices and why you should care, we dove into the world of microservices and its key benefits compared to archaic monolithic platforms. Without a big bang transition, microservices can be adaptable in your current enterprise strategy and beneficial to your overall business.
“Quality is not what happens when what you do matches your intentions. It is what happens when what you do matches your customers’ expectations.” – Guaspari
When selecting an ecommerce platform, it’s important to select a platform that will allow you to meet your customer’s digital expectations today, as well as be flexible enough to grow with their evolving needs. The customer expectation bar is climbing rapidly and selecting an ecommerce platform, which can grow with you is critical.
While there is a wealth of information available about the features of ecommerce platforms, it is not often clear how the specific features and functions translate into finding the right ecommerce platform for your situation. This guide focuses on how to evaluate an ecommerce package on the merits of its architecture and flexibility. This document was created based on countless conversations with customer and product focus groups, industry analysts and our own research, which tries to look at the high level.
The Skava Commerce platform is built using modular microservices architecture. Its microservices allow you to ideate and release updates quickly, iterating on new features over the course of days instead of months.