Quasi-jacobean

171 total views, 0 views today

The yarn is a package manager for javascript, like maven is for java. Just like yarn there is another package manager, that is the most famous, called npm. According to this post, yarn was born after the facebook team had some problems with npm.

This tutorial is based on yarn website, you can see it here.

So let’s start! To install yarn we need to add the package repository with the following commands:

$ curl -sS /dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -

and:

$ echo "deb /dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list deb

With the package repository added, just run the command to install, but you must confirm the download when requested:

$ sudo apt-get update && sudo apt-get install yarn

After this if everything is ok you can check the yarn version installed like this:

$ yarn -v

That is it!
Hope that you enjoyed.

Feel free to leave your comments.

See you next time!

 

impose

265 total views, no views today

So, what Cloud Computing means?

If you have questions about cloud computing yet, you should read the topics below to stay tuned.

1. Why “cloud”?

This expression was born because is very normal to use graphic representations in cloud format to show the internet as part of the process on IT diagrams, representing something that you can’t touch.

Is that the reason of why people call everything that is on the internet of “Cloud”.

2. “Infinitely available” and “flexible” computing

In the Cloud, the major advantage is the flexibility to create and destroy resources. You don’t need to stay with a computer if you don’t need it anymore.

This capability changed radically the way people buy resources for their business because now you pay exactly for what you are using.

If your audience grows up, you add more computers (infinite resources) on your infrastructure. If your audience goes down, you just destroy these extra computers.

3. Cost-benefit ratio

The image below shows a traditional data center vs cloud provider (AWS in this case).

Pay attention to the BLUE line that is our computational force and the RED line that is our demand/customer.

Look that in Traditional architecture we always lose money  🙁

If we don’t have enough demand our computer is underused. But if our demand grows up fast, probably a part of our customers will have problems to use our solution.

On a Cloud environment as you can see the computational force is flexible and you just pay for what you really are using.

 


As you can imagine, has a lot of Cloud Computing aspects that we didn’t talk here yet. This was a short briefing.

Hope that you enjoyed.

Feel free to leave your comments.

See you next time!