# Slicer's existing architecture

**URL:** <https://discourse.slicer.org/t/slicers-existing-architecture/34732>\
**Category:** Development\
**Created:** [March 6, 2024, 4:35am UTC](https://discourse.slicer.org/t/slicers-existing-architecture/34732 "2024-03-06T04:35:17Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [March 6, 2024, 3:50pm UTC](https://discourse.slicer.org/t/slicers-existing-architecture/34732/3 "2024-03-06T15:50:44Z")

</div>

For reference, both VTK and ITK filters are indeed written by leveraging classes like `vtkThreadedImageAlgorithm` or `itk::MultiThreaderBase`

For example, the new SurfaceNets feature heavily relies on the threading capabilities. See [New surface model generation method: SurfaceNets](https://discourse.slicer.org/t/new-surface-model-generation-method-surfacenets/32430)

---

_[View the full topic](https://discourse.slicer.org/t/slicers-existing-architecture/34732)._