31–39 of 39 posts
Are you planning to support other cloud platforms as well?
Hey HN crowd, founder here. The fact that we hit the frontpage somehow broke the new app signup flow. While we are fixing it, we are temporarily redirecting to app.digger.dev (the old UI). Will keep you posted here!
I really like your demo. A question that always comes up when I see these "Heroku-like" replacements on top of AWS/GCP/Azure is who is the target user? A couple years ago, you would have platform teams helping developers launch their stuff. Since then, AWS has tried to make things easier through services like App Runner. Nowadays, if you don't want to manage the instances yourself, you just use a managed service. Pla…
My understanding with Platform teams is that its more than DevOps, its that a core set of engineers building a platform that the rest of engineering can safely (using that word in a relative sense here) build upon, e.g., I may as part of a platform team create core API services that are then exposed to product side teams to develop against, and we work with each other. This is essentially a productivity feature, because it allows for specialists to collaborate over their expertise, as opposed to having lots of full stack generalists managing their own slices of codebases, which results in shipping faster and higher quality product.
I feel like if you need this, you're not using the right platform. I don't see how someone gets the benefits of IaC with this, seems like it just improves the console experience and auto generates crap IaC. Why even use IaC at this point, aside from your tool probably needing it on the backend to deploy things? If you really need this, seems like you'd be better served by the low code solutions on the cloud providers…
That's a very good point. And it is also the very reason we wanted to build smth like this. The question we asked ourselves: why are people leaving PaaS platforms like Heroku? The answer seems to be that people are starting with simple tools (beanstalk, heroku, GAE etc) but then quickly approaching their limits in terms of both features and cost - and move to "native" AWS / GCP / Azure. At this point they need to reb…
Where is model really works is what companies like Railway and render has done. You also own the compute and storage and retail that to end users. Your potential end users would rather prefer easily to use cloud provider than going to AWS and setting up PaaS on top of that. Your potential customer has got the time and effort for that.
I really like your demo. A question that always comes up when I see these "Heroku-like" replacements on top of AWS/GCP/Azure is who is the target user? A couple years ago, you would have platform teams helping developers launch their stuff. Since then, AWS has tried to make things easier through services like App Runner. Nowadays, if you don't want to manage the instances yourself, you just use a managed service. Pla…
It also impacts team sizing and the minimum number of people required to continuously support every project so it can be kept alive.
If you have a centralised ops / support function then they need things to be standardised so that they can support them.
Looks good. I'd like to see some more full examples
E.g. seeing the visual editor and the outcome of the terraform code then.
I also would be interested how easy it is to customize the terraform code then without it getting overriden by your system then.
this is pretty interesting. Quick question - let's take a popular piece of software (Apache Airflow). Let's say i want to set it up on AWS EKS with all the best practices + spot instances cost reduction ... how would i do it with OpsFlow ? The problem with devops is that i dont know the "right way". I dont know whether i should use private VPC or a public VPC, etc etc. So a library of readymade "templates" would be q…
We attempted to do something similar with my last company (Atomized YC S20). We had a vision of creating an "app store" approach to infrastructure. The hardest problem we ran into wasn't build out the engine that did all the work but actually creating the templates and ensuring that everything was built with best practices in mind. Another issue we ran into was all the options that were available such as instance siz…
I'm curious about this - are u saying early stage devops teams want to build everything themselves ? I mean what im asking is a very "Gruntworks" kind of approach.
Did u not find that to be the case with Atomized ?