Skip to content

Conversation

@yukimori
Copy link

This Pull Request adds a new blog post titled “How LY Corporation Utilizes MLflow”.

The article introduces how LY Corporation provides a managed MLflow service on our internal AI platform,
including:

  • Our architecture for running MLflow instances on Kubernetes
  • Service-to-service authentication and authorization using OAuth 2.0 with Athenz
  • Usage insights and trends based on internal MLflow activity

The goal of this post is to share our experience integrating MLflow at scale within a large organization,
and to offer practical insights for other teams operating MLflow in production environments.

Please let me know if you would like any clarification or adjustments.

Although this post has already received an initial review through Shiga-san, I have made the following updates (apologies for the changes after the review):

  • Based on advice from the Athenz team, I revised the explanation of the service-to-service authentication and authorization mechanism to use terminology aligned with the standard OAuth 2.0 specification.
  • Updated the graph to show the average based on calendar days instead of business days.

@B-Step62 B-Step62 self-requested a review November 26, 2025 07:39
@github-actions
Copy link

github-actions bot commented Dec 2, 2025

🚀 Netlify Preview Deployed!

Preview URL: https://pr-408--test-mlflow-website.netlify.app

Details

PR: #408
Build Action: https://github.com/mlflow/mlflow-website/actions/runs/19664149326
Deploy Action: https://github.com/mlflow/mlflow-website/actions/runs/19850245858

This preview will be updated automatically on new commits.

Copy link
Collaborator

@B-Step62 B-Step62 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you so much for the great blog with tons of learnings, @yukimori-san! Left comments but mostly minor formatting and styles.

---

# How LY Corporation Uses MLflow: An Overview
Hello, I’m Motoki Yuhara from [LY Corporation](https://www.lycorp.co.jp/en/company/overview/), and I’m responsible for building and operating the Managed MLflow service for our internal AI platform.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can skip the self-introduction since the author name and position will be shown at the top of the page. (but it's totally fine to keep the company link).

Screenshot 2025-12-02 at 15 47 19

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed the self-introduction as follows.

I’m responsible for building and operating the Managed MLflow service for the internal AI platform at LY Corporation.


With these mechanisms in place, we have built a managed MLflow environment that integrates seamlessly with our Kubernetes-based training platform while ensuring secure and reliable service-to-service usage.

# MLflow Usage at LY Corporation
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yukimori I wonder we can show this number first before auth sections to let readers get the scale of the platform.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added numerical information at the end of the section “How LY Corporation Uses MLflow: An Overview.”

This platform provides end-to-end MLOPs capabilities from model development to deployment and operation. MLflow is a core component of the platform for managing model training, evaluation, and model lifecycle.
Currently, MLflow is used by approximately 40 services, and it handles more than 600,000 access requests per day on average.

yukimori and others added 22 commits December 19, 2025 14:47
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
@yukimori
Copy link
Author

@B-Step62

Thank you for your comment.

I have merged your suggestions and made revisions in accordance with the comments. I would appreciate it if you could review it again.

@yukimori yukimori requested a review from B-Step62 December 19, 2025 08:05
@yukimori
Copy link
Author

@B-Step62

Just a gentle reminder on this PR.
When you have a moment, I’d really appreciate your review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants