Explorations with tech...

With all the variety of options out there to code your application's infrastructure for the cloud, I recently worked with Pulumi. If you have ever used Hashicorp's Terraform, AWS's Cloudformation or Red Hat's Ansible for designing cloud infrastructure, the one thing they all have in common is a framework of rules and standards which have to be followed. Pulumi differs from all of them by giving you the option to pick the programming language you want to work with when designing for the cloud.

Working with media for the web means having it optimized for best performance. Using a CDN to distribute static assets is great, but having bulkier file sizes is still inefficient.

At re:Inevent(2017), AWS made an announcement for an ambitious feature which they would launch in 2018 - Aurora Serverless. It's been a highly anticipated feature ever since AWS made the announcement. Aurora as you may already know is quite a popular relational database service offered by AWS which is pretty much known for it's outstanding performance. Now taking that one step further is they made it serverless.

Serverless technologies have been around for quite some time now. They are primarily useful for executing event driven use cases( IoT, mobile and the like) with great performance. Almost every notable cloud provider today offer their own implementations of developing serverless functions. Amazon Web Services was first to market with their serverless product Lambda and has steadily evolved ever since.

For someone who has recently stepped into managing infrastructure on the cloud, the tools available at one's disposal could 'cloud' your judgement. There is basically no right or wrong choice because it all boils down to the task at hand and what helps you achieve your goal with minimal effort. If anything, flexibility should be a prime element because if things change in future you shouldn't have to put it in a lot of effort for modifications.