Service meshes like istio.io start to solve a portion of this.
Almost certainly there is endless complexity but I bet you can come up with something useful. Good luck!
> people who have been working on infrastructure long enough know that there's really only a handful of useful architectures that solve 90% of problems
I totally agree with you on that point.
Also, given that architectures are created on your own cloud provider account you could easily add the missing parts.
> It's very hard because every providers have different APIs and concepts so you have to start from scratch for each.
Why not build it as a layer on top of Terraform?
Let's take an example: You have an architecture with a CI/CD. Great. You add your CodePipeline and CodeBuild ressources to your plan. Perfect.
For the CI part, you want your build to start on every commit on every non-master branch. Bad news: CodePipeline doesn't have support for multi-branch. So you will need to find a way to clone the default pipeline for each new branch.
Repeat this for all the user-friendly features (GitHub check runs, env vars management, deployment monitoring/rollback...) for the three cloud providers for all the different architectures and you start to feel the difficulty (I can testify ;)).
Users wouldn’t need to know about Terraform (unless they wanted to. It might be nice to have a way to export the Terraform code)
I use Terraform “under the hood” for this project.
What I was trying to explain is that the "hard part" is not the creation of the architecture components but the user-friendly features.
For the export feature, It's something I've been thinking about for a while.
Given that I use Terraform under the hood, I've been thinking about a feature to merge the base architecture plan with your custom plan.
So you could have a catalog of "base" architectures and another catalog of "custom" architectures that you could spin up in seconds.
What do you think about it?
Love this idea, the ease of Heroku + the flexibility of Kubernetes would be amazing.
Yes! I used Terraform because it was the tool I know best but Pulumi seems very elegant.
One of the main reason the big players dominate the Web (in the marketing space) so much is because SaaS is easier to handle (for most people) than having to deploy and maintain your infra.
if you streamline the process so that your regular SMB can build their digital infrastructure and maintain their private data clouds, it would go a long way to help us all with privacy.
A suite of open-source / on premise license one stop shop.
I think it will depend on the people that will use it.
Some architecture require more maintenance than other.
For example, the first architecture that I've created is a serverless architecture based on Docker. Under the hood it only uses managed services like Fargate, CodePipeline, CodeBuild, Aurora...
Given that you'll have a catalog of different architectures, people that don't have any experience with AWS may need to choose architectures like that.
Also, each architecture contains a detailed Readme that explain the basic operations (updating ELB HealthCheck, increasing the amount of RAM that could be used by a Fargate task and so on...).
It's a complex subject, by the way, so I am entirely open to any comments, ideas or suggestions.
Still when you succeed perhaps the next goal is to simply specify what sort of compute function, the scale and risk tolerances, and let the patterns be assembled accordingly.
Even if you can lock the API version of the SDKs, you will still need to update all the architectures with the new features and changes.
It's very challenging but I love working on it!
What do you think about it?
I didn't know Juju, I'll try it out!
I'm not very comfortable using a comment for promotional purpose so if you would like to try it out, drop me an email at [email protected], I will send you the link.
I will try to make a Show HN post in the following weeks.
I'm building a "catalog" of architectures that you could use to create a complete cloud architecture on your AWS, GCP or Azure account in less than one minute.
So, for example, you could create a docker-based architecture with CI/CD, auto-scaling, zero downtime deployment, SSL, load-balancing, high availability and MongoDB in less than one minute in your own AWS account.
It's like Terraform with the user-friendliness of Heroku.
It's very hard because every providers have different APIs and concepts so you have to start from scratch for each.
I love working on it because cloud-computing may have so much impact in some organizations like biotech startups or NGOs.