When building applications, one has to factor failures into the design. An application may fail because of a bug in the code. The underlying infrastructure running the application can fail, whether it is a bare metal server or a virtual machine. The network connectivity can fail intermittently. A datacenter may lose power and the backup generator may not start either. That's already a lot of risks to cover and to protect from.
Developers do not like to write the same thing twice. The DRY principle is one example of this. Similarly they don't like having to go through tons of clicks in a user interface to setup an environment. Consequently shell scripts have been long used by system administrators and developers to automate repetitive, error-prone and uninteresting tasks.
Learn how to organize your project with multiple deployment environments
Looking to build your next project on the IBM Cloud and not sure where to start?
Serverless computing platforms give developers a rapid way to build APIs without servers. OpenWhisk supports automatic generation of REST API for actions exposed by API Gateway. When the capabilities provided by the API Gateway do not cover all usecases you have for an API - such as publishing it in a developer portal or performing advanced mapping, transformation, validation, you can migrate to the API Connect service.
Logistics Wizard is a reimagined supply chain optimization system for the 21st century. In this post, we show how to deploy its microservices in Kubernetes.
As your app gets more users and traffic how do you scale its components to handle the additional load?