Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
aws-lambda-java-libs
Official mirror for interface definitions and helper classes for Java code running on the AWS Lambda platform.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Context: I've seen some commonalities to the work I've been doing lately. In GraphQL/ReScript/Elm, we define records which are basically VO's; data that represent a thing in our domain.
Any React/Angular developer knows why; I need it for List Item/Checkbox state. This spiraled into a lot more business stuff when you'd need context from another part of the app, and "stuff" extra data on the VO. Back-end devs would have no idea what "other parts of the app" meant
Context: I've seen some commonalities to the work I've been doing lately. In GraphQL/ReScript/Elm, we define records which are basically VO's; data that represent a thing in our domain.
Context: I've seen some commonalities to the work I've been doing lately. In GraphQL/ReScript/Elm, we define records which are basically VO's; data that represent a thing in our domain.
In the case of microservices/Lambdas required to respond to GraphQL/AppSync, they have to follow the GraphQL contract and provide all data. So they'll often end up making multiple calls, mapping these DTO's to their own VO's that have all the data they need.
In the case of microservices/Lambdas required to respond to GraphQL/AppSync, they have to follow the GraphQL contract and provide all data. So they'll often end up making multiple calls, mapping these DTO's to their own VO's that have all the data they need.
Any React/Angular developer knows why; I need it for List Item/Checkbox state. This spiraled into a lot more business stuff when you'd need context from another part of the app, and "stuff" extra data on the VO. Back-end devs would have no idea what "other parts of the app" meant