Tag Archives: fairfax

Node.js deployments at Fairfax with Code Deploy, Codeship and 12factor

This week I presented at the Node.js Wellington meetup around the tooling we have setup at Fairfax for running micro services for Node.js apps.

Essentially we have a workflow that uses Codeship for CI/CD and AWS Code Deploy for deployment. Our apps follow the principals of the Twelve-Factor App making each service simple and consistent to deploy.

This talk covers the reasons for this particular approach, the technologies used and offers a look at our stack including infrastructure and the deployment pipeline.

Whilst this talk is Node.js specific, we use the same technology for both Node.js and Java microservices and will shortly be standardising our Ruby applications on this approach as well.

AWS Cost Control at Fairfax

Earlier this month I was invited to speak at the AWS Wellington User Group around how we’ve been handling cost control at Fairfax including our use of spot pricing. I’ve now processed the video and got a recording up online for anyone interested in watching.

The video isn’t great since we took it in dim light using a cellphone and a webcam in a red lit bar, but the audio came through pretty good.

 

Back in Welly!

It’s been just over a week since we returned to Wellington, been great to get home and start making plans for long term!

Was a bit of a mission moving out of our Sydney place – whilst we went over with a total of 4 suitcases, we returned with a much larger unexpected 8 suitcases worth of stuff, which we then had to pay to lug back across the Tasman.

Too much heap space consumed by our luggage :-(

Our luggage reminds me of a Java application and heap space.

Teeny-tiny little 737.

Teeny-tiny little 737 to take us home.

Since arriving, I’ve resumed working for Fairfax as a Systems Architect, looking after both the New Zealand and the Australian systems, including SMH, TheAge, Stuff and another 700-odd sites owned by Fairfax.

It’s a bit of a step up for me, still lots of hands on engineering work, but a chance to grow my skills and take responsibility for designing and building our next generation systems on both sides of the Tasman.

It’s certainly a bit of a change talking with my AU colleagues via Google Hangout video chat rather than sitting in the pub over a beer and it’s sad to lose that closeness, but still glad I can continue working with such an excellent group of people.

I’ve also gained a bunch of friendly NZ colleagues whom I’ll be working with on various projects, seems like a pretty cool bunch.

An important NZ public holiday.

An important NZ public holiday, celebrated by the NZ office.

Meanwhile on a personal front, Lisa and I are staying in a serviced apartment for 6 months whilst we finish putting together our deposit and then go house hunting in Wellington for a place of our own!

The Reserve Bank has made it tricky with banks being limited on the number of low equity loans they offer, but we have enough to get a place in a decent price bracket with a 20% deposit. If we can get approval of a low equity loan, then our options open up even more.

It’s good to be back home again! Once we’ve settled in, will be out and about house hunting and just generally enjoying Wellington.

Wellington CBD from Mt Kaukau

Wellington CBD from Mt Kaukau

“OpsDev”

I recently did a talk at one of the regular Fairfax “Brown Bag” lunches about tools used by the operations team and how developers can use these tools to debug some of their systems and issues.

It won’t be anything mind blowing for experienced *nix users, but it will be of interest to less experienced engineers or developers who don’t venture into server land too often.

If you’re interested, my colleague and I are both featured on the YouTube video below – my block starts at 14:00, but my colleague’s talk about R at the start may also be of interest.

Additionally, Fairfax AU has also started blogging and publishing other videos and talk like this, as well as blog posts from other people around the technology business (developers, operations, managers, etc) to try and showcase a bit more about what goes on behind the scenes in our organisation.

You can follow the Fairfax Engineering blog at engineering.fairfaxmedia.com.au or on Twitter at @FairfaxEng.

Launch Paywall!

So far my time working at Fairfax Media AU has been pretty much non-stop from day one – whilst the media companies are often thought of as dull and slow moving, the reality is that companies like Fairfax are huge and include a massive range of digital properties and are not afraid to invest in new technologies where there are clear business advantages.

It’s great stuff for me, since I’m working with a really skilled group of people and being given some awesome and challenging projects to keep me occupied.

Since January I’ve been working with the development team to build up the infrastructure needed to run the servers for our new paywall initiative. It’s been a really fun experience working with a group of skilled and forwards thinking group of developers and being able to build infrastructure that is visible by millions of people and at such a key stage in the media business is a very rare opportunity.

Our new paywall has just been launched a few days ago on Sydney Morning Hearld and The Age websites for select international countries (including the US and UK)  before we roll it out world wide later in the year.

Paywalls on SMH and The Age, as seen for select international countries.

Paywalls on SMH and The Age, as seen for select international countries.

Mobile hasn't been neglected, a well polished interface has been provided there too.

Mobile hasn’t been neglected, a well polished interface has been provided there too.

Obviously paywalls are a pretty controversial topic, there’s already heaps of debate online  ranging from acceptance to outright rage for the idea of having to pay for daily news content and plenty of reflection over long term sustainability of Fairfax itself.

I won’t go into too much detail, I have somewhat mixed personal views on the idea, but generally I think Fairfax has created a pretty good trade off between making content casually available and sharable. Rather than a complete block, the paywall is porus and allows a select number of article reads a month, along with liberal social media sharing and reading of links shared by others.

Changing a business model is always hard and there will be those whom are both happy and unhappy with the change, time will tell how well it works. Thankfully my job is about designing and managing the best infrastructure to run the vision that comes down from management rather than trying to see into the future of the consumption and payment of media content, which has got to the be the hardest job around right now….

The future is digital!

Whatever your format of choice, we have your fix!

It’s been an interesting project working with a mix of technologies including both conventional and cloud based virtualisation methods and using tools such as Puppet for fast deployment and expansions of the environment, along with documenting and ensuring it’s an easy environment to support for the future engineers who operate it.

I’ve only been here 6 months and have already picked up a huge range of new skills, I’m sure that the next 6 months will be even more exciting. :-)