I wish managed databases were available but I know they are working on bringing it back for new customers. I liked the example of how to use Docker Swarm. I almost wish it was a more easier example of maybe a simple we app showed the hostname to know the frontend was being load balance between the two nodes.
Great video.. but I wonder if your networks (frontend, backend) are overlays? Or it's only working on one machine only. Because all you did was making Dockerfiles and push them. We never saw how it really works. Would be more simple if it was only docker-compose file without Dockerfile. Ex: Nginx, postgresql, traefik, authelia (authentik), django, redis, heimdall, socket-proxy... etc... I think the biggest problem with swarm, is communication between machines. How to share the same networks for databases or reverse proxies. How to share secrets or environment variables. Why should we use replicas. What are "services". Why do we push images and where do we push it? Should we create a registry container? Can consul be a good thing?
For a recommendation, databases should be in different servers from applications. But for a tight budget, setup application and database on the same server.
Databases are different beasts than applications because require different replication, loadbalancing and snapshotting strategies based on master-replica relations. These operations are not easy to manage that's why most of the time architects just delegate those tasks to dedicated database entities like those linodes he chose.
Very nice walkthrough of Docker Swarm.
Will surely try to do what you showed :)
hey, where did we configured, which services to be rum on which instances??
This is great! This will make scaling much easier then what I can do right now
I wish managed databases were available but I know they are working on bringing it back for new customers.
I liked the example of how to use Docker Swarm. I almost wish it was a more easier example of maybe a simple we app showed the hostname to know the frontend was being load balance between the two nodes.
Greate teacher
Great video.. but I wonder if your networks (frontend, backend) are overlays? Or it's only working on one machine only. Because all you did was making Dockerfiles and push them. We never saw how it really works. Would be more simple if it was only docker-compose file without Dockerfile. Ex: Nginx, postgresql, traefik, authelia (authentik), django, redis, heimdall, socket-proxy... etc...
I think the biggest problem with swarm, is communication between machines. How to share the same networks for databases or reverse proxies. How to share secrets or environment variables. Why should we use replicas. What are "services". Why do we push images and where do we push it? Should we create a registry container? Can consul be a good thing?
is most of the companies using go language or python sir
Great tutorial! Thanks!
Is there any reasons why you moving postgres to a seperate linode?
For a recommendation, databases should be in different servers from applications. But for a tight budget, setup application and database on the same server.
Databases are different beasts than applications because require different replication, loadbalancing and snapshotting strategies based on master-replica relations. These operations are not easy to manage that's why most of the time architects just delegate those tasks to dedicated database entities like those linodes he chose.
Can u please share with us the github repository for the application
You can find the GitHub repo for this project here:
github.com/sidpalas/devops-directive-docker-course
how to deploy a next js app to Linode?
Hey there! This guide will get you started with Next.js on Linode:
www.linode.com/docs/guides/getting-started-next-js/
@@AkamaiDeveloper q
❤❤❤
@@RofikulIslam-os5hq।।a,।àk🎉
@@AkamaiDeveloper🎉
a
😅 0:44 😅
K
😅
❤️❤️
BbjhuUKy😮