If you have a database schema table with data that multiple applications need access to...
1. Do you create a single Record Type which multiple application use/share? This in my opinion tightly couples your applications.
2. Do you create separate Record Types per application so they can evolve separately? This in my opinion allows each application to evolve it's Record Type independently, and the only tight coupling is the shared database table structure.
What are your thoughts and recommendations on the two approaches?
Discussion posts and replies are publicly visible
Hey! If you're all about data reading without dealing with Record Actions, consider opting for a domain-based model. In simple terms, let one primary domain or app be the data 'owner' and share it through WebAPIs for other apps to read. This keeps everything neatly separated. The domain manages the data flow, and each app can grow independently without interfering with the others. Just a quick note, having a robust versioning strategy is key to managing changes in the services you expose. By the way, have you checked out applooter.com for more insights on optimizing your app strategies?