Do you need a separate database for each service?
You don’t. Creating a separate database for each service helps to enforce domain boundaries, but it’s only one approach. There’s nothing stopping you from having all your services share the same database. As long as your services behave and don’t do unexpected things to data owned by other services, you’ll be fine.
Do you need two machines for service 1?
Service 1 is a huge success. Hosting the database on two machines (master and failover) is not an option any longer. But scaling the cluster to multiple machines requires strategies such as sharding. Meanwhile, team 2 is happy with the current scale, and sees no reason to move to anything else.
When do you need a separate trust or joint trust?
Absent complex tax planning needs (as would be the case if, for example, your estate was close to or beyond the current Federal estate tax exemption amount), the choice of whether to have separate or joint Trusts depend on a few things. Most of your assets are owned jointly.
Is it OK to have multiple databases in one server?
A single server with a bunch of (logical) databases is just fine as long as you’re diligent about avoiding cross-database queries (which introduce dependencies that harm “independently deployable and scalable”). Hell, cross DB queries are impossible in some cloud database services like Azure SQL. You don’t even need to be diligent there…
Are there any questions you can ask in a 1 : 1 meeting?
But regardless of which topics you are covering, there are a few meeting questions you should always ask in a 1:1 in order to maximize the check in process. These open-ended questions set up the 1:1 with an employee-led meeting agenda rather than a manager-dictated one, which considerably ups the value of these meetings.
What to ask at the end of a 1 on 1?
The hard work of a one-on-one is sometimes just getting them to surface those concerns. By saving a few minutes at the end of your 1:1, you can give them a chance to bring up questions, concerns, or ideas that don’t fit into your more structured conversation.
When to use one to one relationship in database design?
Separate tables may allow more granular security. These considerations are irrelevant in most cases, so in most cases you should consider merging the “1 to 1” tables into a single table. See also: Why use a 1-to-1 relationship in database design?
When do I use one to one relationship?
For example, a Car can only have one current Driver, and the Driver can only drive one car at a time – so the relationship between the concepts of Car and Driver would be 1 to 1. I accept that this is contrived example to demonstrate the point. Another reason is that you want to specialize a concept in different ways.