![]() ![]() It's a good idea, we just haven't got a good design for it yet (other priorities at the time )). Yep, this is something we've been tracking in for a while :). Would it not be possible to handle the issue in a peer-to-peer fashion? I just wanted to reframe the discussion in terms of that instead of SQL Server since it's been problematic :). Yeah, as I said, I definitely buy the scenario that a Windows-based On-Premise backplane makes sense. Why not just skip the middle man? The database could just be utilized so the servers could be aware of each others' existence (registering their IP address, etc.) with the rest handled P2P.īut again it's just a matter of not wanting to force my customers to deploy a dedicated Linux box on top of an already complex (all Windows) infrastructure. Would it not be possible to handle the issue in a peer-to-peer fashion? All the load-balanced servers could broadcast all SignalR messages to each other for routing to their respective connected clients? In principle that wouldn't be all that different from backplaning, which as I understand it means that each server sending an outgoing message hits common database and the database in turn notifies all the other connected servers of the message so they can also send it to their own connected clients. So it's not a matter of preferring or disliking Linux, it's that we have customers who have invested heavily in MS proprietary tech like SQL Server and Windows and want to continue exploiting those investments before moving to Linux and/or the cloud. But again it's just a matter of not wanting to force my customers to deploy a dedicated Linux box on top of an already complex (all Windows) infrastructure. Rick I don't disagree SQL server isn't necessarily the best backplane in the abstract (indeed, I've had a lot of trouble with it in SignalR in ASP.NET-not-core - and debugging on localhost with it is next to impossible - but it is functional). Requirements and not because the load is so great that a single Servers/instances of their application running because of availability In the same way, some applications may need multiple But, you know sometimes I can useĪ rock to hammer a tent post into the ground even though it’s not a InĪll of these scenarios I am just left with the argument around performanceĪnd the idea that Redis is the better or proper tool for this job. ![]() Would be at the top of the list for those designing their solutions. That supporting a heterogeneous environment for the sake of a backplane Obvious answers of just standing up Linux. Uses a container for this one specific purpose. But no one would architect a solution in a manner that *only* This policy is in place to avoid bugs being drowned out in a pile of sensible suggestions for futureĮnhancements and calls for help from people who forget to check back if they get it and so on.The use of a container just to act as a backplane is a workaround. Issues are not the place for questions, and will either be converted to a discussion or closed. Use GitHub Discussions to ask questions, bring up ideas, or other general items. Please do not open an issue on GitHub, unless you have spotted an actual bug in MassTransit. Get help live at the MassTransit Discord server. Get started by reading through the documentation. MassTransit makes it easy to create applications and services that leverage message-based, loosely-coupled asynchronous communication for higher availability, reliability, and scalability. MassTransit is a free, open-source distributed application framework for. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |