Nice Video! However, your monothilic application doesn't magically become Microservice with AWS. You should rewrite your code to be able to run all the components in your Monolith independently, which is in fact the hardest part of this process - 9:02 So, it's not about AWS services but rather it's how smartly you will implement your application to act as if it were a micro service!
The basic here is to break the code into micro services. So one large piece of code is broken down into 3 smaller piece of code - This is where in all practical applications most of the time, money and resource go into. Rest is all about how to use the ECS with ALB. The practical monoliths are mammoth & gigantic...
Thank you for the explanation! When the application is bigger and comes with middlewares, services, controllers, schemas, utils, db connections, etc... Should the part of splitting the code be the same here? Do those components need to be written in every microservice? Or what can I do if I need to re-write a part of (for example) some middleware?
Hi, I need some help with your demo, at time 5:45 of the video I see you use the command "cd.." to come back the previous directory and I can see for the path "amazon-ecs-nodejs-microservices-master/2-containerized/services/api" there are directories like "users", "posts" and "threads" which is not the part of the original git project and I know for sure the command you run on the local machine are not creating those directories as well. So could you please tell what those directories contain and if not having these directories while pushing the "api" directory into the "api:latest" repository affects later during the project's Module 2? I would appreciate your help! Thank you.
Hi, How to fix the aws github sample? There is an issue in python file. I posted in github. Can you please check and let me know. github.com/aws-samples/amazon-ecs-java-microservices/issues/12 I tried the below: I saw a fix for the issue here - stackoverflow.com/questions/26243905/valueerror-expecting-property-name-line-1-column-2-char-1 filename = home + '/.docker/config.json' with open(filename, 'r+') as f: data = json.load(f) #eval(data) data['auths'][hostname]['auth'] = ecr_login_token # logger.info('Writing docker configuration as '+str(data) f.seek(0) f.write(json.dumps(eval(data))) f.truncate() Something to do with data = json.load(f). How do we fix it ?
Thank you gilfoyle, I can now deploy perfect microservice architecture
I know it is kind of randomly asking but do anybody know a good website to watch newly released tv shows online?
@Spencer Elliot i would suggest Flixzone. Just google for it :)
@Preston Gary Definitely, have been using flixzone for since march myself :)
@Preston Gary thanks, I signed up and it seems like a nice service :D I appreciate it !!
@Spencer Elliot no problem =)
Nice Video!
However, your monothilic application doesn't magically become Microservice with AWS.
You should rewrite your code to be able to run all the components in your Monolith independently, which is in fact the hardest part of this process - 9:02
So, it's not about AWS services but rather it's how smartly you will implement your application to act as if it were a micro service!
The background music is so disturbing.
The basic here is to break the code into micro services. So one large piece of code is broken down into 3 smaller piece of code - This is where in all practical applications most of the time, money and resource go into. Rest is all about how to use the ECS with ALB. The practical monoliths are mammoth & gigantic...
If you're interested in microservices skip to 9:05. The rest is just docker on AWS.
Thank you for the explanation!
When the application is bigger and comes with middlewares, services, controllers, schemas, utils, db connections, etc... Should the part of splitting the code be the same here? Do those components need to be written in every microservice? Or what can I do if I need to re-write a part of (for example) some middleware?
TJ Miller living his silicon valley life
Thank you, amazing explanation even for who don't speak English
great demo, for this use case microservices really shine.
And what happens when your node app crashes? Container up and down?
Thank you Jon Snow
After updating to task number to 2 for api then not able to access the url i.e microservice. Can you pls suggest
Interesting, Thank you
Very cool and neat demo. Thanks a lot!
The "api" given in path pattern at 12:20 whats is it(at creation of services)...?
Cool and neat but service level communication included video will be more useful
The build command is taking an awfully long time. Its stuck at step 4(Run nmp install).
docker build -t api .
Is this normal?
Nevermind. I restarted the instance and ran, it worked.
total perfect example thx 🙏
Very good! Helped me a lot!
Really good video
great tutorial
Hi,
I need some help with your demo, at time 5:45 of the video I see you use the command "cd.." to come back the previous directory and I can see for the path "amazon-ecs-nodejs-microservices-master/2-containerized/services/api" there are directories like "users", "posts" and "threads" which is not the part of the original git project and I know for sure the command you run on the local machine are not creating those directories as well. So could you please tell what those directories contain and if not having these directories while pushing the "api" directory into the "api:latest" repository affects later during the project's Module 2?
I would appreciate your help! Thank you.
Thank you..I got through my problem!
that was awesome
Nothing but love
Hi,
How to fix the aws github sample? There is an issue in python file. I posted in github. Can you please check and let me know.
github.com/aws-samples/amazon-ecs-java-microservices/issues/12
I tried the below: I saw a fix for the issue here - stackoverflow.com/questions/26243905/valueerror-expecting-property-name-line-1-column-2-char-1
filename = home + '/.docker/config.json'
with open(filename, 'r+') as f:
data = json.load(f)
#eval(data)
data['auths'][hostname]['auth'] = ecr_login_token
# logger.info('Writing docker configuration as '+str(data)
f.seek(0)
f.write(json.dumps(eval(data)))
f.truncate()
Something to do with data = json.load(f). How do we fix it ?
quoting silicon valley, this is the guy of the group with crazy face hair, the other four are the indian, the oriental, the fat and the thin.