Intive Blog

The Architecting on AWS experience

Retiro neighbourhood, Buenos Aires


Thanks to the support of intive-FDV, and specially of its partners Matías Gorostegui and Francisco Ronconi, we had the opportunity to attend one of the few workshops that, for the moment, AWS is offering in Argentina. So, on May 30, we started a three-day course dictated by an expert, Hernán García, who has lots of experience with AWS. Here are some comments about the experience:

First day (64° F):

We will divide the first day in two parts:

  1. First we did a quick review of Amazon’s core services, similar to the platform’s introductory courses.
  2. In the second part, García touched a little more administrative issues, which have to be taken into account when considering our infrastructure. Specifically, there are three things to highlight:
  • Amazon’s social responsibility model, which establishes who is responsible for security, scalability and fault tolerance in each of the services. Here are the links in Spanish and English.

  • How AWS evolved through its offer: from IaaS (Infrastructure as a Service) to PaaS (Platform as a Service) and SaaS (Software as a Service). This is an interesting topic, since it changes the way we should consider our infrastructure, how we can adopt it and, in some cases, its social responsibility model.
  • The last topic was AWS Cloud Adoption Framework (AWS CAF), a framework through which organizations can migrate from an “On premise” infrastructure to one in AWS. Here is the documentation in English.

On this first day we also discussed good practices in architecture: how to detect areas of vulnerability and some basic safety techniques that Amazon can help us implement.

Second day (55° F. Yes, you read well: temperature dropped from 64° to 55° F)

Everything fails, all the time

Werner Vogels. CTO,

On the second day, the aim was to get familiar with the different services and see how they can be included in a scalable and fault tolerant design. Debate was then opened to pose different solutions or implementation possibilities. We also did several “laboratories” to put into practice what was discussed.

Third day (53° F)

On the last day we reviewed some case studies and learned good and bad practices from the design to the implementation of an infrastructure in the cloud. These are the key ideas we learned:

  • Infrastructure needs to be regarded as a software.
  • Resources must not be viewed as disposable. We have to define the service as if we were to use it for the rest of our lives. Keep in mind that if it stops working, our business would as well. We must always be able to replicate our infrastructure, thus, it shall be transparent, simple and maintainable.

Now, some considerations:

  • Breakfast is the most important thing in the day.
  • Although we didnt’ get to see the whole content, we managed to delve into discussions about practical cases and personal experiences. That’s really fruitful.
  • We need more AWS official workshops to achieve better results.
  • Infrastructure is volatile, so we need to think of it as such. Consider the infrastructure as a box of chocolates.
  • Three days didn’t seem enough.
  • It’s worth training your staff. Thanks intive-FDV!

Rodolfo Cordero

Rodolfo Cordero has been a developer at intive since June 2016. He is a graduate in Software Development from the Universidad Latina de Costa Rica, his country of origin. A regular reader and music lover, he took courses in cocktailing and to become a barista, skills that delight the staff of intive in the after parties organized by the company.

Add comment