11–20 of 30 posts
> Docker and kubernetes are everywhere. I'm willing to bet a dollar not even 1% of deployments use these. The world is a pretty big place.
Would love to hear what the best practices for a new greenfield project, say Django-Postgres-Redis-Nginx, would be if you wanted to avoid containers for some time.
But ansible is cool too.
Funny you say that because we don't use containers yet and definitely have no reason to use Kubernetes. However, we are looking at switching to AWS ECS with fargate for our SAAS. If anyone wants to consult, hit me up.
Earlier quoted context omitted.
Would love to hear what the best practices for a new greenfield project, say Django-Postgres-Redis-Nginx, would be if you wanted to avoid containers for some time.
Yeah nearly every Django starter/cookiecutter I see is dockerized.
I have my own ansible setup that I use, but it feels old. It works just fine, but I want to see what I can improve.
OP, is your only experience working with technology companies and trendy startups trying to hit some mega-million valuation? The real world is a lot more messy than the best practices that tech companies come up with. Go work for some local warehouse or AC repair company's IT departments. They might have some technology for managing inventory or scheduling appointments or billing or any one of a hundred tasks that is…
I've been in the industry for 20+ years. My opinion is that the extra complexity that comes from containarization is not necessary at many of the early startups. The benefits are not needed and the costs are hard to see but non-trivial. The companies I worked with either were slowly moving towards containarization, or were already there before I joined. I always thought that it is premature. My pet projects never use…
Yeah, go hog-wild and do whatever makes you happy as a solo act, so long as you do things securely and protect your users. By definition, there's no conflict between developers possible.
You might pay a price later if you do things your way and get too successful, but that's a better problem to have than being too late to market with your great idea just because you were trying to do things "the right way".
Funny you say that because we don't use containers yet and definitely have no reason to use Kubernetes. However, we are looking at switching to AWS ECS with fargate for our SAAS. If anyone wants to consult, hit me up.
Can you share more about your current setup, and what is the motivating factor for the move to AWS ECS?
- Development consistency and portability. Right now, we dont containerize and every developer install various tools/libraries to support our tech stack. We are looking at docker to solve this for us as our dev team is 15+ and growing
- We are moving away from Single Tenant to Multi Tenat SAAS architecture for various business reasons and we now need a much more resilient architecture to handle about few thousand RPS with mostly write heavy requests. We are a bit hesitant on using stuff like EC2 and figure out how to allocate CPU and Memory based on usages and instead looking at EC2. I am sure an argument can be made that its not needed but this seems like the best option to handle both dev and production use case.
Thoughts ?
Funny you say that because we don't use containers yet and definitely have no reason to use Kubernetes. However, we are looking at switching to AWS ECS with fargate for our SAAS. If anyone wants to consult, hit me up.