I found it easier (because I have been working on it) to create web applications using Oracle ADF and related tools but I am not sure of how much it will cost.
I am no entrepreneur or organization, I am just a developer but I had an idea of developing web application (a typical data input, store and report like) for which Oracle ADF will ease my development. The Oracle's pricing list looks complicated. My total operational budget(including hosting, and licenses) is around $50-$100 per month (which I know is very less, but GAE or AWS comes around this budget). I am looking at a small userbase here mayB grow slowly.
Thanks
If I'm not mistaking is the cheapest WebLogic Server license +- 20.000 dollar per CPU.
You can use ADF Essentials + GlassFish. Those are both free to use, the downside is that ADF Essentials doesn't support out of the box security.
Oracle does have a cloud offering where you pay per month and it can run ADF apps on WebLogic - see - https://cloud.oracle.com/mycloud/f?p=service:java_pricing:0:::::
But given the amount you had in mind you might want to look into the GlassFish+ADF Essentials option. http://multikoop.blogspot.com/2012/09/adf-essentials-in-redhat-cloud.html
Related
I have completed my first web & Mobile project in Spring mvc 3.2.6 + Hibernate + Maven,Mysql & Rest Services.
Now i want to host the application.So that i can hit the webservice via mobile & host the web application.While browsing the google found the following link.
http://aws.amazon.com/free/
https://www.openshift.com/
http://azure.microsoft.com/en-in/pricing/
http://www.rackspace.com/cloud/private
https://www.heroku.com/pricing
https://appengine.google.com/start
So could you please anyone guide which one of the above server is good to host.Right now i am planning to use FREE version of the above server and in future i may use a paid version.Could anyone please which one is best?
I appreciate your answers & suggestion!!!Thank you.
I can say for Openshift. The best features it gave to you is:
No credit card required
No trial time
Doesn't need to sleep
Can scale, you can use up to 3 small gears on free plan, all loadbalanced by default
Many cartridges (like a pre-built package with servers) like MySQL, Mongo, RedisCloud, AMQPCloud, a bunch of others services using the Marketplace with a lot of free ones
Sleep when nobody is using, when someone hit a request the server goes on again , also auto scale up and down
Easy setup and Java ApplicationServers support (Tomcat, JBoss, Wildfly***)
Easy build customization via hooks
You can upgrade to bronze plan without paying a coin using the free gears you have, and you get alot of features
Runs on AWS Infrastructure
EDIT
Think of Gears as machines, it's just a fancy name they give to it, like Heroku named theirs Dynos
Price plans are located here with side by side comparison. You can check the marketplace offers here. Also they have some quick starters, all Java cartridges comes with Java 7 and Maven 3 installed by default. See here for more detailed tech.
They have a developers site with content to get started, help and documentation
** Small gears are machines with 1 CPU, 512Mb of RAM and 1GB disk
*** Wildfly on a free plan takes so much disk space, then is pratical impossible to use, but for paid plans is awesome
I am hoping to get some advice as to how i can figure out what is going on with some performance issues i am suffering from. I have a custom MVC application which is running on Azure Websites in West Europe datacenter. I have one of our offices trying to connect to the website from Singapore which is where the problem lies. If i connect to the website myself (from UK) the performance is fast and zippy. If our Singapore office tries to connect the performance is terribly slow. Sometimes getting to the initial homepage is slow (i.e. no database connections required for login page).
The page will sometimes just sit and "hang" there. What i want to know is how can i debug the performance issues with Azure? What kind of monitoring or performance checks can i do to see if it is a website / sql issue.
Thanks
I would suggest using Application Insights. It's easy to add to a custom MVC app, and will give you good info to help determine where exactly the issue lies.
https://azure.microsoft.com/en-us/documentation/articles/app-insights-detect-triage-diagnose/
The Azure New Relic add in from the market place is very useful. There is a free version which gives you plenty of detail on browser performance and basic sql profiling.
It can provide such details as shown in the screen shot below.
You can use the Support Site Extension (http://azure.microsoft.com/blog/2014/12/01/new-updates-to-support-site-extension-for-azure-websites/) which would allow you to look at live event logs and HTTP traffic. There are also some more advanced tools for performance issues (i.e. memory dump, event viewer logs). For a deeper dive into debugging in Azure App Service see: https://channel9.msdn.com/Events/Ignite/2015/BRK4704.
Also as Ben said, Application Insights (https://azure.microsoft.com/en-us/documentation/articles/app-insights-detect-triage-diagnose/) may help.
I have a project and I'm planning to start the web app as an Azure Web Site and then migrate it to an Azure Cloud Service (also called Hosted Service) if it is needed as a scale strategy.
The decision is because I read that Azure Web Sites are more simple and fast to develop with almost no Azure-specific configurations or code. So starting fast and simple is a good starting point for the project.
But, is that a good starting point for you?
Is migrating an Azure Web Site to an Azure Cloud Service the same as you were migrating a normal ASP.NET Website to an Azure Cloud Service?
Would you start with an Azure Cloud Service right from the beginning? If yes, why?
Thanks for your time.
There are benefits to both deployment models, it will eventually come down to what you are trying to achieve and ultimately the success of your application.
Below I've outlined the Pros and Cons of each of the models to ensure that you're making the right choice for your applications goals.
Windows Azure Web Sites
You have properly identified that Windows Azure Web Sites is a great starting point for an application, however you could also consider that Web Sites does offer enough scalability for many solutions.
Pros
10 Free sites during preview [Free for 12 months]
Easy Deployment (use Git, TFS, Web Deploy or FTP)
Quick Scalability (You can move to your own dedicated cluster [aka reserved standard])
Simple Development (Supports Classic ASP, ASP.NET, Node.js, Python & PHP)
Persistent Environment (most people are used to this)
Cons
No SSL Support on Custom Domains
in Preview (currently no SLA)
Windows Azure Cloud Services
Cloud Services (formerly known as Hosted Services) is definitely the vision for the future of Web Applications. It is built with resiliency in mind to keep the cost of applications affordable by scaling to meet demand, and dial back capacity when your traffic slows.
Pros
Increased control over the cost of your application (if architected correctly)
Flexibility (You have full control over the environment)
SSL Support
Language Agnostic
Web Server Agnostic (although IIS is available by default)
Auto Management of Servers
Cons
Architecture should be carefully considered
Deployment time is slower (Slows development cycle)
Things to consider for Portability
The items above might have given you enough to plan the immediate future of the application and it is very likely that you might want to consider Cloud Services in the future (it fits a number of application scenarios better in the long run).
Here is a list of things to help portability between Web Sites to Cloud Services:
Start thinking Stateless
Windows Azure Web Sites is nice as it is a persistent environment, which means you are able to store things like session state and assets to the disk.
Although this is a good feature, it's best to start planning towards a stateless application, if your end goal is to be in Cloud Services. Here are a few things you can do to start thinking stateless:
Don't rely on Session State
If you need it, come up with a strategy to make it scale (Caching Service, SQL, or Storage)
Use the Storage Service
Assets such as Static HTML, css, javascript and images are better placed in Storage
Avoids additional bandwidth on your Web Site (potentially stay shared longer for lower cost)
Can be CDN Enabled, provides a better experience for International markets
Easier to update web assets when application is migrated to Cloud Services
Storing User content
If your application already stores to the Storage Service, there is one less code modification in the future when moving to cloud services.
Make it easy to discover patterns in your Data
The benefit of Cloud Services is it enables you to reduce cost by only scaling what needs scaled. Starting the process of identifying your scale units i.e. How you partition your database or Tables in Storage.
I read all post and all of them are very helpful.
In addition to all post , I found an info on msdn : Windows Azure Websites, Cloud Services, and VMs: When to use which?
With Windows Azure Websites you can:
Build highly scalable web sites on Windows Azure.
Quickly and easily deploy sites to a highly scalable cloud environment that allows you to start small and scale as needed.
Use the languages and open source applications of your choice then deploy with FTP, Git or TFS, and easily integrate Windows Azure services like SQL Database, Caching, CDN and Storage.
With Cloud Services you can:
Build or extend your enterprise applications on Windows Azure.
Create highly-available, scalable applications and services using a rich PaaS environment. Support advanced multi-tier scenarios, automated deployments and elastic scale. Deliver great SaaS solutions to customers anywhere around the world.
And also there is summarizes the option on msdn :
And comparing some features Web Sites and Cloud Services on msdn:
Azure is a great place to have your app, but there are some considerations you need to know before start migrating it.
Azure Websites and Hosted Services are really trivial to deploy. With
Visual studio you generate the package and simply upload it. Then you
have a Development environment to check it. If it's ok for you, swap
ips. If it's not ok for you, upgrade again.
Your instances have some properties that could be annoying. For
example, you cannot be sure about your IP. Then if your app works
with some provider using IP restriction, you will need to figure out
how to proceed.
More considerations. Your "server" could be reimaged at any moment.
If you store something on the local disc, that file could go away at any moment.
Azure works very nice if you have at least 2 instances or more for
each website. Maybe your app is not prepared for that. The first step
will be managing the sessions with the appFabric. Is really
easy, just a change on your web config. Be careful because this
session state doesn't work exactly as the "old one". You cannot store
non-serializable objects (should be easy to adapt) or a very large objects (more than 8MB).
If you are going to develop something from zero, I suggest you to start into azure from the beginning. The reason is simple: it's really cheap to start and you will not pay serious money until the app have lot's of visits. It's also very cheap to setup a SQLAzure and a storage account. One you have all in place, it's easy to add more instances or scale up.
Example:
Imagine you have an idea and you wish to show up to some possible investors.
You start setting up a little SQLAzure database (1GB ), $9,99 monthly.
Then you build a site and you put 2 extra small instances, $18,72 monthly.
Let's say you need 100 GB of space (images, backups, ...), $12,50 monthly.
At his point, you have all in place to start your business paying less than $50 monthly.
If you site have exit and the visits starts to come, you change your instances for small instances (it's really dangerous to have production environment with extra small instances, because do not have cpu reservation). Then you change the extra small cost ($18,71) up to $57,60. Maybe you need more space to that SQL Azure? etc...
prices calculated from here: http://www.windowsazure.com/en-us/pricing/calculator/?scenario=web .
Those are few tips, there is a lot more. My advice is to start a trial account and play with it.
Final advice: Its very easy to solve everything just purchasing more resources. Sometimes you need to refactor and optimize your code. If you simply add more resources each time you have a problem, you could end with a huge bill and a very messy code.
Hope it helps!
Another advantage of Windows Azure Cloud Services over Web Sites is that a cloud service can be added to an Azure Virtual Network. This can give it access to on-premises resources like databases. So if your requirements are such that you need the scalability offered by Azure but need to keep your data on-premises due to security restrictions, cloud services is a better choice.
Azure web sites cannot be part of an Azure virtual network. To access on-premises resources mechanisms such as Azure Service Bus Relay must be configured.
We've had our web site running on PHP on some hosting and at some point decided to move it to Azure (where sits main part of our service). We've started with Azure Web Sites which was great from development point of view (mainly integration with git). But after about a week of testing (when we've decided to actually move the production web site) we've found that currently
No SSL for custom domains
Custom domains are available only for reserved instances (no shared infrastructure)
SLA
So we moved to Hosted Service. The main problem for us was lack of ability of simple deployment (need to build package and upload whole package of the web site), and found solution was to use dropbox - as a startup task for role, we're installing dropbox service on the machine, which takes all the web site from dropbox, which in turn have SVN checked out folder, so site updates became very easy.
I have been making Desktop applications for last few years. but now i have quite that job and thinking about doing working for myself. I have gone through many ideas. finally i decided to develop Online billing application . Since i am new in web application i know very little about web technologies.
I am thinking about developing that application in php or asp.net with mysql database. I don't know which one is better.(you can guide me here). I don't know whether its good idea or not.but i don't want to do job and work for myself that's for sure.
its going to be a big project so I was making budget for this whole project but i don't know what kind of hosting i will need for this app because database load will be very high because its billing application. i don't know how much it will cost me.I will give user free trial for 30 days to use application and if they like they can upgrade their accounts.
So i need your help to decide what kind of hosting will be appropriate.is this ok if i use webhosting that we use to host website which will cost me $10 to $15 a month or i will have to use cloud hosting which will cost me a lot?
I hope this link will give you idea. I want to make application like this : http://www.rapid-billing.com .
pls help me out. it might me small things for you but to me it matters a lot. Thanks
Initially, you won't have very high traffic, so using a cheap, shared server should be fine. If you outgrow it, then you must have some money coming in, so the added expense of cloud hosting will be more tolerable. There's no need to go all-in before you even get going.
That said, many cloud hosts offer some amount of hosting free, which would probably suit you just as well during initial development. An added plus of starting in the cloud is that you won't have to migrate later. Off the top of my head, Google App Engine and Heroku come to mind as well-known cloud hosts with a free tier. Microsoft Azure also provides a free 3 month trial, and I imagine they'd be a good host if you choose to go with ASP.
A client has asked whether or not I can provide some support for his intranet which runs on Oracle Application Server Portal. Not having used this technology before I thought I'd ask if anyone else has and what they thought of developing for it.
I'm a c#/ASP.NET developer so I note with apprehension that there's no mention of .NET in the developers guide. Anyone tried to make the two work together and lived to tell the tale?
Oracle Portal was never meant to be a "platform," but instead to fulfull a specific need. When Portal was not the right solution directly, the pointer was to JDev and BC4J, plus needed other stuff. I have done extensive Oracle Portal development and for what it is, it did just fine (i.e. a "portal" to core data and applications with some exposure of that data via the portal).
The current direction of the portal product is to separate it out and have it under Oracle's "Web Center." The focus here is to make the development of portlets closer and closer to standard java development. You can find the official statement here:
http://www.oracle.com/technology/products/ias/portal/pdf/oracle_portal_sod_r11.pdf
Web Center is much more of a "platform" that has all the buzz words around the 2.0 technologies. Including content mgmt, portal, and a .NET WSRP integration feature/function. I would check that out in addition to portal (which does quick and easy portlets for web center too).
My company (a dedicated Oracle shop) and I have used Oracle Portal for many years and have been very successful with it. But I have to warn you against taking on this task if you do not have experience with PL/SQL (Oracle's proprietary database programming language).
An intranet built on Oracle Portal is likely to make extensive use of custom-built "portlets". You can build these in Java or PL/SQL; in my experience, 95% of all real-life portlets are built using PL/SQL.
Theoretically, if you use the latest version of Oracle Portal (10.1.4), you can consume WSRP 1.0 portlets. So if you can build portlets in .NET that will communicate using WSRP 1.0, you could integrate these. But if your customer asks for "support", they probably expect you to be able to tweak their existing portlets - and that would require PL/SQL programming experience.
There's a fairly good description of Oracle Portal on the Oracle Wiki:
http://wiki.oracle.com/page/Oracle+Portal
Strategically, Oracle has placed Oracle Portal is in the "Continue & Converge" category, which means that it's supported and will receive minor updates. Their strategic portal product these days is Oracle WebCenter, but that's a $125,000 per CPU behemoth; it's likely to be overkill for 99% of all sites built on Oracle Portal.
The only experience I've had with an Oracle Portal was obliquely, when I inherited a system that used one for a relatively simple maintenance web application. A large part of my opinion of Oracle's stuff comes from my background with SQL Server/ASP.NET, but Oracle is just plain harder to set up and administer and keep running, and that applies not just to the database but also to auxiliary stuff like Oracle Portal, their SOA suite, their Mobility Server etc. Even experienced Oracle people tend to agree with this, so hopefully I won't piss anyone off.
I would definitely not provide support for an Oracle Portal application (or any other Oracle product, for that matter) unless I had a lot of experience with the tools.
I have developed a dozen or so Java portlets for Oracle Portal over the past few years. If you are not necessarily tied into using .NET to develop portlets and do not want to use PL/SQL, I would recommend this approach. Oracle's Portlet Developer Kit (PDK) offers good functionality (http://www.oracle.com/technology/products/ias/portal/pdk.html).
I've not tried the WSRP approach but have deployed ASP.NET apps using the Web Clipping Portlet that comes with Oracle Portal with some success.
I have found Portal to be difficult to work with at times and a good knowledge of the other components in the Application Server stack (OID, SSO, Oracle DB, etc) is very helpful.
I recommend that you take a look at Oracle's WebCenter 11g Suite. When Oracle acquired BEA, it took on a few portal products, but from everything I've heard, WebCenter 11g is Oracle's story as far as portals go for the future - all the active development will be concentrated there. You can find a decent amount of material out there. Here's a blog post to get you started on WebCenter 11g.