Included with every Microsoft Azure Service Fabric Actor and Service is a nice little settings.xml file that you may have considered using to store configuration values for your actors and services. Unfortunately, the documentation on how this file can be used is a bit lacking, so after hitting my head against it for a couple days, I figured out how it can be used so you don’t have to!
In the age of Big Data, companies are pushing to collect and analyze as many data sources as possible so they can enrich the customer experience and drive sales. One way to gather rich data is by integrating Customer Relationship Management (CRM) tools with business intelligence (BI) platforms. CRM provides companies with customer-centric data that directly relates to satisfaction, engagement, and experience metrics – while BI can add an additional layer to present this data in a meaningful and actionable way.
If you are reading this post then, like many others I meet, you are potentially looking at PLM (Product Lifecycle Management) solutions and may be confused with which direction or vendor...
You know when you get that feeling that you have experienced the same situation in the past. You can’t put your finger on it but you know you have been here before. Well that is how I feel when I think about the emerging world of containers and microservices. I actually think this feeling of déjà vu is a good thing — containers and microservices are beginning to see the glimmers of the commercialization of a service oriented approach to computing.