We've recently discovered the wonders of a CloudRun stack here at Kogan.
As a fast moving business we often need to quickly spin up new projects to demonstrate new ideas. We previously used Heroku, but for low-traffic or internal sites we didn't need the application to be running constantly: we're looking for a serverless solution!
One of the most important things you can do for your development teams' productivity is to shorten the feedback loop during development. This applies to getting feedback from customers or stakeholders to ensure you're building the right thing, as much as it does to testing the code you're writing to ensure no bugs have crept into your change set.
Today we're focusing on the Development - Test feedback loop. Developing a change and running your regression test suite to validate that change should be as fast as possible.
We've used three different systems to run our unit tests over the last few years. Beginning with a self-hosted Jenkins instance, transitioning to Travis CI, and finally arriving at Circle CI.
Last Thursday we had the React Meetup once again! A quick summary of talks and relevant links are set out below:
Three speakers covered these topics:
Ben Teese talked on how to implement component/data colocation with Apollo Client and React - Slides
Alec McGavin spoke about what really happens when a React component re-renders - Repo
Basarat Ali Syed showed us the GLS layout system and how to make development at Australia Post a breeze - Link
Interest in attending a meetup? Join us next quarter! - https://www.meetup.com/React-Melbourne/
Earlier this week Matthew Schinckel wrote a post about how he monitors Celery queue sizes with a Redis backend.
RabbitMQ (https://www.rabbitmq.com/ is also a popular backend for Celery, and it took us a long time to get good visibility into our task queues and backlogs. So we'd like to share our solution for monitoring RabbitMQ celery queues for others that might be in a similar situation.
A quick minor efficiency tip for today that'll make your life at the Django command line incrementally better.
You're using django-extensions in your project, right? If not, go and rectify that problem immediately.
The best feature™ that django-extensions provides is the shell_plus command. You know the worst thing about `shell_plus`? The name. That's a long name to type out into your shell, especially since it's snake_case, and I type the command approximately 15,000 times per day. Wouldn't it be nice to alias `shell_plus` to something like `sh`? Well, now you can!
This is part 2 of our Kubernetes hackday series. Part 1 goes over how we spent the day and what the goals and motivations are.
For part 2, we're going to delve into the architecture required for running a Django application on Kubernetes, as well as some of the tooling we used to assist us.
This post will assume some knowledge with deploying and operating a production web application. I'm not going to spend much time going over the terminology that Kubernetes uses either. What I hope to do in this post is present enough information to kickstart your own migration. Kubernetes is big - and knowing what to research now and what to put off until later is really tricky.
I'm also going to describe this deployment in terms of Amazon EKS simply because I was on the EKS team, and most of our applications are already on AWS.
