Lately, the public cloud services market has created one of the biggest disruptions in the tech market. In fact, as per Forrester Data, public cloud services forecasted a 22% CAGR in the public cloud market from 2016 to 2020. In addition, Gartner projected the Infrastructure as a Service (IaaS) to grow 35.9% by end of 2018 to reach $40.8 billion. Looking at the potential of the cloud market and the benefits associated, right now would be the apt time to migrate from monolithic to the cloud.

First, let me say that I know AWS doesn’t promise anything about network performance as it relates to packets. At best, they leave it as a multivariate calculus problem for the reader — inclusive of CPU performance, code optimization, MTU, and current network congestion under the VLANs. But still, I was curious to see if there was any correlation to Amazon’s published “Network Performance” and the actual packets per second metric I tested.

Remember the customer who reported a hard-coded packet per second (PPS) limit in AWS? His use case was a reverse-proxy server to a very active database cluster, complete with heartbeats, keep-alive connections, and a heavy load of queries and traffic. When the network throughput was sustained for an hour or so, the throughput would drop despite increasing demand.

Victory Square Technologies and Plug and Play Ventures invested in the Vancouver and California-based startup with participation from key angels in the enterprise and infrastructure space.

Have you been bitten by unexpected costs in the cloud? Whether you are all in with serverless, cloud-native services, on demand and reserved instances, or you build systems and applications with all those things, it is very likely you have had a bad experience with unexpected costs. Why is that? Let me ask you, what is your DevOps tool for observing cost?

A customer of ours reported a limit on number of packets in Amazon’s EC2 instances. According to the report, it didn’t happen on all instance types, and didn’t happen all the time. Also, it was unrelated entirely to bandwidth or MTU. According to the report, packet transmission rates were limited the same as CPU on t2/t3 instances — each instance earns credits which, when exhausted, cause throttling.

Cloud is a big part of Atlassian’s future, and we’re more focused than ever on delivering a great Server to Cloud migration experience. When developing software, there is no better way to test than doing it yourself. So that’s what we did. In an effort to learn more, understand pain points, and make a better experience for our customers, we migrated our whole company’s Jira and Confluence instances to the Atlassian Cloud.