I would like to know what is the real benefit of using azure web job sdk in web job.
I have some business logic to be executed without any interaction with storage,service bus.It is interacting with Sharepoint and Azure Sql. I have checked question here -Basic of Azure WebJobs SDK
which says JobHostConfiguration is not required for the job.
In which cases the JobHostConfiguration and webjobs sdk will be required and why we should use that?
WebJobs 3.x targets .NET Standard 2.0. This means you can use it from a .NET Framework application or a .NET Core 2.x application, the choice is up to you. If you want to make a .NET Framework application that uses WebJobs, then follow the same guide but with a .NET Framework console app as the starting point (instead of .NET Core).
If you're planning on deploying this webjob to a webapp that is running a .NET Framework application, I think it makes sense to use .NET framework for the webjob too.
You can refer here for more details on Webjobs Host.
Webjob SDK Version 2.x
The JobHostConfiguration class has a UseDevelopmentSettings method that enables development mode. The following example shows how to use development settings. To make config.IsDevelopment return true when it runs locally, set a local environment variable named AzureWebJobsEnv with the value Development.
Please let me know if this helps.
I am looking to replace Enterprise Lib. Cache with App Fabric distributed cache engine. I am going to be honest - I have no idea where to start. I know that SharePoint 2013 is already utilizing App Fabric so I my first concern is of configuration and overall architecture:
Can I use the same engine used by the SharePoint farm or do I have to rely on my own custom instance?
I need to develope WAS application and should be hosted into Demandware platform. Can i develop the WAS application using tomcat and can host it into the Demandware or should WAS application be developed in the Demandware platform?
I am new to Demanware platform and WAS. Guide me.
You cannot build a web service outside of the UX Studio paradigm like what you described, but you can build a psuedo-service like pipeline in UX Studio that returns JSON, XML, etc. and it will work more or less just like any other REST service.
Demandware is Software as a Service (SaaS) provider, which will not allow you to access the underlying infrastructure (e.g. Tomcat server, Oracle DB, etc.) to make/install your custom extensions.
UPDATE (25.09.2015):
Currently Demandware are making extensions to their controllers, migrating from pipeleine-based controllers to script based ones. Chances are that at some point they may even introduce an API for creating web-services.
Until this happens, your only option is to make some custom pipelines and utilize something like XML/JSON over HTTP for this type of functionality. (Or if you insist on having it as SOAP based service, you would need to parse the SOAP envelopes with explicit code)
Demandware platform is a proprietary technology which allows developing only using their sandboxes and own IDE "UX Studio". All this stuff is available for demandware developers on their xchange portal. Access there could be requested by a merchant you do a development for.
Demandware has the core framework is closed to third parties and is exposed via the Demandware script and REST API's as well as Demandware's own Pipelet system.
Sadly you can't deploy external application in Demandware server, we have to separately create new app in UX studio
You can get the proper help on Demandware Wiki or on Exchange
we're looking to implement TFS 2010 for our teams which are split up at onshore and offshore. we've TFS Proxy in plan for the offshore team, with the TFS setup at onshore.
i know that when the clients at offshore checkout their code, it will be from the proxy whereas the webservices call will be directly on the app tier.
we will also have build machines at offshore & onshore. the onshore build machine can get the latest code version from the app tier, and that is just fine. my question is when the build machine at offshore requests a get latest, will it get the code directly from the app tier at onshore or is there a provision where the files can be got from the tfs proxy?
any help with this is going to be of much help. thanks.
MSDN: Configure Team Foundation Build Service to Use Team Foundation Server Proxy
You can configure Team Foundation Build Service to retrieve files from Team Foundation Server Proxy by modifying a registry entry on the server that is running Team Foundation Build Service. If you modify this entry, Team Foundation Build Service at the remote site can work with version control from the proxy's cache.
http://msdn.microsoft.com/en-us/library/cc716770.aspx
I found some questions here on how to create a SaaS. This much is easy, but what I don't understand is what makes an application a PaaS and not a SaaS. What lines does an application cross before we can start calling it a PaaS (platform as a service) and not just a SaaS (software as a service)? It seems like a small difference but I can't pinpoint it.
I would welcome even examples of PaaS if you can point something about them that makes them a PaaS and not a SaaS. A common name in this area is salesforce but I don't know much about the service itself to understand from it why it's a PaaS.
Edit: I feel that from a programmer's perspective, it's the same job, or no? I think the only difference is the PaaS is for developers as end users and SaaS is for regular users as end users. Does that sum it up?
Using Salesforce.com as an example - they offer the Force.com platform, which provides a database, a programming language, integration features and so on. You can use this platform to build whatever you need/like.
Salesforce also offer their own, prebuilt CRM applications - this is software-as-a-service as the application has been built for you, you simply start using it.
PaaS provides you with the components and tools to build something; SaaS provides you a prebuilt application you can pick up and use straight away. The line can be blurred - again, using the Salesforce example, you can tailor their SaaS offerings by using some of their PaaS technologies.
On the surface it looks pretty simple; Think of Amazon's EC2 or Microsoft's Azure as PaaS and various Services (like a weather serivce) or CMS as SaaS.
PS. Try searching for "PaaS vs. SaaS" on google.
This definition is also pretty common:
Level 1: IaaS > Virtualization, Server, Storage, Network (AWS, Rackspace …)
Level 2: PaaS > Runtime, Middleware, OS (Heroku, appfog, dotcloud …)
Level 3: SaaS > Application, Data (most startups)
Basically, SaaS is a specific online software solution such as CRM, Project Management, Billing, Accounting etc. that mostly flexible by providing some scalability and extensibility features.
On the other hand, PaaS is kind of base services that contains required features to host many different type of online softwares including SaaS applications.
At this point i can say that there are different kind of PaaS in the market. Some of them are targeting the developer by providing infrastructures and frameworks in specific technologies such as Microsoft Azure, Google Apps, Heroku and more ...
The others (including Force.com and Viravis) provides complete solution for a specific needs (such as online database applications) for developers and business analysts as well as the end users by providing required tools to develop online applications without programming.
As a result, all of the PaaS providers in the market presents a simlified solution for creating and running online softwares including SaaS applications. I think this is the main difference between SaaS and PaaS.
Check this Question for other opinions.
I think this is how it is -
IaaS - Like having a computer with or without an OS/operating system.
Think brand new computer with or without Windows OS.
PaaS - Like having a computer with an OS, and tools/software to
make your own tools/software or apps.
Think computer where you are allowed to touch only things like an installed
database, IDE, web server etc.
SaaS - Like having a computer with a pre-loaded software/tool.
You can tweak the pre-loaded tool as per your needs, but you
don't get to make your own tools.
Think computer where you are allowed to use only excel spreadsheets.
You can change the font size and stuff, but you are pretty much stuck
with excels features. If you wanted to make a software like excel yourself,
you need PaaS or even IaaS.
Real world examples -
IaaS - Rackspace, Amazon Ec2 etc.
PaaS - Heroku, Google App Engine
SaaS - SalesForce, Workday
PAAS (Platform As A Service) :
A layer on top of IAAS (Infrastructure As A Service)
Examples: Runtimes (like java runtimes), Databases (like mySql, Oracle), Web Servers (tomcat etc)
SAAS (Software As A Service) :
A layer on top on PAAS
Examples: Applications like email (Gmail, Yahoo mail etc), Social Networking sites (Facebook etc)
source
When you develop an application and deploy it on server(Example: www.gmail.com), then many user comes and start using your application. Your application will be SaaS for the users who are using your application.
When you have developed an application and want a server(Pre configured server like having linux, java, hibernate, mysql etc.) that can run your application. Application that provides you that pre configured server will be PaaS for you.