Personality protocol for a chatbots platform. How to share personalities among different layers and components. At the end of the day is customization and parametrization of LLM instructions, however an interesting topic to explore.
I agree with many points, however, it depends on the abstraction that you need and the abstraction depends on the architecture you are adopting.
For example, if you are doing DDD and your repository implementation is about SQL, adding another layer of abstraction is not worth. But if your design is less sophisticated, or you are in an early stage of the project, you may find appealing to use that abstraction.
I suspect many of us can tell more about IT horror-stories in the banking industry. There is simply no way to make agile software in such a gigantic and obsolete environment. And yes... doesn't matter if you do micro-front architecture now... it is still obsolete.
Primarily for storage at this point.
I run some CI/CD on my local network, and the artefacts produced by the building process are massive. Paying for that is not worth it.