Prisma

Hey all... How would I set up my schema.graphql to handle this response?

[  [
    { name: 'full_name', values: [Array] },
    { name: 'how_many_miles_has_the_car_done?', values: [Array] },
    { name: 'phone_number', values: [Array] },
    { name: 'what_is_the_reg_number_of_the_car?', values: [Array] }
  ]]

<@UJA839NG7>
```type ArrayInfoType {
  name: string,
  values: Json @default("[]")
}

'''Your mutation'''
myMutation: [[ArrayInfoType]]```

How are there so many users in here, yet so little activity? Just wondering :sweat_smile:

yeah, and a lot of questions goes unanswered, which is discouraging

Yeah, Prisma Slack is one of the least active ones. And so many people have so many questions which largely go unanswered. Very discouraging indeed.

Hey Mikkel, Yorch, and Samrith :wave::skin-tone-4: ,

Thanks a lot for sharing your thoughts and sorry to hear that’s been your experience.

Prisma 1 is in maintenance mode and we’re working hard to push a stable release of the Prisma 2 (See <https://github.com/prisma/prisma/issues/4898>). Therefor our support efforts are primarily directed at the new version: Prisma 2.

I suggest to check out the more active <#CKQTGR6T0|prisma2-preview> channel where you can get support for Prisma 2 related questions.

Hey Daniel,

Thanks for the prompt response. I do understand that, but I also do agree with <@UQZ4T6XTR> said.

It’s difficult to decipher things, primarily because when you search for Prisma 2 docs, then it shows you Prisma 1 docs (majorly SEO) and vice-versa.

Plus, in a lot of the examples, it uses outdated codewords (like Photon) and these docs are extremely confusing to someone who already has a lot to grasp with Prisma, Nexus, Nexus Prisma, etc etc.

If I can help in correcting these docs, do point me in the direction, and I’ll raise PRs in the appropriate places to update these. :slightly_smiling_face:

Hey Samrith :wave: It's absolutely true and we're aware that the state of content with the Prisma 2 docs on GitHub is pretty messy right now. We're doing our best to keep everything up-to-date, plus we're about to launch a new version of the Prisma docs including the 2.0 content, so hopefully that will resolve the SEO and other issues.

Aside from that, it would be certainly be helpful and very appreciated if you create an issue (or even a PR) whenever you come across an inconsistency or other problem with the docs! :slightly_smiling_face:

In my humble opinion, you can't put Prisma 1 _support_ in maintainance mode until you have actually released a complete replacement in the form of Prisma 2 (for me that includes mongodb support)

Cool Daniel, the preview channel was just what I was looking for :slightly_smiling_face:
I'm super excited for prisma2 by the way. Lack of activity just makes you wonder!

Has anyone figured out how to deploy prisma on AWS? All the tutorials seem to be broken there <@UCZMXEP3J> <@U3D8LQ8HK>

<@UMT26C9KM> EKS, ECS, EBS take your pick just use the docker container and scale like you do any other docker service

So along with the graphql server, you are running a mysql instance and  running a BE prisma server on that same instance?

no use an RDS DB  like  aurora mysql or postgres and prisma connect to that db

ok, but you are using the ec2 for both the graphql server and primsma server?

got ya, I would not put them on an ec2 server unless you were just wanting to test that or very low load service

im a kubernetes fan myself but could use ECS if you wanted

Why kubernetes over ec2? As an aside would love to see a best practice totorial on setting prisma up

lots of reasons really, best practice you have some sort of LB in front of the service that has autoscaling rules of some sort

is there any information on how much load a prisma demo server could take vs a micro ec2 running a graphql and a prisma backend server? i.e. 100 queries per second?

Screen Shot 2020-03-10 at 6.53.48 PM.png

<@U7RFNCZQE> I tried to use RDS DB Aurora & this is what I get when attempting to connect it with the appropriate & correct credentials.

<@UDREAPDR6> did you by chance choose aurora serverless mysql?

is the port open on the db security group to your IP

also you specified a database name, for prisma on a fresh db  you wont need to specify a db, your first model will create one