diff --git a/Asynchronous-messaging.md b/Asynchronous-messaging.md index 2d4bb9d..67affac 100644 --- a/Asynchronous-messaging.md +++ b/Asynchronous-messaging.md @@ -1 +1,33 @@ -Placeholder to reference Asynchronous messaging solutions. +**IMPORTANT NOTICE** + +The [asynchronous messaging implementations used in eShopOnContainers](https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/src/BuildingBlocks/EventBus) to handle integration events, are simplified versions that have value in as much as they're useful for grasping the main concepts and scenarios. + +**DON'T USE THEM IN PRODUCTION**. + +For production-grade messaging solutions you can take a look at the following resources: + +- **Azure Service Bus** \ + + +- **NServiceBus** \ + + +- **MassTransit** \ + + +- **EasyNetQ** \ + + +You can also evaluate other messaging solutions such as: + +- **Brighter** \ + + +- **CAP** \ + + +You can also explore some asynchronous messaging implementations for eShopOnContainers in the following GitHub repos: + +- Using [**NServiceBus**](https://particular.net/nservicebus): + +- Using [**CAP**](http://cap.dotnetcore.xyz/): diff --git a/Explore-the-application.md b/Explore-the-application.md index 457c4df..febd903 100644 --- a/Explore-the-application.md +++ b/Explore-the-application.md @@ -50,12 +50,17 @@ Then, after providing the size (i.e. 10) and the current page (i.e. 1) for the d ## Xamarin.Forms mobile apps for Android, iOS and Windows +Xamarin Mobile App supports the most common mobile OS platforms (iOS, Android and Windows/UWP). In this case, the consumption of the microservices is done from C# but running on the client devices, so out of the Docker Host internal network (Like from your network or even the Internet). + You can deploy the Xamarin app to real iOS, Android or Windows devices. + You can also test it on an Android Emulator based on Hyper-V like the Visual Studio Android Emulator (Do NOT install the Google's Android emulator or it will break Docker and Hyper-V, as mentioned in the [Windows setup page](Windows-setup)). +![](images/Explore-the-application/xamarin-mobile-app.png) + By default, the Xamarin app shows fake data from mock-services. In order to really access the microservices/containers in Docker from the mobile app, you need to: -- Disable mock-services in the Xamarin app by setting the UseMockServices = false in the App.xaml.cs and specify the host IP in BaseEndpoint = "http://10.106.144.28" at the GlobalSettings.cs. Both files in the Xamarin.Forms project (PCL). +- Disable mock-services in the Xamarin app by setting the **UseMockServices = false** in the `App.xaml.cs` and specify the host IP in `BaseEndpoint = http://` at the `GlobalSettings.cs`. Both files in the Xamarin.Forms project (PCL). - Another alternative is to change that IP through the app UI, by modifying the IP address in the Settings page of the App as shown in the screenshot below. - In addition, you need to make sure that the used TCP ports of the services are open in the local firewall. diff --git a/Release-notes.md b/Release-notes.md index 9be189a..d88dbb0 100644 --- a/Release-notes.md +++ b/Release-notes.md @@ -41,6 +41,7 @@ The latest [3.0.0 release](https://github.com/dotnet-architecture/eShopOnContain - Sidecar implementation with Envoy/Linkerd - Improved API Gateway and resilience - gRPC for microservice-to-microservice communications + - Dev Spaces support (only for containers that don't use gRPC) #### New folder structure diff --git a/images/Explore-the-application/xamarin-mobile-app.png b/images/Explore-the-application/xamarin-mobile-app.png new file mode 100644 index 0000000..7b63a48 Binary files /dev/null and b/images/Explore-the-application/xamarin-mobile-app.png differ