- Qlikview Online Training – https://www.youtube.com/watch?v=Ef_BigFXCis
- QlikView Basics – https://www.youtube.com/playlist?list=PL6_D9USWkG1DNfoH_urghaL35Ux1g3Zx1
- QlikView Developer Tutorial – https://www.youtube.com/playlist?list=PLW1uf5CQ_gSp0C_BrM1El55eaqHbkoq1i
- Free QlikView Designer Training – Beginner – https://www.youtube.com/playlist?list=PL65050F15B53C5A01
- QlikView 101 – https://www.youtube.com/playlist?list=PLW1uf5CQ_gSqKKB-aOnEd8iSwlX1XkTwx
- Qlikview complete tutorial – https://www.youtube.com/playlist?list=PL6_D9USWkG1DNfoH_urghaL35Ux1g3Zx1
Application or service orchestration is the process of integrating two or more applications and/or services together to automate a process, or synchronize data in real-time. Often, point-to-point integration may be used as the path of least resistance. However, point-to-point integration always leads to a complex tangle of application dependencies (often referred to as “spaghetti code”) that is very hard to manage, monitor and maintain. Application orchestration provides a) an approach to integration that decouples applications from each other, b) capabilities for message routing, security, transformation and reliability, and c) most importantly, a way to manage and monitor your integrations centrally.
More reading here: https://www.mulesoft.org/what-application-orchestration
Few items which I had to revisit today due to some reason.
- Application domains, which are represented by AppDomain objects, help provide isolation, unloading, and security boundaries for executing managed code.
Use application domains to isolate tasks that might bring down a process. If the state of the AppDomain that’s executing a task becomes unstable, the AppDomain can be unloaded without affecting the process. This is important when a process must run for long periods without restarting. You can also use application domains to isolate tasks that should not share data.
- If an assembly is loaded into the default application domain, it cannot be unloaded from memory while the process is running. However, if you open a second application domain to load and execute the assembly, the assembly is unloaded when that application domain is unloaded. Use this technique to minimize the working set of long-running processes that occasionally use large DLLs.
- Ref: https://msdn.microsoft.com/en-us/library/system.appdomain(v=vs.110).aspx
- WCF throttling provides some properties that you can use to limit how many instances or sessions are created at the application level
- Ref: http://wcftutorial.net/WCF-Throttling.aspx
- ConcurrencyMode.Reentrant implies that the service (or callback) processes only one message at a given time
- Ref 1: https://msdn.microsoft.com/en-us/library/aa395214(v=vs.110).aspx
- Ref 2: http://www.codeproject.com/Articles/89858/WCF-Concurrency-Single-Multiple-and-Reentrant-and