As you may know, Vapor offers support for deploying your serverless application to a region of your choice. Starting today, you may also choose the Asia Pacific (Osaka) region when starting a new project on Vapor. This new region offers low latency for customers seeking to serve end-users in Western Japan.
image
Please check out the AWS blog announcement of this region for more information.
We hope you enjoy this new addition to Laravel Vapor. At Laravel, we're committed to providing you with the most robust and developer friendly PHP experience in the world. If you haven't checked out Vapor, now is a great time to start! You can create your account today at: vapor.laravel.com.
This article was originally posted, with additional formatting, on my personal blog at laravel serializes model Background When dispatching an object onto the queue, behind the scenes Laravel is recursively serializing the object and all of its properties into a string representation that is then written to the queue. There it awaits a queue worker to retrieve it from the queue and unserialize it back into a PHP object (Phew!). Problem When complicated objects are serialized, their string representations can be atrociously long, taking up unnecessary resources both on the queue and application servers. Solution Because of this, Laravel offers a trait called SerializesModels which, when added to an object, finds any properties of type Model or Eloquent\Collection during serialization and replaces them with a plain-old-PHP-object (POPO) known as a ModelIdentifier. These identifier objects represent the original properties Model type and ID, or IDs in the case of an Eloquent\Collection,