3 ms·

This seems really awesome. I read the sample project, and was able to understand it really fast. It honestly would make our engineer onboarding really fast! Sin

This seems really awesome. I read the sample project, and was able to understand it really fast. It honestly would make our engineer onboarding really fast! Since it's all in one simple place. And the architecture is standardized. The authentication model is what I liked most. I think the biggest blocker is the use of Prisma however. I've never heard of Prisma before, and I'd have no problem using it. But I use DynamoDB for practically everything, not sure how that translates to that world. The second concern is that most of projects are written in Typescript. I'm not sure how this works with TS. I'd hate to write an entity twice - for example, a user entity, and a user interface in TS. Because they have to be typed anyways.

Martinsos 6y ago
Great to hear that :)!! Thanks Nikolas for answering regarding Prisma! The reason why we chose Prisma is because it is declarative, which plays really well with Wasp, and because it supports multiple types of databases - for now only relational, but as Nikolas said, in the future also nosql. Regarding TS - you are right, TS is a better fit for this than JS! We started with JS, but plan is to switch to TS real soon, for the reasons you described. Here is the Github issue discussing this: https://github.com/wasp-lang/wasp/issues/143 https://github.com/wasp-lang/wasp/issues/143 . If you don't mind me asking, how big is your team / what are you using right now to build web apps?
nikolasburk 6y ago
Hey, Nikolas from the Prisma team here! As of today, we indeed only support relational databases (Postgres, MySQL, SQL Server, SQLite) but we are already working on a connector for MongoDB[1] and plan to expand to more DBs in the future, here's the open issue to support DynamoDB[2]. Hopefully Prisma becomes an option for you once we support your favorite DBs! [1]: https://www.notion.so/prismaio/Prisma-Roadmap-50766227b779464ab98899accb98295f?p=9f115ebf4a754069a7d7eaae94dc4651 https://www.notion.so/prismaio/Prisma-Roadmap-50766227b77946... [2]: https://github.com/prisma/prisma/issues/1676 https://github.com/prisma/prisma/issues/1676

Martinsos 6y ago

Great to hear that :)!! Thanks Nikolas for answering regarding Prisma! The reason why we chose Prisma is because it is declarative, which plays really well with Wasp, and because it supports multiple types of databases - for now only relational, but as Nikolas said, in the future also nosql. Regarding TS - you are right, TS is a better fit for this than JS! We started with JS, but plan is to switch to TS real soon, for the reasons you described. Here is the Github issue discussing this: https://github.com/wasp-lang/wasp/issues/143 https://github.com/wasp-lang/wasp/issues/143 . If you don't mind me asking, how big is your team / what are you using right now to build web apps?

nikolasburk 6y ago

Hey, Nikolas from the Prisma team here! As of today, we indeed only support relational databases (Postgres, MySQL, SQL Server, SQLite) but we are already working on a connector for MongoDB[1] and plan to expand to more DBs in the future, here's the open issue to support DynamoDB[2]. Hopefully Prisma becomes an option for you once we support your favorite DBs! [1]: https://www.notion.so/prismaio/Prisma-Roadmap-50766227b779464ab98899accb98295f?p=9f115ebf4a754069a7d7eaae94dc4651 https://www.notion.so/prismaio/Prisma-Roadmap-50766227b77946... [2]: https://github.com/prisma/prisma/issues/1676 https://github.com/prisma/prisma/issues/1676