microservice data consistency, eventual versus strong? should we go with eventual consistency or strong consistency

hey all, ive been thinkin a lot abt data consistency across microservices lately. were movin toward more domain-driven design, and with that comes the challenge of maintainin consistent data when its spread across different services. are u generally aimin for strong consistency or leanin into eventual consistency with mechs like event sourcin or sagas? whats the trade-offs uve found most impactful in ur architectures