Today I’m going to speak about another important Best practice, Tips, and Tricks that you need to know before you start to develop your Logic App solutions: Choose properly your developer tools.

In this blog post series, we will be comparing different services in AWS, GCP and Azure. We'll go into detail in each of the resources and understand the differences between providers, something you need to be aware if you are looking into switching clouds. Some examples will be given using Terraform, the Infrastructure as Code (IaC) market leader. If you want to know more about different IaC tools and how they compare, check our other blog post - Terraform vs Pulumi vs CloudFormation.

Amazon Web Services (AWS) provides three types of Elastic Compute Cloud (EC2) instances; On-Demand Instances, Reserved Instances (RIs), and Spot Instances. EC2 On-Demand instances are the default and most expensive instances. RIs and Spot instances offer discounts of up to 72% and 90% on On-Demand instances, respectively. The Reserved Instances are long-term commitments that guarantee you compute power for a year or three. Spot instances fluctuate in price and availability constantly.

Today I will talk about naming convention because I think this is so critical to implement from day one, and people tend to forget. We earlier addressed the importance of providing a good naming convention to your Logic App name and actions inside your business process. Today we will speak about the Connectors (or API Connections) naming convention.

Customers are demanding multi-cloud solutions to solve problems such as resource constraints, application mobility, and flexible architectures. VMware is positioning new products to meet this demand and provide a unified experience across infrastructures. In this latest look at the hybridized data center, VMware meets the customer where they are to demonstrate the efficacy of VMware Tanzu Kubernetes Grid in a public cloud deployment.

Even though NoSQL databases like Amazon’s own DynamoDB are very popular today, for many business use cases, there’s almost no way around using a traditional relational database. Amazon Relational Database Service (RDS), released back in October 2009, is one of Amazon’s first cloud services and can therefore be seen as a very mature service.

MEGA cloud storage launched in 2013 as a successor of a now-defunct file hosting service Megaupload. It quickly grew to a cloud storage behemoth by making itself stand out by good zero-knowledge and easy-to-use cloud storage equipped with end-to-end encryption. Like its predecessor Megaupload, MEGA is synonymous with internet culture and file storage for many users worldwide.

You’re a Cloud Strategist and your time is in demand. Your whole team is occupied meeting timelines and addressing concerns related to your business, which is why it made sense to sign up for Spot by Netapp’s Eco product in the first place. Eco’s ability to provide dedicated, cloud savings without taking your valuable time is just what the doctor ordered. In fact, Eco does such a good job, often the only time you think about it is when it is time to pay the bill.

Debugging application performance in Azure AppService is something that’s quite difficult using Azure’s built-in services (like Application Insights). Among some of the issues are visualizations, and the time it takes to be able to query data. In this post, we’ll walk through the steps to ingest HTTP Access Logs from Azure AppService into Honeycomb to provide for near real-time analysis Access Logs.