#serverless

39 tweets

Just had quite the AHA! moment when talking to an applicant ... I am mostly not
coding backend code any more, but much more integration and automation code.
#serverless solves the heavy lifting, but tying it all together is a task that
needs a lot of work. #nobackend

I think this is what a proper #serverless architecture diagram should look like:

  • focus on the scenario / feature (store and retrieve temperature from a device)
  • show the flow of data
  • show the services involved to enable flow
  • link to source code where they are defined.
    Embedded Photo
Replying to @coderbyheart

For Xeris, #Serverless' main advantage is the reduced cost. However it also
simplified the provisioning of multiple instances of their solution, for
testing, preview and development. Some not so serverless services need special
attention.

Replying to @coderbyheart

We also give you a technical home assignment (without a time limit) where we ask
you to implement a cloud component base on a real-world example from one of our
projects in a #serverless fashion on the #cloud of your choice, so you can focus
on providing a great example.