- 7 IoT Platform vendors to watch out for - September 21, 2019
- 6 Decision making criteria that will affect IoT platform vendor selection this year - August 22, 2019
- Ten reasons to use IoT platform-based services. - July 15, 2019
“If you decide that you’re going to do only the things you know are going to work, you’re going to leave a lot of opportunity on the table.” Jeff Bezos
We have never made a secret of the fact that we favour Amazon Web Services (AWS) in the Cloud solutions we put together for our customers. We believe that it is the best & most complete cloud platform out there and we have a lot of confidence that AWS allows us to deliver better business outcomes for our clients at a rational cost. We have also written in the past about some features of AWS that excited us. It’s time to walk that AWS talk, though – let’s talk a bit about 3 cool things we have done recently with AWS.
Our own little App store experience (well almost)
The AWS Marketplace has been around for about 3 & ½ years now and has over 2200 products on it (when we last looked). There are reports that it is now a $ 1 Billion platform – that’s quite a lot of vendors selling a lot of Infrastructure code. We have been trying, in our own little way, to make a dent in the Marketplace. In our day to day work, we generally create a lot of instances. So in addition to creating these instances, we also keep them downloadable so other people with similar needs can directly use these instances. We can also sell the instances that we create for very specialised cases. We like that as a software engineering company focused on things like big data, analytics and enterprise-worthy solutions it’s fun to believe that in some strange way we are players in an App-store kind of environment. Well-ok a software engineering infrastructure app-store.
Fair & balanced
Incoming application traffic on the cloud is fickle, right? Sudden spurts, peaks and troughs are the norm. Elastic Load Balancing (ELB) helps balance the incoming traffic load across Amazon EC2 instances. We used ELB to distribute the load of a critical application on multiple instances without having to change the application code – pretty cool we think! While we are on the subject of doing many things at once how about our recent experience with AWS CodeDeploy. Now, obviously, any app contains all sorts of code – scripts, “exe”s, config files and so on. While developing the code finds its way into so many locations – GitHub repositories, S3 buckets and so on. CodeDeploy is a great way to, well, deploy the application in the face of this variety. We used Code Deploy to deploy a new release on multiple instances at the same time in a single click. How’s that for fast and easy?
The name of the route
How could we not talk about our experience with AWS Route 53 after flagging it as a feature we really like in our last blog. As we had mentioned then Route 53 is a very scalable cloud Domain Name System (DNS) web service, which offers a reliable, fast, and cost-effective way to translate names into numeric IP addresses. The big benefit is that remapping domains to different IPs can be done in a matter of minutes rather than the hours it would have taken with other services providers. In a recent case, we used AWS Route 53 for effective routing of end users to the closest AWS region for lowest latency by locating the nearest server. We can call this right-routing!
We know there is a lot of AWS still out there waiting to be explored. We’re ready and eager to dive deeper. Let’s turn to Bezos again for inspiration, “If you never want to be criticized, for goodness’ sake don’t do anything news.”