Skip to main content

Deliver SaaS According Twelve-Factor App

If you haven't heard of the twelve-factor app, it gives us a recommendation or a methodology for developing SaaS or web apps structured into twelve items. The recommendation has some connections with microservice architecture and cloud-native environments which become more popular today. We can learn the details on its website. In this post, we will do a quick review of the twelve points.


One Codebase Multiple Deployment

We should maintain only one codebase for our application even though the application may be deployed into multiple environments like development, staging, and production. Having multiple codebases will lead to any kinds of complicated issues.


Explicitly State Dependencies

All the dependencies for running our application should be stated in the project itself. Many programming languages have a kind of file that maintains a list of the dependencies like package.json in Node.js. We should also be aware of the dependencies related to the platform that runs our application like tools that are installed globally in the operating system.

The recommendation is to avoid the use of global scope dependencies at all. We can run our application in an isolated or virtual environment. This also prevents other processes in the system from affecting our application in some ways.


Maintain Configuration in The Environment

Maintaining configuration in the environment where our application running helps us to easily maintain the structure of the configuration of our application in multiple deployments. Keeping all configurations for all environments in a variable is discouraged because that just adds complexity. We can just populate a configuration for an environment into a variable in our code in which the value can be retrieved from a variable or secret manager in our CI/CD platform.


Attachable Backing Services

Any backing services for our application like databases or queue servers should be easily attached or detached so that we can swiftly switch or replace the service, for example, from a local database to cloud-based services. It is also related to the principle of multiple deployments where backing service can vary.


Separate Code, Build, and Run

This part means we shouldn't modify the released version of our application on the fly like for quick patching of an issue. Every release is read-only, we should modify the code in the development phase and release a new version.


Stateless Processes

This is the solution for an easy scaling out of our application. If our application is stateful which means certain values like sessions are tied to the runner engine or the machine, that will hinder us from scaling out with ease.


Binding Service to Port

We should allow our application to be accessed through a certain URL with a specific port. This dispels the need for a web server to expose the services of our application.


Concurrent Processes

We can categorize jobs in our application into several types. Then, the jobs can be implemented as modules that can run concurently to each other. This will help us to scale up only certain modules that are necessary.


Fast Startup and Graceful Termination

Our application should be able to be started within seconds and maintain termination well so that there is no job or data lost, especially in a microservice environment with several concurrent workers. Applying a mechanism like create before destroy in the deployment life-cycle can be helpful.


Similarity of Environments in Development Phases

Even though there are various adapters for anything, maintaining the similarity of technology or backing services in all environments is preferable. With an adapter, we can make MySQL and PostgreSQL interchangeable but there must be trade-offs and the absence of some features. Besides the technological aspects, gaps in people/teams or development processes should be managed too. We may leverage more container-based services to let the development environment have similar technology to the production environment.


Logs as Stream of Events

We don't need to make our application to manage its logs itself. Let our application expose a stream of events unbuffered into stdout or using third-party tools that are specified to manage and analyze logs.


Administration Tasks as One-Off Processes

Administration tasks like validating data or migrating databases should be implemented as one-off processes. This can be run using the same platform that we use for developing our main application. Most platforms today support REPL implementation where we can create a script and run it directly in a terminal session.


Comments

Popular posts from this blog

Configuring Swap Memory on Ubuntu Using Ansible

If we maintain a Linux machine with a low memory capacity while we are required to run an application with high memory consumption, enabling swap memory is an option. Ansible can be utilized as a helper tool to automate the creation of swap memory. A swap file can be allocated in the available storage of the machine. The swap file then can be assigned as a swap memory. Firstly, we should prepare the inventory file. The following snippet is an example, you must provide your own configuration. [server] 192.168.1.2 [server:vars] ansible_user=root ansible_ssh_private_key_file=~/.ssh/id_rsa Secondly, we need to prepare the task file that contains not only the tasks but also some variables and connection information. For instance, we set /swapfile  as the name of our swap file. We also set the swap memory size to 2GB and the swappiness level to 60. - hosts: server become: true vars: swap_vars: size: 2G swappiness: 60 For simplicity, we only check the exi

Rangkaian Sensor Infrared dengan Photo Dioda

Keunggulan photodioda dibandingkan LDR adalah photodioda lebih tidak rentan terhadap noise karena hanya menerima sinar infrared, sedangkan LDR menerima seluruh cahaya yang ada termasuk infrared. Rangkaian yang akan kita gunakan adalah seperti gambar di bawah ini. Pada saat intensitas Infrared yang diterima Photodiode besar maka tahanan Photodiode menjadi kecil, sedangkan jika intensitas Infrared yang diterima Photodiode kecil maka tahanan yang dimiliki photodiode besar. Jika  tahanan photodiode kecil  maka tegangan  V- akan kecil . Misal tahanan photodiode mengecil menjadi 10kOhm. Maka dengan teorema pembagi tegangan: V- = Rrx/(Rrx + R2) x Vcc V- = 10 / (10+10) x Vcc V- = (1/2) x 5 Volt V- = 2.5 Volt Sedangkan jika  tahanan photodiode besar  maka tegangan  V- akan besar  (mendekati nilai Vcc). Misal tahanan photodiode menjadi 150kOhm. Maka dengan teorema pembagi tegangan: V- = Rrx/(Rrx + R2) x Vcc V- = 150 / (150+10) x Vcc V- = (150/160) x 5

Installing VSCode Server Manually on Ubuntu

I've ever gotten stuck on updating the VSCode server on my remote server because of an unstable connection between my remote server and visualstudio.com that host the updated server source codes. The download and update process failed over and over so I couldn't remotely access my remote files through VSCode. The solution is by downloading the server source codes through a host with a stable connection which in my case I downloaded from a cloud VPS server. Then I transfer the downloaded source codes as a compressed file to my remote server through SCP. Once the file had been on my remote sever, I extracted them and align the configuration. The more detailed steps are as follows. First, we should get the commit ID of our current VSCode application by clicking on the About option on the Help menu. The commit ID is a hexadecimal number like  92da9481c0904c6adfe372c12da3b7748d74bdcb . Then we can download the compressed server source codes as a single file from the host.

Resize VirtualBox LVM Storage

VirtualBox is a free solution to host virtual machines on your computer. It provides configuration options for many components on our machine such as memory, storage, networking, etc. It also allows us to resize our machine storage after its operating system is installed. LVM is a volume manager in a Linux platform that helps us to allocate partitions in the system and configure the storage size that will be utilized for a specific volume group. There are some points to be noticed when we work with LVM on VirtualBox to resize our storage. These are some steps that need to be performed. 1. Stop your machine before resizing the storage. 2. Set new storage size using GUI by selecting " File > Virtual Media Manager > Properties " then find the desired virtual hard disk name that will be resized. OR , by running a CLI program located in " Program Files\Oracle\VirtualBox\VBoxManage.exe ".  cd "/c/Program Files/Oracle/VirtualBox" ./VBoxManage.exe list

Managing MongoDB Records Using NestJS and Mongoose

NestJS is a framework for developing Node.js-based applications. It provides an additional abstraction layer on top of Express or other HTTP handlers and gives developers a stable foundation to build applications with structured procedures. Meanwhile, Mongoose is a schema modeling helper based on Node.js for MongoDB. There are several main steps to be performed for allowing our program to handle MongoDB records. First, we need to add the dependencies which are @nestjs/mongoose , mongoose , and @types/mongoose . Then, we need to define the connection configuration on the application module decorator. import { MongooseModule } from '@nestjs/mongoose'; @Module({ imports: [ MongooseModule.forRoot('mongodb://localhost:27017/mydb'), ], controllers: [AppController], providers: [AppService], }) Next, we create the schema definition using helpers provided by NestJS and Mongoose. The following snippet is an example with a declaration of index setting and an o

Generate API Documentation Using Swagger Module in NestJS

Swagger provides us a standard to generate API documentation based on the Open API specification. If we use NestJS for building our API providers, we can utilize a tool provided by NestJS in the  @nestjs/swagger  module to generate the documentation automatically in the built time. This module also requires the swagger-ui-express module if we use Express as the NestJS base HTTP handler. Set Swagger configuration First, we need to define Swagger options and instantiate the documentation provider on the main.ts file. import { DocumentBuilder, SwaggerModule } from '@nestjs/swagger'; // sample application instance const app = await NestFactory.create(AppModule); // setup Swagger options const options = new DocumentBuilder() .setTitle('Coffee') .setVersion('1.0') .setDescription('Learn NestJS with coffee') .build(); // build the document const document = SwaggerModule.createDocument(app, options); // provide an endpoint