# Modern Production stack for Great Expectations

**URL:** <https://discourse.greatexpectations.io/t/modern-production-stack-for-great-expectations/1456>\
**Category:** Feedback\
**Created:** [October 26, 2023, 12:45pm UTC](https://discourse.greatexpectations.io/t/modern-production-stack-for-great-expectations/1456 "2023-10-26T12:45:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aleksei](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@Aleksei](https://discourse.greatexpectations.io/u/Aleksei)\
**Post date:** [October 26, 2023, 12:45pm UTC](https://discourse.greatexpectations.io/t/modern-production-stack-for-great-expectations/1456/1 "2023-10-26T12:45:14Z")

</div>

Hello, community.  
I want to raise the topic of a modern stack for GX in production  
As I see for production using:

- A fluent data source is better than a block config data source
- Checkpoint is better than a validator
- Checkpoint is better than SimpleCheckpoint
- Data assistance is better than rule-based profiler

Thoughts?

---

<div class="post-metadata">

**Author:** ![CesarGarcia](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.greatexpectations.io/cesargarcia/32/195_2.png) [@CesarGarcia](https://discourse.greatexpectations.io/u/CesarGarcia)\
**Post date:** [November 9, 2023, 11:46am UTC](https://discourse.greatexpectations.io/t/modern-production-stack-for-great-expectations/1456/2 "2023-11-09T11:46:46Z")

</div>

Hi Aleksei,

Thanks for raising such an important topic. To answer that question, I think it would be quite important to map these concepts to the related documentation and the steps along the GX workflow. I have to review the new updates to the docs and I’ll share any insights in this thread.

---

<div class="post-metadata">

**Author:** ![Aleksei](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@Aleksei](https://discourse.greatexpectations.io/u/Aleksei)\
**Post date:** [November 15, 2023, 8:00pm UTC](https://discourse.greatexpectations.io/t/modern-production-stack-for-great-expectations/1456/3 "2023-11-15T20:00:03Z")

</div>

@CesarGarcia thank you! Yes, will be great to point out best practices in GX docs. But before this, it needs approval from the community and GX.

---

<div class="post-metadata">

**Author:** ![Aleksei](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@Aleksei](https://discourse.greatexpectations.io/u/Aleksei)\
**Post date:** [November 15, 2023, 8:01pm UTC](https://discourse.greatexpectations.io/t/modern-production-stack-for-great-expectations/1456/4 "2023-11-15T20:01:22Z")

</div>

Add some points about expectations  
json as expectations storage is better than code

---

<div class="post-metadata">

**Author:** ![mateocolina](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@mateocolina](https://discourse.greatexpectations.io/u/mateocolina)\
**Post date:** [January 4, 2024, 11:13pm UTC](https://discourse.greatexpectations.io/t/modern-production-stack-for-great-expectations/1456/5 "2024-01-04T23:13:03Z")

</div>

Any news on this topic? We are currently exploring the possibility to deploy and run expectations on Kubernetes. The setup in mind would be

- Build Docker image with dependencies
- store great\_expectations.yml as a ConfigMap and use Kustomize to manage enviroments
- Airflow to trigger the checkpoint run
- use sidecar pod with access to expectation suites

We are currently struggling with how to incorporate this process with CI/CD. And what the development process will look like. Any idea?

Is there also a best practice for running always the same actions for all checkpoints?

Anything else to look out for? Anything missing?