[Blog] Why we decided to keep Juggler as our ORM

[bajtos]

Write a blog post about the discussion we had in #537 and the decision we reached.

• Explain why this discussion started in the first place
• Summarize the arguments for keeping juggler and for switching to a different ORM
• Explain why we decided to keep Juggler
• Tell readers about the next steps we are planning

[shimks]

This should be given a priority (dp3 or non-dp3). I'd rather have this be part of DP3, but we may already be overloaded enough so I'm also ok with it being non-DP3 as well.

[dhmlau]

With "juggler-next" as the top of our backlog, I'd like this to mark as tob to explain our approach on "juggler-next".

[richardpringle]

@bajtos, any updates on a blog post date? (no pressure 😉)

[stale]

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

[stale]

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

[stale]

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.