In our Dev Camp this year we chose to experiment with Event Sourcing, using EventFlow for the solution. One task was to configure it to use an Azure Cosmos database instead of a SQL Server one. There were some hurdles to overcome. This post takes you through the attempts we made and the solution we found.
Meeting the challenges of software commercialisation is not just about the code. How do you start that journey? What needs to happen along the way to ensure the best launch? And once your product has made it into the market, what needs to be in place for its continued success?
Technology and social media mean we may now be more connected than ever. At the same time, many of us feel a greater sense of loneliness than ever before. To help combat loneliness, Ami was launched in 2016 to connect lonely people with volunteers who find fulfilment in helping others. After success in Oxfordshire, Ami is now reaching out into other counties with a vision of becoming a national organisation to help combat loneliness across the UK.
Our final day saw huge progress in the application's client and server sides coming together. This was really the focus of the day with everyone working together to solve the final challenges and get the client communicating with the server.
Development progresses on all fronts in day 4, with the client and server sides moving closer together thanks to new work on the shared classes and API.
By the end of day 3 we'd managed to get the Blazor application constructing a dynamic form based on an external set of defined fields and having those fields be validated dynamically on the client-side again based on externally defined validation rules. Here's what that looks like...
In day 2 the team continued making progress in each of their areas. The EventFlow project begins to come together, shared client and server validation plans are made, and getting Event Flow working with Cosmos DB causes frustration.
In day 1 we set up our client and server-side teams; identified useful resources and frameworks for the week; and began setting up the solution and its components.
At OCC, dev camps are a way for us to experiment with new technologies, create prototype products, and bring back recommendations to the wider company regarding the new tools and techniques we've been able to evaluate.
More on Blazor – Microsoft’s experimental .NET web framework using C#/Razor and HTML that runs entirely in the browser via WebAssembly. The TAB reviews the Blazor community, Razor Components and the Blazor workshop put together by the ASP .NET team. Plus tips from the coalface on building .NET Standard applications.
The TAB reviews new features in Xamarin.Forms V4.0, including the Shell framework for quickly putting together a cross-platform application, Visual for look and feel consistencies across platforms and CarouselView for a vertical or horizontal flow of “cards”. Plus the TAB’s view of Visual Studio App Center, a front end on Azure DevOps for building and deploying apps.
The TAB discusses TLS, https and W3C’s Feature Policy.
The digital environment gives businesses the opportunity to share data and content. By delivering the right information across a range of needs, it allows individuals and groups to work smarter and upskill for the benefit of increased productivity and personal achievement.