I don't use offline simulations, except when I do server-side rendering and need to see the rendered HTML. Otherwise, sls invoke local/sam local invoke is sufficient for REST APIs. Beyond that, I have integration and e2e tests.
-
-
-
Interesting! What about your e2e tests? They run online on a test environment right?
- Još 4 druga odgovora
Novi razgovor -
-
-
It's a hard question, and I go back and forth. Depends a lot on your architecture. Are you just an HTTP backend and a datastore? You can get pretty far with local dev. Are you using a lot of native integrations, like SQS, Kinesis, DDB streams, step functions? Much harder.
-
Amplify mock will get you pretty far including Cognito JWTs
Kraj razgovora
Novi razgovor -
-
-
When I hear devs talk of offline/local serverless dev workflow, what they usually really mean is fast and isolated. I almost never use any of the “offline” emulators
-
The “integration” mode I mention here is usually fast enough for me... https://t.co/QWIqAxXX98 https://twitter.com/paulswail/status/1224030317708750851?s=21 …
- Još 2 druga odgovora
Novi razgovor -
-
-
We completely support offline for http://arc.codes supported services: ApiG, Dynamo, SNS, SQS, etc. People will probably say it's impossible or hard but the reality is AWS is *very stable* for these services. If you are building a web app check it out.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I don't use it simply because the cloud services are online and you should adapt your development workflow to be online focused. When you start to create systems to get it offline, funny things can happen because of differences between the two.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I tend to use a local environment purely as a way to execute function locally to catch pesky errors. AWS-SDK-mock node module makes this easy along with serverless-mocha-plugin
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.