npm install --save serverless-sequelize-migrations
plugins: - serverless-sequelize-migrations
You can check whether the plugin is ready to be used through the terminal. To do so, type the following command on the CLI:
the console should display SequelizeMigrations as one of the available plugins in your Serverless project.
For the plugin to work correctly, you have to set the database information as environment variables on the service provider section as follows:
provider: environment: DB_DIALECT: 'database_dialect' /* one of 'mysql' | 'mariadb' | 'postgres' | 'mssql' */ DB_NAME: 'database_name' DB_USERNAME: 'database_username' DB_PASSWORD: 'database_password' DB_HOST: 'database_host' DB_PORT: 'database_port'
or by using DB_CONNECTION_URL
provider: environment: DB_CONNECTION_URL: database_dialect://database_username:database_password@database_host:database_port/database_name`
Replace the variables with the information of your own database.
Obs: This plugin does not have support to create the database itself.
As per Sequelize docs, you'll have to manually install the driver for your database of choice:
# One of the following: $ npm install --save pg pg-hstore # Postgres $ npm install --save mysql2 # MySQL $ npm install --save mariadb # MariaDB $ npm install --save tedious # Microsoft SQL Server
To see the available commands of the plugin, run
sls migrations on the terminal. The following should appear:
Plugin: SequelizeMigrations migrations .................... Sequelize migrations management for Serverless migrations create ............. Create a migration file migrations up ................. Execute all pending migrations migrations down ............... Rolls back one or more migrations migrations reset .............. Rolls back all migrations migrations list ............... Shows a list of migrations --path / -p ........................ Specify the migrations path (default is './migrations') --verbose / -v ..................... Shows sequelize logs
For any of these commands, you can specify two parameters:
--pathto inform the path of migrations on your project.
--verboseto show sequelize execution logs during the operations.
In order to see the options of each command individually, you can run
sls migrations <command> --help on the terminal.
The commands (those that have some option) and it's options are presented below:
--name / -n (required) ... Specify the name of the migration to be created
--rollback / -r .......... Rolls back applied migrations in case of error (default is false) --dbDialect ........................ Specify the database dialect (one of: 'mysql', 'mariadb', 'postgres', 'mssql') --dbHost ........................... Specify the database host --dbPort ........................... Specify the database port --dbName ........................... Specify the database name --dbUsername ....................... Specify the database username --dbPassword ....................... Specify the database password
--times / -t ............. Specify how many times to roll back (default is 1) --name / -n .............. Specify the name of the migration to be rolled back (e.g. "--name create-users.js") --dbDialect ........................ Specify the database dialect (one of: 'mysql', 'mariadb', 'postgres', 'mssql') --dbHost ........................... Specify the database host --dbPort ........................... Specify the database port --dbName ........................... Specify the database name --dbUsername ....................... Specify the database username --dbPassword ....................... Specify the database password
--status / -s ............ Specify the status of migrations to be listed (--status pending [default] or --status executed) --dbDialect ........................ Specify the database dialect (one of: 'mysql', 'mariadb', 'postgres', 'mssql') --dbHost ........................... Specify the database host --dbPort ........................... Specify the database port --dbName ........................... Specify the database name --dbUsername ....................... Specify the database username --dbPassword ....................... Specify the database password
You can also define a migrations path variable on the custom section of your project service file.
custom: migrationsPath: './custom/migrations/path'
Important: if you inform the --path option through the CLI, this configuration will be ignored.
Source Code: https://github.com/manelferreira/serverless-sequelize-migrations
License: MIT license
The moving of applications, databases and other business elements from the local server to the cloud server called cloud migration. This article will deal with migration techniques, requirement and the benefits of cloud migration.
In simple terms, moving from local to the public cloud server is called cloud migration. Gartner says 17.5% revenue growth as promised in cloud migration and also has a forecast for 2022 as shown in the following image.
#cloud computing services #cloud migration #all #cloud #cloud migration strategy #enterprise cloud migration strategy #business benefits of cloud migration #key benefits of cloud migration #benefits of cloud migration #types of cloud migration
Serverless M (or Serverless Modular) is a plugin for the serverless framework. This plugins helps you in managing multiple serverless projects with a single serverless.yml file. This plugin gives you a super charged CLI options that you can use to create new features, build them in a single file and deploy them all in parallel
Currently this plugin is tested for the below stack only
Make sure you have the serverless CLI installed
# Install serverless globally $ npm install serverless -g
To start the serverless modular project locally you can either start with es5 or es6 templates or add it as a plugin
# Step 1. Download the template $ sls create --template-url https://github.com/aa2kb/serverless-modular/tree/master/template/modular-es6 --path myModularService # Step 2. Change directory $ cd myModularService # Step 3. Create a package.json file $ npm init # Step 3. Install dependencies $ npm i serverless-modular serverless-webpack webpack --save-dev
# Step 1. Download the template $ sls create --template-url https://github.com/aa2kb/serverless-modular/tree/master/template/modular-es5 --path myModularService # Step 2. Change directory $ cd myModularService # Step 3. Create a package.json file $ npm init # Step 3. Install dependencies $ npm i serverless-modular --save-dev
If you dont want to use the templates above you can just add in your existing project
plugins: - serverless-modular
Now you are all done to start building your serverless modular functions
The serverless CLI can be accessed by
# Serverless Modular CLI $ serverless modular # shorthand $ sls m
Serverless Modular CLI is based on 4 main commands
sls m init
sls m feature
sls m function
sls m build
sls m deploy
sls m init
The serverless init command helps in creating a basic
.gitignore that is useful for serverless modular.
.gitignore for serverless modular looks like this
#node_modules node_modules #sm main functions sm.functions.yml #serverless file generated by build src/**/serverless.yml #main serverless directories generated for sls deploy .serverless #feature serverless directories generated sls deploy src/**/.serverless #serverless logs file generated for main sls deploy .sm.log #serverless logs file generated for feature sls deploy src/**/.sm.log #Webpack config copied in each feature src/**/webpack.config.js
The feature command helps in building new features for your project
This command comes with three options
--name: Specify the name you want for your feature
--remove: set value to true if you want to remove the feature
|--basePath||-p||❎||string||same as name|
Creating a basic feature
# Creating a jedi feature $ sls m feature -n jedi
Creating a feature with different base path
# A feature with different base path $ sls m feature -n jedi -p tatooine
Deleting a feature
# Anakin is going to delete the jedi feature $ sls m feature -n jedi -r true
The function command helps in adding new function to a feature
This command comes with four options
--name: Specify the name you want for your function
--feature: Specify the name of the existing feature
|--path||-p||❎||string||same as name|
Creating a basic function
# Creating a cloak function for jedi feature $ sls m function -n cloak -f jedi
Creating a basic function with different path and method
# Creating a cloak function for jedi feature with custom path and HTTP method $ sls m function -n cloak -f jedi -p powers -m POST
The build command helps in building the project for local or global scope
This command comes with four options
--scope: Specify the scope of the build, use this with "--feature" tag
--feature: Specify the name of the existing feature you want to build
Saving build Config in serverless.yml
You can also save config in serverless.yml file
custom: smConfig: build: scope: local
all feature build (local scope)
# Building all local features $ sls m build
Single feature build (local scope)
# Building a single feature $ sls m build -f jedi -s local
All features build global scope
# Building all features with global scope $ sls m build -s global
The deploy command helps in deploying serverless projects to AWS (it uses
sls deploy command)
This command comes with four options
--sm-parallel: Specify if you want to deploy parallel (will only run in parallel when doing multiple deployments)
--sm-scope: Specify if you want to deploy local features or global
--sm-features: Specify the local features you want to deploy (comma separated if multiple)
Saving deploy Config in serverless.yml
You can also save config in serverless.yml file
custom: smConfig: deploy: scope: local parallel: true ignoreBuild: true
Deploy all features locally
# deploy all local features $ sls m deploy
Deploy all features globally
# deploy all global features $ sls m deploy --sm-scope global
Deploy single feature
# deploy all global features $ sls m deploy --sm-features jedi
Deploy Multiple features
# deploy all global features $ sls m deploy --sm-features jedi,sith,dark_side
Deploy Multiple features in sequence
# deploy all global features $ sls m deploy --sm-features jedi,sith,dark_side --sm-parallel false
As we know that laravel migration provides very simple way to create database table structure. We need to create migration file and write table structure then migrate that migration. Sometimes we need to rollback that migration. So here we will discuss about the migration rollback in laravel.
We can run the rollback artisan command to rollback on a particular step. We can execute the following artisan command.
php artisan migrate:rollback --step=1
Every time when we will rollback, we will get the last batch of migration.
**Note: **This rollback command will work on laravel 5.3 or above version. For the version below 5.3, there is no command available for migration rollback in laravel.
We can also use the following command to rollback and re migrate.
php artisan migrate:refresh --step=2
It will rollback and remigrate last two migration.
You can also checkout the article for executing single migration by clicking on the link below.
#laravel #how to perform rollback migration in laravel #laravel migration rollback #migration refresh in laravel #migration rollback batch in laravel #migration rollback for one specific migration #migration rollback in laravel
Sometimes while working on a laravel application, we just need to migrate only single or specific migration. If we run normal migrate command it will migrate all the migrations written in the application. Here i will let you know to migrate single migration in laravel.
Migrations play very important role for aplication’s database structure. We just need to create migrations in the application for each table which you want and whenever we migrate these migrations. New table structure would be created.
For new developers or setting up new environment, we do not need to backup of table structure. We will just need to run the migrations. It will automatically create desired tables in the database connected from the laravel application.
We can run all the migrations using the command below.
php artisan migrate
Now if we want to run only one migration or a specific migration, we will need to define a path parameter and will need to specify the path of that migration file which we want to run like below.
php artisan migrate --path=/database/migrations/my_migration.php
It will migrate only my_migration.php file. Here, you will need to replace file name from your own migration file.
You can also learn how to add column in existing daatbase table through migration by clicking on the below.
#laravel #how to migrate single migration file #laravel migration #laravel single migration #migrate specific migration in laravel
In the past few years, especially after Amazon Web Services (AWS) introduced its Lambda platform, serverless architecture became the business realm’s buzzword. The increasing popularity of serverless applications saw market leaders like Netflix, Airbnb, Nike, etc., adopting the serverless architecture to handle their backend functions better. Moreover, serverless architecture’s market size is expected to reach a whopping $9.17 billion by the year 2023.
Why use serverless computing?
As a business it is best to approach a professional mobile app development company to build apps that are deployed on various servers; nevertheless, businesses should understand that the benefits of the serverless applications lie in the possibility it promises ideal business implementations and not in the hype created by cloud vendors. With the serverless architecture, the developers can easily code arbitrary codes on-demand without worrying about the underlying hardware.
But as is the case with all game-changing trends, many businesses opt for serverless applications just for the sake of being up-to-date with their peers without thinking about the actual need of their business.
The serverless applications work well with stateless use cases, the cases which execute cleanly and give the next operation in a sequence. On the other hand, the serverless architecture is not fit for predictable applications where there is a lot of reading and writing in the backend system.
Another benefit of working with the serverless software architecture is that the third-party service provider will charge based on the total number of requests. As the number of requests increases, the charge is bound to increase, but then it will cost significantly less than a dedicated IT infrastructure.
Defining serverless software architecture
In serverless software architecture, the application logic is implemented in an environment where operating systems, servers, or virtual machines are not visible. Although where the application logic is executed is running on any operating system which uses physical servers. But the difference here is that managing the infrastructure is the soul of the service provider and the mobile app developer focuses only on writing the codes.
There are two different approaches when it comes to serverless applications. They are
Backend as a service (BaaS)
Function as a service (FaaS)
Moreover, other examples of third-party services are Autho, AWS Cognito (authentication as a service), Amazon Kinesis, Keen IO (analytics as a service), and many more.
FaaS serverless architecture is majorly used with microservices architecture as it renders everything to the organization. AWS Lambda, Google Cloud functions, etc., are some of the examples of FaaS implementation.
Pros of Serverless applications
There are specific ways in which serverless applications can redefine the way business is done in the modern age and has some distinct advantages over the traditional could platforms. Here are a few –
🔹 Highly Scalable
The flexible nature of the serverless architecture makes it ideal for scaling the applications. The serverless application’s benefit is that it allows the vendor to run each of the functions in separate containers, allowing optimizing them automatically and effectively. Moreover, unlike in the traditional cloud, one doesn’t need to purchase a certain number of resources in serverless applications and can be as flexible as possible.
As the organizations don’t need to spend hundreds and thousands of dollars on hardware, they don’t need to pay anything to the engineers to maintain the hardware. The serverless application’s pricing model is execution based as the organization is charged according to the executions they have made.
The company that uses the serverless applications is allotted a specific amount of time, and the pricing of the execution depends on the memory required. Different types of costs like presence detection, access authorization, image processing, etc., associated with a physical or virtual server is completely eliminated with the serverless applications.
🔹 Focuses on user experience
As the companies don’t always think about maintaining the servers, it allows them to focus on more productive things like developing and improving customer service features. A recent survey says that about 56% of the users are either using or planning to use the serverless applications in the coming six months.
Moreover, as the companies would save money with serverless apps as they don’t have to maintain any hardware system, it can be then utilized to enhance the level of customer service and features of the apps.
🔹 Ease of migration
It is easy to get started with serverless applications by porting individual features and operate them as on-demand events. For example, in a CMS, a video plugin requires transcoding video for different formats and bitrates. If the organization wished to do this with a WordPress server, it might not be a good fit as it would require resources dedicated to serving pages rather than encoding the video.
Moreover, the benefits of serverless applications can be used optimally to handle metadata encoding and creation. Similarly, serverless apps can be used in other plugins that are often prone to critical vulnerabilities.
Cons of serverless applications
Despite having some clear benefits, serverless applications are not specific for every single use case. We have listed the top things that an organization should keep in mind while opting for serverless applications.
🔹 Complete dependence on third-party vendor
In the realm of serverless applications, the third-party vendor is the king, and the organizations have no options but to play according to their rules. For example, if an application is set in Lambda, it is not easy to port it into Azure. The same is the case for coding languages. In present times, only Python developers and Node.js developers have the luxury to choose between existing serverless options.
Therefore, if you are planning to consider serverless applications for your next project, make sure that your vendor has everything needed to complete the project.
🔹 Challenges in debugging with traditional tools
It isn’t easy to perform debugging, especially for large enterprise applications that include various individual functions. Serverless applications use traditional tools and thus provide no option to attach a debugger in the public cloud. The organization can either do the debugging process locally or use logging for the same purpose. In addition to this, the DevOps tools in the serverless application do not support the idea of quickly deploying small bits of codes into running applications.
#serverless-application #serverless #serverless-computing #serverless-architeture #serverless-application-prosand-cons