Posts

Part 2 - Decomposing and decoupling to achieve composability

Image
Having introduced "composable" in part 1 , we will now look at deconstructing and decoupling the typical layers of a digital solution to understand how composability can be achieved within them. Let's assume a typical application is composed of the following four layers: Client UI - typical client UI to serve channels like web, mobile, email, Social, AR/VR, Kiosk Infrastructure - this includes networking, security, hosting, routing and other typical functions Platforms/products - Off-the-self, plug-and-play, pay-as-you-go, bespoke products and tools that offer packaged business capabilities (PCBs is another Gartner term) or business applications as well as persistence Data storage - storage and persistence for data and analytics. Enterprise Data Lakes, Collections DB etc. Non-composable version of a digital solution will still include these layers but they are siloed. Decomposing the digital solution into these basic layers is in other terms is achieved through decoupling

Part 1 - Introduction to Composable

Image
 If you are in the business of building digital solutions, you may have come across the terms "Composable", "Composable Enterprise", "Composable Architecture", "Composable DXP"  "Composable Commerce" etc. I believe this was coined by Gartner in one of their publications couple of years ago and since then it has gained a lot of traction. But like most industry jargons, most readers tend to piece the topic together in their mind by associating the definition of the word with a function they perform professionally. For e.g. API-first . Every time I ask someone to define what API-first means, they then do offer a simple explanation which is to build APIs first before building UI or something similar. While there may be nothing wrong with that definition, API-first much more than that. for e.g. developing an API description language . So, I thought it may be a good idea to dig a bit deeper into "Composable" and perhaps offer a fram

OneWeb: Unifying multi-brand experience management and digital operations with the power of Sitecore

Although Sitecore offers multi-tenancy OOTB, many enterprise customers of Sitecore find themselves managing websites across multiple brands, business units, regions and often end up with multiple deployments that may increase redundancy, reduce reusability and increase overall cost of marketing and IT operations. This session will showcase how a large CPG enterprise used OneWeb framework utilizing best practices and enabling advanced features of Sitecore to unify digital operations. OneWeb: Unifying multi-brand experience management and digital operations with the power of Sitecore from VarunNehra

From Azure Search to SearchStax

Image
 Now that Sitecore v10.x is fully supported on Azure AKS, Sitecore in its reference architecture has replaced Azure Search with SearchStax as the go to provider for Solr as a service. This presentation showcases the what, the why and the how to deploying SearchStax. Migrating from Azure Search to SearcStax from VarunNehra

Get Ready for Jamstack with Sitecore Experience Edge

An introduction to Jamstack architecture. With Sitecore supporting React and Next.js you are one step closer to Jamstack delivery with Sitecore JSS, Experience Edge for Sitecore Content Hub and  Experience Edge for Sitecore XM enable Jamstack architecture. Get ready for_jamstack_with_sitecore_experience_edge_upload from VarunNehra

Newest feature of Next.js: Incremental Site Regeneration (ISR)

Image
I am sure you are already aware of the difference between Static Site Generation (SSG) and Server Side Rendering (SSR) and their benefits respectively.  The key difference between the two is that SSG generates the HTML at build time, making it static, but allows for changes to UI using client-side scripting (JS) to make it dynamic whereas, SSR generates HTML on page request. The benefit of SSR is that it allows you to change HTML without requiring a build, which means you can continuously update the UI without requiring a build.  This key difference makes SSG fast and performant and ideal for brochure ware sites, blogs, developer documentation etc. and make SSR comparatively slow but ideal for portals and dynamic applications. Next.js does a great job of enabling both using React. Now some say SSG should be the default way forward but there are reasons why SSR becomes a preferred approach. However, with Next.js v9.5, a new feature was announced called Incremental Site Regeneration. Thi

Introducing Sitecore Experience Edge: The What, The Why and The How

Sitecore Experience Edge, A short story (Intro to Sitecore Experience Edge) from VarunNehra I recently presented a lightning talk on introducing Sitecore's Experience Edge for Content Hub and Experience Manager. What you need to know to evaluate, select and implement the right product for you or your customer. Enjoy!

Google Lighthouse Tips: Importance of web page speed

Image
Mobile Focus  75% of global mobile users were on 2G and 3G as of 2016 (Source: GSMA Mobile)  1MB takes minimum of 5 seconds to download on a typical 3G connection. (Source: WebPageTest & DevTools 3D definition)   19 seconds is the average time a mobile web page takes to load on a 3G connection. (Source: Google DoubleClick blog)  70% of mobile pages take nearly 7 seconds for visual content above the fold to display on the screen. (Source: Think with Google)  UX & UI Performance  As the number of elements on a page increases from 400 to 6000 the probability of conversion drops 95%. (Source Think with Google)  Site takes >1 sec to become interactive, users lose attention, and their perception of completing the page task is broken. (Source: Google Developers Blog)  As page load time increases from 1 sec to 7 secs, the probably of mobile site visitor bouncing increased 113%. (Source: Think with Google)  Proven Results  Walmart saw 1% increase in revenue for every 100ms improvemen

Sitecore Symposium 2020: Accelerating Digital Business with Enterprise Marketplaces using Sitecore Experience Cloud

Image
Accelerating Digital Business with Enterprise Marketplaces using Sitecore Experience Cloud - Part 1  Accelerating Digital Business with Enterprise Marketplaces using Sitecore Experience Cloud - Part 2 Accelerating Digital Business with Enterprise Marketplaces using Sitecore Experience Cloud - Part 3

1:1 Personalized marketing at scale using Sitecore Connect for Salesforce Pardot

Image
  The 3 pillars of personalized marketing at scale are: Robust Digital Experience Platform (DXP) Marketing automation platform CRM The key to achieving real time personalized marketing requires breaking data silos by integrating systems, building customer profiles iteratively and across channels, collecting the right data, identifying the right KPIs for measurement of success and aligning KPIs with business goals, The Sitecore connect for Salesforce Pardot is a Sitecore connector that provides bi-directional syncing of real time interactions tracked across channels by both Sitecore and Pardot. It offers real time personalization using Sitecore based on a number of data facets available in both Sitecore and Salesforce Pardot. It offers the following features: Integrate multiple instances of Pardot with a single instance of Sitecore. On-demand bi-directional syncing of marketing data. Uses email as a unique identifier between Sitecore Contacts and Pardot Prospects. Creates new contacts a