Showing posts with label customer data. Show all posts
Showing posts with label customer data. Show all posts

Thursday, 3 September 2015

Big Data Series – Part 4 Creating a suitable Technology Stack/ Solution


All of these components bring their individual technology features. Companies must wisely put together an overall solution from among those components, leveraging their complementary advantages and customizing those to their particular needs.

There are four fundamental technology stacks (with their variations) offer possible solutions:

1.       Big data core only or with enhancements (with complex event processing, with in-memory database, with query engine or with complex event processing and query engine)

o   This technology is the de-facto standard for exceptional data movement, processing and interactivity.

o   Data usually enters the cluster through batch or streaming.

o   Events are not processed immediately, but in intervals. Enables parallel processing on large data sets, and thus advanced analytics.

o   Applications and services may access the core directly and deliver improved performance of large, unstructured data sets.

o   Adding CEP enhances big data core processing capabilities, real-time detection of patterns in data and trigger events. Enables real-time animated dashboards. Could add machine learning program to the CEP.

o   IMDB can further increase computing power through placing key data in RAM.

o   Query engines can further open interfaces for applications to access big data even faster.

2.       In-memory data base (IMDB) cluster only or with enhancements (with Big Data Platform, with complex event processing)

o   External data is streamed in or transferred as bulk to the IMDB

o   Users and applications can directly query the IMDB, usually through SQL like structures.

o   The incoming data is first pre-processed through the BDP before it goes to the IMDB

o   In case of CEP, the CEP first ingests the data; the processing is then done in the IMDB and then returned to the application for faster interactivity.

3.       Distributed Cache only or with enhancement (with Application and Big Data platform)

o   A simple caching stack sitting atop of the data source repository. The application retrieves the data. The most relevant data subset is placed in the cache.

o   Processing of the data falls to the application (may result in slower processing speeds)

o   If BDP, the BDP ingests the data from the source and does the bulk of the processing, then puts data subset in cache.

4.       Appliance only or with enhancement (with Big Data platform)

o   Data streams directly into the appliances; the application talks directly to the appliance

o   If BDP, the BDP ingests and processes data. The application can directly talk to the appliance for queries.

Continue part 5 out of 5

Thursday, 20 August 2015

How Web Content Management Systems enable digital

You all know my passion about digital and how to drive forward related technologies & applications. Today I want to share my thoughts on WCMS and explain why we should care about it.
Web Content Management Systems (WCMS) can been viewed as a technology and content delivery back bone for digital experiences. There are over a billion Web sites in this world and each site needs a WCMS!
Wikipedia describes, “A web content management system (WCMS) is a software system that provides website authoring, collaboration, and administration tools designed to allow users with little knowledge of web programming languages or markup languages to create and manage website content with relative ease.”
A WCMS brings together the specialized products that customers use across the customer journey (Marketing, Software and Commerce Suites, Customer Service Systems, Community Sites, Social Systems, etc.).
This back bone brings together Customer data, Resources and Orchestration, Contextual Delivery, and Touch Points. The platform extends through APIs, Integration frameworks, Data extractions, and Developer Environment. Insights are generated through Data capture, Analytics, Machine learning and Dash boards.
Customer Data includes the Master profile, segmentation, preferences, audiences and external data. Resources and Orchestration includes the Assets (Marketing, Social and third party content, rich media), Interactions (forms, rating & reviews) and Business Operations (localization and globalization).
While Web Content Management has existed for now decades, systems are evolving to meet the needs of for providing mobile, social and personal experiences and meeting application development & delivery needs.
WCMS must enable all roles (site designers, marketers, merchandisers, product managers, editors, etc.) to manage and create content in an effective way. Such content must be delivered effectively on browsers and mobile devices. Unfortunately no vendor is currently providing adequate mobile app support…
The WCMS must also effectively integrate with other key applications such as CRM, Customer Communication Management, digital asset management, test & target tools and employee portal products. The WCMS should be a single tenant PaaS, ideally multi-tenant SaaS.
WCMS has important responsibilities across the customer journey: Manage Marketing, user generated product content. Organize micro-sites and landing pages. Enable search ratings and reviews. Support employee and self-service portals. Manage Customer Reviews.
Companies need to carefully examine a vendor’s global reach, partner network, code base, as well as ease of use for own developers,
Locking at companies: Adobe is the clear leader, also perhaps most pricy in the industry. Site core, Acquia and IBM (both Cloud based or focus) the other two big leaders. HP, Oracle, Opentext and SDL are also strong players.

+++
To share your own thoughts or other best practices about this topic, please email me directly to alexwsteinberg (@) gmail.com.

Alternatively, you also may connect with me and become part of my professional network of Business, Digital, Technology & Sustainability experts at

https://www.linkedin.com/in/alexwsteinberg   or
Xing at https://www.xing.com/profile/Alex_Steinberg   or
Google+ at  https://plus.google.com/u/0/+AlexWSteinberg/posts