So I've given you a bunch of reasons why I think that building a Web application engo is a really good
idea.
And let me give you an example to show you just how much more efficient something written and go is
than something written in.
So right now I'm looking at lineout.
And Lynard is a service that allows you to have virtual private servers.
So Digital Ocean has the same thing.
They're called droplets.
Later in this course will be deploying a A server.
I'm going to use Lynard.
You can use whatever you want if you choose to deploy one.
But I have two servers I want to show you.
One is called Ghost Server.
And let's look at that.
That's in Toronto.
It has four CPU cores.
It has eight gigs of RAM and 160 gigs of storage.
So that's go server.
And the other one is called Romulus.
And Romulus also has four CPU cores, also has eight gigs of RAM and also has 160 gigs of storage.
And I'm going to go over to my I'll just hide this and go over to here.
Let me get there eventually.
OK, let me bring up my terminals so I have two windows open.
One is connected to go server.
This is a server that is running some go applications.
And if I go to VA, W-W and else, other sites and else you'll see I have this many applications.
These are all go applications, every single one of them, except for Disk and Tusi data.
Everything else is an application written and go.
And they are there are a lot.
There's what one, two, three, four, five, six, seven plus eight is fifteen plus seven is 22 applications
all written and go all running on this server, this one Romulus.
Let's go to our Web sites and else.
It has about the same number of applications and every one of these is written in.
The majority of them are there might be one static site there, but the majority of them are actually
written using Laravel in P.
So I'm going to now run an application called Top on this server and I'll run the same application called
Top on this server.
Remember, the one on the left is running go applications.
Look at its load, average point zero four and look at the load average on this one point eight nine.
So it's using far more resources to run about the same number of websites, which all have about the
same amount of traffic, a fair bit of traffic, but it's far more efficient to run something and go
than it is to run something in.
And look at the memory usage again.
You know, we have much less memory being used in go than there is over here on on P.
And if you look at the uptime, this server has been running for 11 days and the uptime for the server,
it's been running for 17 days.
So they've been running for about the same amount of time.
And yet the load usage, the amount of system resources consumed by Laravel is vastly higher than it
is in go, so that if nothing else is a compelling reason to use a comp. language rather than an interpreted
language.