What is the price of implementing and hosting couchbase lite / mobile myself - xamarin.forms

I'm just getting started with Xamarin development, and I'm discovery the wonders of using Couchbase Light / Mobile to manage local data and data sync. I watched a very nice video from Xamarin Evolve 2014, in which the folks from Couchbase presented some great use cases for using Couchbase in Xamarin mobile apps.
My question is: given, that there are 3 components involved - the Light/Mobile library, the Gateway, and the Server - for me to start my development, and, later on to deploy in production: are all these components commercial, are there an open source counterparts? If only commercial components exist - what is the pricing?
-Eugene

Couchbase and Couchbase Mobile are Open Source under an Apache 2.0 license, with the development in the open on github.
There are two binary releases, a Community Edition and an Enterprise Edition which each have different terms in their license agreements and as pointed out, the Enterprise Edition is through subscription, which gives the subscriber access to Couchbase, Inc. for help, enhancements and an escalation path when you need to resolve something right away.

Related

Migrating off of the MSDKUI

I have an old project that needs updating. It is using the MSDKUI.
There is a note at the bottom of the MSDKUI iOS githib page:
https://github.com/heremaps/msdkui-ios
Maintenance Notice
The MSDKUI project will be discontinued as it is incompatible with the new 4.x HERE SDK releases.
I am using the Enterprise API for the truck routing features. The Enterprise API is on v3 and the Navigation API is on v4
Do I migrate off of the Enterprise API to the Navigation API?
If I can continue using the Enterpise API do I need to immediately come off of the MSDKUI? Or can I continue to use that + the Enterprise API for a while until the Enterprise API moves to v4?
As stated in the maintenance notice: The HERE team does not plan any additional feature implementation for the future. This repository will stay online and it can still be forked and used for commercial or non-commercial projects, but we plan only limited maintenance work from now on.
There is no need to switch immediately but I would recommend to get in contact with us to start evaluating the Navigation release based on 4.x.
I would recommend to migrate from the older 3.x version to the new 4.x editions, e.g. the HERE SDK Navigate Edition for iOS.
It has excellent truck features, like dedicated truck warning functions and truck map layers.
The documentation for 4.x also provides a migration guide that explains how easily you can migrate from Premium to Navigate.
Regrading the MSDKUI toolkit: There's no equivalent yet, but if you consider to switch to Flutter, then you can benefit from this new Ref App project on GitHub. It has a lot of ready-made UI and it's free to use in commercial apps.

Is UWP/Xamarin ready for enterprise applications?

Is UWP or Xamarin is usable for enterprise applications like CRM, ERP, etc...
Is the any sample on market, or there are any patterns?
These platform are firstly mobile platforms, but they had a excellent support, a lot of graphically possibility and very modern look and feel. These platform are designed for mobile application in first line, but they are ready for enterprice applications?
Of course the are lot of extension in built control (DataGrid, Charts) which makes possible to create enterprise application. But I did not find any. Is there and problem or drawback of this platforms?
Thank you
Is UWP/Xamarin ready for enterprise applications?
The answer is yes. Xamarin UWP applies not only to mobile platforms but also to desktop platforms(Windows 10). You could also run it in the desktop client. This benefits from the native universal window platform.
For pattern, there many pattern you could select such as publish-subscribe MVVM etc. For more you could refer Enterprise Application Patterns using Xamarin.Forms.
For enterprise publish, you could think of Xamarin UWP application as UWP application, and Distribute LOB apps to enterprises document has described the details of publish process.
And this blog describe the possibility of Xamarin.Form enterprise application that you could refer.

Developing ASP.NET application for a Linux Server [duplicate]

This question's answers are a community effort. Edit existing answers to improve this post. It is not currently accepting new answers or interactions.
For a developer with a Java background, I am interested in exploring software development using the ASP.NET tools/platform as well.
Java web applications (.jsp and servlets) can run on many server platforms.
Question: Will a .NET web application be able to run in a Linux based server? Considering the scenario of not being able to use a Windows server for hosting a web app.
So I know this is an older question but I think it could stand an updated answer.
Microsoft has officially released asp.net vnext and its open source and deploy-able to both Linux and Mac. Its all still pretty new but does rely on the latest builds of mono and thus currently needs you to compile the mono-framework but in time I suspect that it will be easier to access as various linux distros release updated versions of mono. This is a how to setup guide
This information may be somewhat volatile and with updates is due to change.
Update ASP.NET CORE 11/10/2017
asp.net vnext is now known as asp.net core.
asp.net core is being treated as a high priority in Microsoft due in part to its use with microservice architecture and docker and container technologies
It has become much more compatible with existing .net libraries due to .net standard 2.0.
It performs well when compared to other technology stacks such as go and node.js
It depends what specific .NET technologies you're using. The Mono Project provides an Apache module (mod_mono) for running ASP.NET sites, and from what I gather it works well.
Mono doesn't support all the .NET APIs, though - notably WPF (and possibly WCF too, I can't remember) - but it does provide good support for much else of the framework.
If you're starting from scratch and particularly want to target non-Windows servers, then ensuring your project works with Mono would be a good goal to aim for. However, if you need particular APIs or language features that are not supported by Mono, then you will need to use a Windows server for deployment. It's a design-time/architectural choice that should make up front.
You might want to consider this guide that helps Windows developers port their code to Mono/Linux:
Guide: Porting ASP.NET Applications - Mono
I can speak from experience. Even if your ASP.net website only uses .NET libraries supported by Mono you are going to have a hard time getting it to run if its anything beyond Hello World.
You won't have to re-write much code but you will spend hours/days/weeks dealing with little issues with mod_mono/xsp/apache configuration and file permissions and error handling and all the little things that go into a large website. (Be prepared to spend a lot of time asking questions on serverfault :) )
The problem is that a lot of people don't use Mono for ASP.net websites and so there aren't as many people reporting bugs so a lot of things that are minor bugs go un-fixed for a long time.
Now you can publish ASP.NET 5 app to Docker on Linux with Visual Studio. See the below post from Scott Haselman
http://www.hanselman.com/blog/PublishingAnASPNET5AppToDockerOnLinuxWithVisualStudio.aspx
Since the technologies evolve and this question is top ranked in google, we need to include beyond the mono the new asp.net core, which is a complete rewrite of the asp.net to run for production in Linux and Windows and for development for Linux, Windows and Mac:
You can develop and run your ASP.NET Core apps cross-platform on
Windows, Mac and Linux. ASP.NET Core is open source at GitHub.
Yes we can. get familiar with Mono Project and read this article to get started.
For ASP.NET on Linux, check out Mono.
That said, thousands of sites run on Windows Server without any issues. A poorly-configured server with any OS will be vulnerable; Linux won't save you from a poor admin.
So I guess my "best practice" for deplying an ASP.NET app would be to use Windows Server 2008 (likely Web edition). And hire a good administrator.
You can use Mono to run ASP.NET applications on Apache/Linux, however it has a limited subset of what you can do under Windows. As for "they" saying Windows is more vulnerable to attack - it's not true. IIS has had less security problems over the last couple of years that Apache, but in either case it's all down to the administration of the boxes - both OSes can be easily secured. These days the attack points are not the OS or web server software, but the applications themselves.
dotnet is the official home of .NET on GitHub. It's a great starting point to find many .NET OSS projects from Microsoft and the community, including many that are part of the .NET Foundation.
This may be a great start to support Linux.
Now a days .Net is run in multiple platforms,like linux ,Mac os etc.
but mono is not fully platform independent ,Because to deploy .NET in another OS required
third party software.so it is not like java platform independent.
Mono is running in different platform ,because of JIT is there in different os.
Mono is not fully success in moonlight(silver light in .NET) .Not only Research is going on.
Mono uses XSP2 server or apache . some of the big companies are using this project,Some of the robotic project are also running on mono.
For more details http://www.mono-project.com/Main_Page.
There is the Mono Project from Novell that will allow you to run ASP.Net on Apache.
http://www.mono-project.com/Main_Page
The Mono project is your best option. However, it has a lot of pitfalls (like incomplete API support in some areas), and it's legally gray (people like Richard Stallman have derided the use of Mono because of the possibility of Microsoft coming down on Mono by using its patent rights, but that's another story).
Anyway, Apache supports .NET/Mono through a module, but the last time I checked the version supplied with Debian, it gave Perl language support only; I can't say if it's changed since, perhaps someone else can correct me there.

Downgrading from Alfresco Enterprise to Alfresco Community

We’re thinking about downgrading our Alfresco Enterprise 3.4.1 to Alfresco Community.
I’m used to Alfresco Enterprise, but I have no experience with Community version.
We’re using EMC, Alfresco Explorer and our own development based on Web Services API and Foundation API.
I’m worried about database migration. Could I simply configure Alfresco Community 3.4.e to use our Oracle Database for Alfresco Enterprise 3.4.1? Is the schema compatible for both Community and Enterprise distributions? Which version of Alfresco Community should I use? 3.4.e? What is the downgrade path between distributions? Is there any kind of correspondence between versions of both distributions?
Any downgrade experience, guide or any related information will be welcomed.
The Alfresco Community Edition is open source, and works with a fully open source stack. Your DB options are PostGreSQL (recommended) or MySQL.
Alfresco Enterprise supports the open source databases that Community supports, PostGreSQL and MySQL, as well as a few proprietary databases too. You can look at the Database Configuration page for more information. Support for Oracle databases is only available in Enterprise.
If you want to keep paying Oracle all that money for your database licenses, then you'll need to continue to pay a tiny fraction of that cost to Alfresco for an Enterprise License. Community, being open source, only supports a fully open source stack, so you can't use Community with your uber expensive proprietary database!
If you were using an open source database like PostGreSQL or MySQL, then you might be able to do the switch as part of an upgrade. Enterprise Service Packs (eg 3.4.1) are normally newer than the equivalent community release from that series (Community gets the bug fixes on Head). Moving from a 3.4.x enterprise service pack back to a 3.4 community wouldn't be recommended, but moving from 3.4.x enterprise to a 4.x community might work. However, that's not a tested migration path, so you could well be on your own... Alfresco QA tests community -> newer community, enterprise -> newer enterprise, and community upgrading to enterprise, which are the supported paths.
This question is similar with this one about difference between Community and Enterprise version
You can not use Oracle database for Community version. It is only available for Enterprise.
There is not downgrade path for any Alfresco versions. If you are using Enterprise 3.4.2 try to use the same Community version.
I searched the web for possibilities of a downgrade from enterprise to community version, too. What I found is the answer "You may be able to downgrade, however that is never supported or tested."
When downgrading, you have to keep in mind that the community version X usually has more functionalities than the enterprise version with the same version number.
So, downgrading is experimental. I have already seen log files where the downgrade failed.
Maybe it is an option for you to export all content and import this ACP file on the new system with the community version?
Please read your contract carefully. Support and Licensing might not be the same thing in your case. If you don't want to pay anymore to Alfresco, you might be entitled to keep using your current enterprise version, but you would not longer have support. Before considering downgrading, check your contract. If in the future you want to get support and upgrade again, it might just be easier to do it with your current Alfresco Enterprise version.
But, as I said, it depends on your agreement with Alfresco.
Migration of the Alfresco repo database is no fun at all. There is no official way switching databases and in 3.x version you may have serialized objects which could be stored by hibernate db specific. This changed a little when Alfresco removed most of hibernate dependencies after 3.4. It may be an option to migrate to 4.0 EE first, migrate the db to postgres (which is closer to oracle than mysql) and finally upgrade to Alfresco Community 4.2.f (latest version with Web Services API). This may be a lot of work (even in your code) but should work.
Here in Germany it is legaly problematic to limit software usage in time if you sell a support subscription (at least for the old contracts you may have) so customers here can request support for a time unlimited EE license key before canceling the subscription contract. I recommend you go this way and update your old 3.4 to the latest 3.4.x or 4.x enterprise version available and stay on Oracle db if you don't care these costs. This step should be done anyway ;-)
I have done it before in order to create a development environment in my local machine,
First, you cannot use Oracle database so you have to use postgresql (recommended) or MySql, exporting and importing the database is not recommended, so you have to create the repository hierarchy and fix the rules, etc., then copy all custom jars (jobs, actions, workflows...) and library from the lib folder to the new one,
If you are using an external application based on alfresco uuids, make sure you updated the uuids after creating the repositories and rules

ASP.NET Microsoft CRM Starter kit

Can anybody recommend a "starter kit" or basic framework for an asp.net web app that can read data from Microsoft Dynamics CRM?
No updates are required from the app at this time, just reads. I'm currently reading through the SDK documentation but a simplified project would be quite handy.
Some sample code (in C# and VB.net) for doing various things with CRM comes with the SDK.
Have a look in the \sdk\server folder and the \sdk\visualstudiotemplates folder in the same folder that you installed the SDK in. Hopefully these should give you a head start.
As for Microsoft Dynamics CRM 2011 Software Development Kit (SDK) the download can be made here
In the /sdk/crmsdk2011.chm document one should find many tutorials that are assisted by code (.sln included)

Resources