This week I introduced Google Cloud Platform to a select group of individuals. I wanted to show them the “Operational Simplicity” of the platform vis-a-vis the other IaaS providers.
I read an excellent book on Google Compute Engine (GCE) recently, which is a great tutorial on the various services available in GCE. I strongly recommend the book. One of the examples there was of a Load Balancer in Action, where the authors demonstrated spinning up a couple of Virtual Instances, setting them up with a Apache Web Server and then bringing them down and up again to demonstrate how the Load Balancer works. I thought that would be a great demo to show and full marks to the authors, I just went through the script but I did a little bit more, which I want to share with everyone.
I recently had the opportunity to introduce first-time Cloud Computing students to a first-hand experience of what it means to work with a IaaS Provider.
The goals of the hands-on session was the following:
- Provision a Virtual Machine for each of the students.
- Allow the students to SSH into their respective VMs.
- Deploy one of the following:
- Apache Web Server with a web site
- Node.js application
- No installing any tools/runtimes on the participant machines. A browser is all they have.
In an earlier blog post, I had presented the view that one of the best ways to learn Docker in my opinion is to move to the cloud and not do this stuff on your local machine. Chief reasons among them being bandwidth issues that could completely spoil your experience around Docker.
Docker is all the rage and there are valid reasons for it. Every software developer needs to understand this fundamental shift that is happening when it comes to packaging, delivering and running applications as containers. It would definitely pay to start learning this technology. There are enough resources on the Net to do that today and hopefully I will come around with some tutorials that can help demonstrate how useful Docker can be to individual developers like you and me.
The focus of this blog post is different though. It is about which platform/OS should I start learning Docker on. And then I would like to make some points from the perspective of countries/individuals where it is not easy to get high speed internet access all the time for several reasons. My focus is going to be for students who want to get started and have limited resources.
Over the last couple of weeks I have covered the news around several features that have been released on Google Cloud Platform (GCP). I write these articles on ProgrammableWeb. Here are the list of articles:
The articles demonstrate the recent spate of feature releases on GCP. They are targeted squarely towards the developers/organizations and helping them get more productive, write secure apps and finally get a shot at a messaging service in GCP. Not to speak of Google Cloud Storage Nearline that changes the game when it comes to cold data storage.
Android Studio has solid support for working with Google Cloud Endpoints. I have written a series of tutorials on working with Gradle, Android Studio, Cloud Modules over here. One of the episodes in that chapter was around generating the Persistence Layer in your Endpoints using Objectify.
At the time of that writing, the skeleton wrapper code that was generated for Endpoint when you provide it your Entity class was minimal. It was of not much use and you had to pretty much write the Objectify code for list, get, add, update and remove methods.
Since then the support has been upped by several notches and I should have written about this earlier but got around to it only now. The bottom line is that if you have an Objectify annotated Entity code, Android Studio is currently doing a great job of generating the Endpoints class with all the persistence goodness of Objectify generated for you. This can greatly help to reduce the time to generate working persistence code for your Mobile backend.
I recently wrote a blog post on writing a temperature logger using Arduino + Python + Orchestrate.io database service. Several readers wrote back to use an alternative database if possible. I have decided to rewire that tutorial but this time with Firebase database. This would also act as a introductory tutorial on Firebase.