Sitecore: Utilizing Pipelines for Long Processes
August 9, 2016
While GeekHive is a platform agnostic technology partner, we have several developers on staff who excel at Sitecore builds. Joining our CTO Jay Oliver who wrote, Running Sitecore 8 in a Docker Container, and my fellow developer Steve VandenBush who wrote, Disconnected Sitecore: a Headless and Non-Traditional Approach, I just wrote my first post for Sitecore’s Blog, Utilizing Pipelines for Long Processes. Together our aim is to contribute to the Sitecore community-at-large through Sitecore’s Technical Blog.
Here’s an excerpt from the post:
At GeekHive, we aim to do things as efficiently and effectively as possible. If you develop in Sitecore long enough, eventually you will be tasked with some type of long running process that may be multi-stepped. For example, read an RSS feed, sanitize the data, import that data into Sitecore, and publish the changes. The details of an operation like this are up to the requirements and the developer performing the work, but any long running process such as the example given can abide by some simple concepts that will make the work cleaner and easier to manage in the future.
In the same way that Sitecore uses pipelines throughout the page request lifecycle, e.g. preprocessRequest, httpRequestBegin, httpRequestProcessed, etc. it’s possible to add custom pipelines that make sense for your operation. For this blog post, we’ll continue with the example from the introductory paragraph.
You can find the entire post on Sitecore’s technical blog here, in it, I lay out an easy to read and follow configuration file for the process.
If you’re interested in learning more about Sitecore best practices, check out my other blog posts here.
Stay up to date with our email updates!