There’s no doubt that the main skill of any software developer is to write good code regardless of the programming language and the platform he is specialized on. Besides this fundamental set of skills there’s an additional one which is oftentimes overlooked or undervalued by many developers.
In the past years I’ve worked with various clients to migrate existing workloads to the cloud and to build new ones in a cloud-native fashion. Most of the time the main goal for those projects was to reduce costs. However, in my opinion there’s just one reason for any business to leverage the cloud.
Slack revolutionized the way how people communicate and collaborate in companies, projects and communities. Following the huge success of Slack Microsoft launched Teams to offer a similar tool. Having worked with both applications on a daily basis I’d like to give my take on why I think Teams is only a poor copy of Slack.
AWS provides a set of services for supporting the DevOps tool chain. With these tools it’s easy to run the complete DevOps Pipeline on AWS. Here are 6 reasons why everyone using AWS should use these tools for automating their processes for building, testing and deploying their applications.
Automating the deployment of your application is key for fast development cycles. CodeDeploy is a service offered by AWS to perform this task. This post shows how to integrate AWS Lightsail and CodeDeploy to achieve automation of deployments.
Scaling web applications can be tricky. One obstacle is the handling of shared data, like images uploaded by users. A common solution is the usage of a shared file system. For these kinds of use cases AWS provides the Elastic File System (EFS). Fortunately, it can also be used with AWS Lightsail using three easy steps.
AWS Lightsail is a set of services offered by AWS which can be used to run the infrastructure needed for hosting web applications: virtual servers, managed databases and load balancers. Launching the infrastructure through infrastructure as code tools is not well supported yet. Fortunately, this can be done with little effort by using the AWS CLI instead.
One of the fundamental characteristics of the cloud is metered billing: You only pay for what you actually use. However, this makes it kind of unpredictable what you are charged at the end of the month. AWS Budgets help you to keep an eye on your spending and getting notified once you exceed pre-defined thresholds.
In previous blog posts I’ve shown how to build serverless microservices which provide a REST API. Each service consists of a bunch of Lambda functions triggered by the AWS API Gateway. In a real world scenario multiple microservices would compose an application exposed through a single domain. To achieve this, a custom domain can be used.