The latest articles on DEV Community by jcoelho (@jcoelhoo). https://dev.to/jcoelhoo https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F865312%2Fd7d3dec5-45b2-49ff-873c-3f23ec8db99e.jpeg https://dev.to/jcoelhoo en jcoelho Tue, 31 May 2022 10:07:46 +0000 https://dev.to/jcoelhoo/the-challenges-of-building-multi-cloud-3f3g https://dev.to/jcoelhoo/the-challenges-of-building-multi-cloud-3f3g <p><a href="https://docs.multy.dev/blog/challenges-of-building-multi-cloud">https://docs.multy.dev/blog/challenges-of-building-multi-cloud</a></p> <p>Multi cloud has long been a contentious topic when you talk about cloud infrastructure. Infrastructure as code tools such as Terraform and Pulumi have made deploying to any cloud much easier - you can now use a single interface to deploy infrastructure to virtually any cloud environment. However, the effort of creating infrastructure for each cloud provider still requires significant expertise and time to get right, leading many to see it as a effort not worth taking.</p> <p>In this blog post, we'll go over the potential consequences of running on a single cloud, the current options companies have when deploying cloud infrastructure and the common pitfalls.</p> cloud aws azure cloudnative jcoelho Fri, 20 May 2022 11:42:02 +0000 https://dev.to/jcoelhoo/were-building-an-open-source-tool-to-deploy-infrastructure-to-any-cloud-1m50 https://dev.to/jcoelhoo/were-building-an-open-source-tool-to-deploy-infrastructure-to-any-cloud-1m50 <p>Me and a few friends have been working on <a href="https://multy.dev">multy.dev</a>, an open-source cloud agnostic API that makes it easy to deploy the same infrastructure to any cloud provider using native managed services.</p> <p>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.</p> <p>We are still in early days of development and currently support core services from AWS and Azure:</p> <ul> <li>Networking (virtual_network, subnet, route_table, security_group, network_interface, public_ip)</li> <li>Compute (virtual_machine, managed kubernetes)</li> <li>Database (managed MySQL databases)</li> <li>Vault (managed secrets)</li> <li>Storage (managed storage) Abstraction cloud differences (Azure VM public vs AWS EC2 private by default)</li> <li>Deployment through Terraform</li> </ul> <p>We’re looking for feedback from other developers about our approach. Let us know your thoughts!</p> <p>GitHub: <a href="https://github.com/multycloud/multy">https://github.com/multycloud/multy</a></p> go opensource cloud devops