This talk is the result of my curiosity. I like understanding things in detail and programming closures had me scratching my head for a while until I decided to investigate it, came across the great Ruby under a microscope book and voilà, everything makes sense now!
Here you can see the slides and the video from my closures talk at madrid.rb
Two facts are the motivations for this talk:
- First one is that the model cannot be changed once it is in production, well, you can, but by migrating data away to the new model using external tools such as Spark.
- The second one is that one of the most common pain points in Cassandra deployments out there is actually performance issues caused by bad data models.
So in order to provide a Cassandra overview and a ‘checklist’ to follow when data modelling here you have my talk.
And the slides are here
Just as a final comment I’d like to remark that it was my bad that, during the talk, I forgot to acknowledge DataStax for all the amazing work they’re doing and because most of the content of this talk is taken from their Academy website. So once again, thanks DataStax for all your efforts, for such an amazing Summit and for all your contributions into the Cassandra Open Source project.
This time I spoke at the Cassandra London Meetup and had the chance to share the stage with the amazing Patrick McFadin!!
My talk is about those concepts on top of which Cassandra lies that definitely make a difference in how we have to model our data. Theoretically reviewing those concepts and do some data modelling by example.
Here you have the slides
You can see the video here: https://skillsmatter.com/skillscasts/7762-scalable-data-modelling-by-example#video
This talk tries to provide with the basic but fundamental concepts required to build scalable Cassandra data models. I think that we, technical people, are impatient, and that sometimes may lead to errors, usually acceptable on the other hand, but in this case, when we’re dealing with Cassandra models, the cost in detecting why models are not scaling and having to modify them live will always be very expensive and painful. Basically, you don’t want to build and deploy models that don’t scale.
In order to get those concepts, here you have the slides and the video.
This is an opportunity ShuttleCloud people gave me after knowing I had the Cassandra Developer official certificate.
We organised it along with some DataStax guys and published it as a Madrid Cassandra Users Meetup.
I prepared and gave the workshop to about highly skilled and motivated people in an intensive day.
The experience was absolutely awesome and, following comments and ratings, people also enjoyed it.
This event was something really special for me. Lots of interesting things happened, but the most important one was being awarded one of the DataStax Cassandra MVP of the year!!
I also obtained the official O’Reilly and DataStax Cassandra developer certification
This talk is a live demo of this blog post.
I have given this talk twice, first at the Cassandra London Meetup and then for Cassandra Summit 2015.
The video is from the Meetup, and below you can see the slides.
Talk for the Christmas Get-Together Swift London Meetup
This talk is the result of this blog post where I tried to show a different approach of using Swift programming language specially focused in memory management and performance.
And happy to come back to MIMO Masters, and even better, this time with a whole module!! During this 20 hours module I lectured about CoreData, MapKit, CoreLocation, Push Notifications, Sensors and iCloud.
In this second session of the Interlat Webinars lecturing I review how the variety of devices on the market, related to brands (and underlying operating system), screen sizes and resolutions, input methods, available sensors, etc…, which is something really good for consumers, constitutes a big problem for those planning to develop an application or game.
The problem is technically called ‘fragmentation’ and appears when we realise all the effort that will be required for our product to run on as many devices as possible.
A possible solution is proposed and it is the use of technologies such as HTML5, CSS, JS and optionally a framework like jQuery Mobile to develop a mobile web application.
Also during the presentation I show a little example of a well-known videogame with a world ranking to show some of the possibilities that this set of technologies gives. Main features are:
- HTML5 Canvas based 2D game
- Usage of websockets to obtain updates to the ranking in real time.
- Usage of Google Maps and a table to display the ranking.
- Usage of jQuery Mobile to quickly build all pages and UI.
- Backend built as an API using Grape, PostgreSQL and ActiveRecord and deployed to Heroku.
You can see the source of the project in my js interlat demo app github repo.