Prisma

Would love some feedback on my recent article “Production ready Prisma” <@U4Z1L6CLV> <https://medium.com/@jjaybrown98/production-ready-prisma-2da868a407dd>

I'd love to see how you'd configure rabbitmq and allow scaling of prisma servers.

All great points, I will definitely add the details on scaling those elements as it was a bit nieve to not discuss the primary and secondary split for management API

<@U6Z07HY14> I believe I did by covering the orchestration and use of docker, don't feel the post is there to convince people one way or the other, but it does rationalise why IMO

I also plan to do one for AWS too, so there will be balance 

Wow, <@U6Z07HY14> this article was written based on my experience, it's not the definitive guide, a simple docker deploy isn't scalable, doesn't provide health checks or resilience. I'm not expecting everyone's experience to be the same, but if I rehashed a "this is why X and Y" then there's a fair amount of the readers attention that can be fatigued by that 

Myself included, this was written based on what I would of liked to of read having gone through this experience

It's not constructive. It's pedantic. Tiger.

I've already taken some good feedback onboard.

Thank you for writing this! I've been trying to implement something similar, and your article has given me plenty of good ideas. One thing I'm wondering about, however, is password storage. You have the database password in plaintext in the configmap and DB_PASSWORD referenced through a secret in the deployment. How do these two relate to each other?

DB_PASSWORD is an environment variable, which is available on the pod once deployed. I'm hoping to improve the secret management section, by giving it a bit more detail 

Because prisma takes config as a string, it's not immediately possible to extract the credentials without additional steps. 

That's what I thought, but I was also secretly hoping you'd found an easy way around this. Thanks for the reply, though