# Best practice for creating pipelines

**URL:** <https://discuss.elastic.co/t/best-practice-for-creating-pipelines/133163>\
**Category:** Elasticsearch\
**Created:** [May 24, 2018, 1:57pm UTC](https://discuss.elastic.co/t/best-practice-for-creating-pipelines/133163 "2018-05-24T13:57:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cloudvar](https://avatars.discourse-cdn.com/v4/letter/c/6de8d8/32.png) [@cloudvar](https://discuss.elastic.co/u/cloudvar)\
**Post date:** [May 24, 2018, 1:57pm UTC](https://discuss.elastic.co/t/best-practice-for-creating-pipelines/133163/1 "2018-05-24T13:57:48Z")

</div>

Best practice for creating pipelines in a microservice environment.

Should I go with each project has their our pipeline and then add a jenkins job that deploy as an when things change.

Or based on techology. One pipelines for redis, one for spark, one for tomcat etc , changes can be handled by adding extra GROK.

Looking for some ideas or who other people are implementing it.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 21, 2018, 1:57pm UTC](https://discuss.elastic.co/t/best-practice-for-creating-pipelines/133163/2 "2018-06-21T13:57:51Z")

</div>

Closed on June 21, 2018, 1:57pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.