---
title: "Discussion on \"Overgrown Tenant class decomposition\" | Hashnode"
description: "Discussion on \"Overgrown Tenant class decomposition\". If you have been working on a multi-tenant application for a long time, there is a high chance that your Tenant model has grown to an enormous size.\nYou probably started with id, name, and subdomain columns.\nLater there were things that had to be con..."
url: "https://hashnode.com/posts/overgrown-tenant-class-decomposition/61dd6bed18ce964d90d0cc19"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Overgrown Tenant class decomposition](https://rubywizards.com/overgrown-tenant-class-decomposition?utm_source=hashnode&utm_medium=feed)

If you have been working on a multi-tenant application for a long time, there is a high chance that your Tenant model has grown to an enormous size. You probably started with id, name, and subdomain columns. Later there were things that had to be con...

Jan 11, 2022 · 2 min read · rubywizards.com  
Read the article

-   [#ruby](https://hashnode.com/tag/ruby)
-   [#ruby-on-rails](https://hashnode.com/tag/ruby-on-rails)

## Written by

[Piotr Jurewicz](https://hashnode.com/@pjurewicz)

@pjurewicz · Łódź, Poland

  
[View profile](https://hashnode.com/@pjurewicz)

ruby on rails developer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.