now this is very basic once you understand the jun...
# orm-help
z
now this is very basic once you understand the jungle that deploying is... but can Prisma cloud be used as production without 3rd party database service like AWS? (obviusly in a pricing model)
a
No, not at the moment, but you can deploy Prisma server on your own infrastructure.
z
you mean like Now?
a
Prisma can be deployed wherever you can run Docker. See the "Deploy Prisma Servers" part in the tutorials section: https://www.prisma.io/docs/tutorials/
z
Right. Let's say I deploy to Prisma cloud+AWS, will I have a major headache migrating to Prisma's own database once they're introduced?
a
It would be pretty easy 🙂 You could
prisma export
and
prisma import
again: https://github.com/prismagraphql/prisma/blob/master/docs/1.0/04-Reference/05-Data-Import-%26-Export/02-Data-Export.md
z
even better!
but when you say deploy Prisma server by Docker... do you mean the GraphQl server (since that one holds my custom resolvers) ?
a
In fact, you have to deploy two components: The Prisma server to which you will deploy your Prisma service and your own GraphQL API.
z
that is the part that confuses me - so like for example Prisma service in Prisma cloud and GraphQL service in AWS?
and with Docker, both services go online together in single image?
a
No both applications will be deployed as separate units (with two Docker images) when you want to run both on your own infrastructure. If you want to host the Prisma server in the Prisma Cloud, you still need a place where your GraphQL service will be deployed (e.g. on AWS with Docker, Kubernetes on AWS, etc.) to.
z
Thx, that was the missing part! It seems this part of Prisma is a jungle, no best practices yet and many options. Will Prisma cloud be the "one ring to bind them all" ?
that should have been "rule" but in scope of Prisma bindings I thought "bind" was more appropriate 🙂