Automation should be at the heart of every software company. If have to configure something manually: script it. Save the script. Use the script. Automate. Anything. Automation. First. Period.
Anneke Keller (CTO), Koen Roumen (Head of Platfom) and me did a talk on DevOpsDays Eindhoven 2022: A true story on how we learned how to handle the immense web traffic caused by a successful influencer campaign. How we built a platform with Karpenter and Keda for rapid and massive auto-scaling and the effects this had on our platform.
At Wehkamp we ❤️ Slack! Seriously, in order to improve our efficiency, we’ve connected many of our applications, alerts and dashboards to Slack channels. But, as with all things, there is a right way and a wrong way of integrating a webhook at enterprise level.
Let’s explore how easy it is to create an application.
Chris Vahl (Cloud Engineer) and me did a talk on Full Stack Live #2 (Orange Talent: At Wehkamp we did a very successful influencer campaign, but it didn’t go well for our website. In this session we discuss what happened and how we mitigated our problems. We also show how we want to move forward using Kubernetes, Karpenter and Keda, to create a platform that scales better. This session is in Dutch.
Let’s use a small snippet to convert any article to Markdown. This might come in handy if you want to repost your articles to blogs that support Markdown like DEV.
This week we had to exfil some data out of a bucket with 5M+ of keys. After doing some calculations and testing with a Bash script that used AWS cli, we decided to go a more performant route and use s3p. They claim to be 5-50 times faster than AWS cli 😊.
Positional arguments like $1 and $2 are hard to read. This Bash pattern maps named options to explicitly allowed variables and validates the required input.
At Wehkamp, we use Google Analytics extensively to measure how many users are active. It is hard to correlate active users with your other statistics that “live” in Prometheus. In this blog I’ll show how you can use the Google Real Time API to produce statistics for active users, page views and screen views.
At Wehkamp we use Redis a lot. It is fast, available and implemented as a managed AWS service called ElastiCache. Sometimes we need to extract data from Redis, and usually I use the redis-cli to interact from the command-line. But what if you need to get the values of 400k+ keys? What would you do? Is there an effective way to query multiple key/values from Redis?
This week I needed to query an ElastiCache instance on AWS – which is Amazons version of Redis. I could not find a decent free client to query this remote dictionary, so I ended up using redis-cli on Ubuntu. Turns out: Redis is a wonderful and powerful system to work with.
Today I had some data coming into our event driven landscape, so I needed to know when my data was processed. As it constituted the processing of 400.000+ records (and I had more things to do), I needed a small script that kept an eye on my JSON API endpoint to see if the values are changed.
