Skip to main content

Show HN: Open-source tool to deploy infrastructure in any cloud https://ift.tt/6Cal8nX

Show HN: Open-source tool to deploy infrastructure in any cloud We have been working on multy.dev, an open-source cloud agnostic API that makes it easy to deploy the same infrastructure to any cloud provider using native managed services. The motivation was the realisation that, even when using Terraform, migrating infrastructure code requires an end-to-end re-write. Even though most core resources are the same in any major cloud, developers need to learn a new provider to deploy the same infrastructure when moving providers. We are still in early days of development and currently support the core services from AWS and Azure: - Networking (virtual_network, subnet, route_table, security_group, network_interface, public_ip) - Compute (virtual_machine, managed kubernetes) - Database (managed MySQL databases) - Vault (managed secrets) - Storage (managed storage) - Abstraction of cloud differences (Azure VM public vs AWS EC2 private by default) - Deployment through Terraform We’re looking for feedback from other developers about our approach. Let us know your thoughts! GitHub: https://ift.tt/xIdgWSj https://multy.dev May 16, 2022 at 11:05PM

Comments

Popular posts from this blog

Show HN: TypeScript query builder with full type inference https://ift.tt/xZp9HOm

Show HN: TypeScript query builder with full type inference Hey HN! Colin here - a TypeScripter, open sourcer, and engineer at EdgeDB. As the creator of Zod and tRPC, I'm interested in designing tools/APIs that use type inference and generics to make life easier for devs. This query builder represents another step in that direction. We set out to build an EdgeQL query builder that can express queries of arbitrary complexity (EdgeQL has feature parity with SQL, roughly) and infer the static type of the query result. We introspect the database and generate a schema-aware client that represent any query, including ones that use built-in functions, operators, string/array/tuple indexing, aggregations, conditionals, type casting, subqueries, computed properties, etc—things most ORMs can’t represent. This post mostly discusses the API design, which I think will be interesting regardless of familiarity with EdgeQL. I’d love to see some of these ideas bleed into future generations of TypeSc...