Hi, Dne 31. 01. 19 v 20:54 blackfalconsoftw...@outlook.com [firebird-support] napsal(a): > II... > My understanding of the Firebird Butler project could be two-fold... > A specification for best practices for developing distributed systems using > the Firebird Database Engine A set of enterprise tools to implement such > systems (ie: an equivalent to Windows Communication Foundtaion: hence the > attribution to ZeroMQ Just my thoughts...
Well, one could call a Framework as "best practices" enforcement tool :-) Although Butler SDK is not a typical framework. If you would draw a parallel to WWW, then Butler specifications are like HTTP and related specifications, Butler SDK's are frameworks and libraries to create services that use these specifications (like there are ones for www technologies), and Butler itself (the product(s)) are applications assembled from these services like web servers, browsers etc. Because it's a LEGO system, it's not a single application, but rather a "distribution" (in Linux sense) or a "delivery platform" (like Steam). Both approaches are possible. Over time, we would like get to the Steam-like deployment platform for Butler services provided by Firebird Project as preferred over purpose-tailored distributions, but it's an open ecosystem, so anyone could do what they want regardless to our preferences. The Firebird Project will create services needed to manage Firebird server deployments (as first goal for Butler product, see description of our plan), but we will not stop there (for example we plan to recreate our internal QA test system as Butler app [set of QA services]). Others could use Butler specifications and SDK's to integrate their applications with services provided by us or other entities as they see fit, or could use Butler applications provided by us and others "as is". Or create their own services/applications for whatever purpose, even not related to Firebird in any way. Does it make more sense now? best regards Pavel Cisar IBPhoenix
