anchor.diff:  [[ocp-33-router-sharding]]
   ==== Router Sharding
   
  -{product-title} offers a xref:../architecture/additional_concepts/sdn.adoc#architecture-additional-concepts-sdn[multi-tenant], docker-compliant platform. Thousands of
  -tenants can be placed on the platform, some which may be subsidiary corporations
  -or have drastically different affiliations. With such diversity, often times
  -business rules and regulatory requirements will dictate that tenants not flow
  -through the same routing tier.
  +{product-title} offers a
  +xref:../architecture/additional_concepts/sdn.adoc#architecture-additional-concepts-sdn[multi-tenant],
  +docker-compliant platform. Thousands of tenants can be placed on the platform,
  +some of which may be subsidiary corporations or have drastically different
  +affiliations. With such diversity, often times business rules and regulatory
  +requirements will dictate that tenants not flow through the same routing tier.
   
   To solve this issue, {product-title} 3.3 introduces
   xref:../architecture/core_concepts/routes.adoc#router-sharding[router sharding].
  
positive.code: rsync --watch`, which launches a long running process that monitors the local
  file system for changes and continuously syncs them to the target container.
  Assuming the target container is running a framework that supports hot reload of
  source code, the development workflow is now: "save file in IDE, reload
  application page in browser, see changes."
  
  For more information, see xref:../dev_guide/copy_files_to_container.adoc#continuous-syncing-on-file-change[Continuous Syncing on File Change].
  
  
negative.code: [[ocp-33-pipelines]]
  ==== Pipelines (Technology Preview)
  
  Previously with CI/CD, it was possible to define small pipeline-like workflows (such as triggering deployments after a new image was built or building an image when upstream source code changed), OpenShift Pipelines (currently in Technology Preview) expose a true first class pipeline execution capability. OpenShift Pipelines are based on the link:https://jenkins.io/solutions/pipeline/[Jenkins Pipeline plug-in]. By integrating Jenkins Pipelines into OpenShift, you can now leverage the full power and flexibility of the Jenkins ecosystem while managing your workflow from within OpenShift.
  
  [NOTE]
  ====
  