Through a local friend who's company that is the leading Connected Systems content provider for Microsoft, we are partnering with them and Microsoft to engage on projects to develop solutions built using Windows Server AppFabric, Workflow Foundation and Windows Communication Foundation. We will be co-sponsoring software development projects that meet business and technical criteria elaborated below. If you are interested, feel free to email me (chris@architectingconnectedsystems.com) or DM me on Twitter (@givenscj).
Qualifying “Business Criteria”
· Signed PR Release Form
· Premier Support
· MCS and/or Partner Engaged
· Current Release of Product
Qualifying “Technical Criteria”
· Hosting: Throughput: WF/WCF > 100 tx/second
· Integrated Platform: AppFabric, WIF, SharePoint Server or BizTalk integrated solution
· Management: PowerShell API | SCOM
· Monitoring: >100M tracked events (15 events/instance @ 50 calls/sec, 8-hour day, over 5 days)
· Persistence: >50K persisted active instances | >10 persist points/workflow
· Tier1/Mission Critical: Cache HA feature and WF/WCF mission critical application
· Projects that have case study potential due to the client’s name.
o Usually for companies that have strong name recommendation or a large in size, but exceptions often occur and smaller companies can still participate, just at a smaller dollar amount.
o Example: a Fortune 1000 corporation embarking on a new project using Workflow Services or WCF Services hosted on Windows Server AppFabric.
· Projects that are technically interesting.
o The project may be developing items which are of interest to the broader Microsoft ISV community, and the work product can be generalized (e.g., removing the client’s IP) for sharing. For example, getting AppFabric to use Oracle for persistence and monitoring.
o The project may well provide lots of feedback on less used aspects of AppFabric, WF and WCF that can be a source of bug reports to MS and guidance to the ISV community. For example, building a Workflow Services design environment completely external to Visual Studio.
o &n
bsp; The project itself does not have to be large in scope- it may be just a proof of concept effort. In effect, Microsoft will “seed” the development’s success.