enechain Corporation
Company
Key | Value |
---|---|
Company | enechain Corporation |
Employee | 160+ |
Founded | 2019 |
Web Site | https://enechain.co.jp/ |
Description | enechain is Japan’s largest energy marketplace operator, collaborating with huge power companies. |
Location | Tokyo, Japan |
Team (Software Engineer - Platform)
Key | Value |
---|---|
Title | Software Engineer (Platform) |
Mission | My mission was to develop internal APIs and tools that improved developer productivity across the organization. |
Term | 2024-04 - 2024-10 |
Team Size | 3 |
Type | Freelance |
Team (Site Reliability Engineer)
Key | Value |
---|---|
Title | Site Reliability Engineer |
Mission | My mission was to improve system reliability for 20 microservices by developing and enhancing observability features. |
Term | 2023-11 - 2024-04 |
Team Size | 5 |
Type | Freelance |
Projects
Key | Value |
---|---|
Summary | EN1. I developed a generator tool for Kubernetes manifests and Terraform configurations for microservices, which reduced initial deployment time by 90%. |
Situation |
|
Task | My mission was to automate creating these configurations to improve development efficiency and reduce errors. |
Action |
|
Result | As a result, the tool made deploying new microservices much smoother. Initial setup and deployment time decreased by 90%. |
Challenge | A key challenge was version management. If developers used an old version of the CLI tool, they could create wrong or outdated templates. |
Solution | To solve this, I set up the CLI client to only trigger a CI pipeline. The main generation logic stayed in the CI environment. This made sure it was always up-to-date. |
Learning | I learned that standardization is the key to improving productivity, as it prevents common errors and ensures consistency. |
Skill | Tool Development / Collaboration / Ownership |
Key | Value |
---|---|
Summary | EN2. I set up a local development environment by deploying Telepresence to the Kubernetes cluster, which accelerated local development for highly dependent microservices. |
Situation |
|
Task | My mission was to let developers work efficiently on individual microservices locally without needing to run all other dependent services. |
Action |
|
Result | As a result, this system accelerated local development cycles. Overall, the speed of microservice development increased. |
Challenge | A key challenge was our strong security standards for Kubernetes clusters. The official Telepresence Helm charts didn't support these security configurations by default. |
Solution | To solve this:
|
Learning | I learned that the key to improving developer productivity in a business setting is to find the right balance while maintaining strict security standards. |
Skill | Kubernetes / Security / Balancing / Difficult Decision / Teamwork / Collaboration |
Technology
Value | Tag |
---|---|
Argo Workflows | Backend |
Go | Backend |
GraphQL | Backend |
gRPC | Backend |
Node.js | Backend |
PostgreSQL | Backend |
Redis | Backend |
TypeScript | Backend, Frontend |
ArgoCD | Infrastructure |
AWS | Infrastructure |
Google Cloud | Infrastructure |
Kubernetes | Infrastructure |
Terraform | Infrastructure |
BigQuery | Data Platform |
Kubeflow | Data Platform |
Datadog | Monitoring |
Prometheus | Monitoring |
React | Frontend |