Colorkrew Blog

Tired of setting up CodeBuild just to push Docker images or run vulnerability scans?

With AWS CodePipeline’s new ECRBuildAndPublish and InspectorScan actions, you can now build, publish, and secure your images directly within your pipeline—no extra setup needed. Curious how it works? Let’s dive in!

Motivation

26 November, 2024 – Just ahead of re:Invent 2024, AWS released an exciting update introducing ECRBuildAndPublish and InspectorScan actions. This update simplifies building and publishing Docker images, letting your pipeline handle it seamlessly.

This blog is little unusual than the usual “show-what-you-built” blogs which we usually see for cloud services and new features on the internet.

In this blog I will sharing my first impressions, good and bad points about the new update on Cloudwatch: Observability Solutions !!!

AWS CloudWatch Observability Solutions aim to simplify monitoring setup with pre-configured tools for AWS services and workloads. But is it really that straightforward? Let’s explore the reality!

In Japan, many companies hire new graduates in large groups every April. However, Colorkrew hires throughout the year. This October, we welcomed two talented new graduates to our team.

One joined as an engineer, and the other joined the business team, working in product operations. One graduated from a university overseas, and the other graduated from a university in Japan.

We all love serverless especially when it comes to AWS LAMBDA functions.

There are good reasons to do so for event-driven, decoupling, automation and many other reasons that time aws lambda was released.

But there can be situations when our dear friend LAMBDA can turn in to a foe and cost us money, downtime and those times are unintentional recursive Loops.
In this blog we will talk about a very simple feature yet a powerful one, recursive loop detection between aws lambda and s3 bucket.

Until Now, if you wanted to run AWS CLI commands, third-party CLI commands, or simply invoke an API, you had to create a CodeBuild project, configure the project with the appropriate commands, and add a CodeBuild action to your pipeline to run the project.

Clearly Users had to deal with 2 components CodePipeline and CodeBuild and of course learn the internals for both in order to use the.

This is Lucky Li, I joined Colorkrew as a new graduate from April.

My position is Engineer, belonging to the Colorkrew Biz product team. My work is developing Colorkrew Biz which is a well-know Saas in Japan.

Before I joined, I conducted academic research and pursued a PhD at the National University.

What data structure would you use to determine whether an entity is in a given dataset with speed? Many would answer “Hashtable” without hesitation. Hashtable performs well when accessing an entity among a group of entities: the average time complexity of its read operations is constant. Nevertheless, using Hashtables can be rather costly when dealing with large datasets. Hashtables need to keep track of every entity in the dataset, resulting in a linear space complexity.

Moving to Japan

The first time I came to Japan, I was a tourist. I spent 1 week here during my final year of college.

The second time I came to Japan, I was moving here, starting a new job and a different way of life.

In the 7 years between, I worked as a software engineer across many American cities and companies.

Time flies and we have entered 2024. And I had joined Colorkrew for 3 months. I am filled with excitement for what the future holds.

My last job was as the director of a multinational e-commerce company. Although the company has gone public, it still maintains the atmosphere of a start-up company.That is also the reason I decided to join Colorkrew.

As the new year begins, I reflect on the last 8 months since my move to Japan; In that time, I have gotten to know my new colleagues better through a myriad of social activities held in Colorkrew’s office in the past year.

One of the most memorable events that I participated in was the Welcome Party, where we welcomed new members to the team through a host of food, drinks and fun activities. One Colorkrewer brought a portable Takoyaki grill and started a makeshift Takoyaki party; Another built a Japanese and English word guessing game, and we enjoyed a few rounds of friendly competition and laughter over the games. Through the event, I was able to catch my first real glimpse of Colorkrew’s informal work culture, where we are able to speak to anyone in the company regardless of their title or designation.

For many software engineers, endpoints for retrieving a list of entities are probably their favorite to implement–all they need to do is build an SQL statement that grabs all the available items, along with some other minor tasks. It’s all fun and games until the number of entities in the database becomes a bottleneck, where each GET request returns tens of thousands of items. You start to see server-side logs bombarded with error messages highlighted in red. Your dear users, previously satisfied with your application, begin to complain about the increasingly lackluster performance. Your product manager is on the brink of losing it and taking out their frustration on you. What?! You say you want to prevent all this from happening? Pagination is what you need! It can drastically improve your endpoints’ performance and save your servers from overload. Today, I will define pagination and introduce the most common pagination techniques.

Recently, I joined a new project at Colorkrew that uses Golang as its backend language. Almost everyone on the team, including myself, had no experience with Golang, so we had to start from zero. Learning Golang has been a rewarding experience so far. After all, it is one of the most in demand programming languages now. However, writing code in Golang is not all sunshine and roses. Unopinionated as I am, I still have my fair share of complaints, the biggest being the recommended way of error handling in Golang.

Many frontend engineers probably have experienced the head-scratching moment when their React components become so gigantic that they keep losing their train of thought when navigating through their frontend code. To salvage readability, one of the most common practices is to split up the humongous React components into smaller pieces. Traditionally, they would do this by chopping up the JSX elements. This method can effectively improve the readability of React components whose sole responsibility is to display data. However, on top of displaying data, some React components are also responsible for retrieving data from the backend. The more effective way to make such React components readable is to separate them into Containers and Views. In this article, I will demonstrate how to divide a React component into a Container and a View based on the principle of separation of concerns.

Throughout my life I been captivated by many forms of fictional media. But in my career as a visual designer in the technical field, nothing offers greater inspiration than science fiction.

To explain why it’s so important to me personally, it helps to establish a few things about my background…