I came across the terms Cloud Hosted, Cloud Optimized and Cloud Native recently. There's a good answer on the distinction between those terms.
Then I saw a few presentations where Cloud Native was equated to SaaS.
According to the NIST definition, Cloud Services, including Software as a Service solutions features:
Broad Network Access
On-demand Self Service
Resource Pooling
Rapid Elasticity
Measured service
"Cloud Native describes the patterns of high performing organizations delivering software faster, consistently and reliably at scale".
- Pivotal
So, it seems like the definition of Cloud Native focuses largely on how software is delivered. SaaS seems to be more about what that software actual is, by category.
Therefore, is it safe to say that an app being Cloud Native does not make it SaaS?
Related
We have a few bare metal servers at IBM with their basic support. I am considering upgrading our support level. The primary reason is the discomfort I have with not having any sort of account manager (although advanced support only gives us a faster support response time from what I can tell).
Does anyone have the specific experience they can share with the benefits (or lack of) of this added support level?
Thx
On Db2 v11.1, how do we get or setup the notification for DBA team if there is any hang or slowness situation in off shift working hours?
The answer depends on the external monitoring and alerting solution you deployed, and how you configure that tooling in your environment.
This application layer tooling is not built into Db2-LUW, although APIs exist in Db2-LUW for such tooling to get the data it needs in order to operate.
IBM and several third parties offer solutions for real time monitoring and alerting in this space. Many cover app-servers, web-servers, database layers, networks and operating-system layers and have different alerting configurability. Many have plugin type architecture with plugins for Db2-LUW monitoring. Do not use stackoverflow for product recommendations however.
For "slowness", this is only meaningful to measure usually at the application layer, in terms of response times and other metrics etc.
For database-hangs, IBM offers a db2-hang_detect script that tooling can orchestrate , requires careful interpretation and even more careful testing.
I'm building a social media app targeting a specific nitche of users.
The app is built in HTML5 with features similar to Facebook or Instagram.
Can the entire application run on Bluemix?
What exactly are the benefits of bluemix to an App of this nature?
Thanks.
Blumix is a PAAS. The benefits of Bluemix are the benefits of a PAAS infrastructure and of the support:
cost savings
reduced technical maintenance
The upfront costs for purchasing servers, other hardware, and the necessary software licenses are eliminated.
Technical Benefits
Choice to choose the programming models, languages, operating systems and databases
Switching in different environments – Development , Test ( System, Integration, UAT,etc)
Hardware Scalability - Auto scaling supported through DevOps Services
Elasticity - Supported through DevOps Services
Automation – Supported at various level from runtime provisioning to development lifecycle
Improved development productivity
Business benefits
Lower Total Cost of Ownership
Faster time to market
Business Continuity
Savings on costs associated with hardware resource consumption and support infrastructure
Facebook is a social network.
And yes you can do something like this on Bluemix choosing the right services. I suggest you to take a look at Bluemix Catalog in order to understand what services you can create and use on Bluemix to do what you want: https://console.ng.bluemix.net/catalog/
In this particular case I suggest you to take a look to Object Storage Service (to store files) - DashDB (or other db service) to store db information - SSO to manage the authentication.
I suggest to take a look at this article too: https://www.ibm.com/developerworks/community/blogs/96960515-2ea1-4391-8170-b0515d08e4da/entry/Moving_to_Cloud_Platform_as_a_Service_Pros_and_Cons?lang=en
This a quite large topic, however let's see some of the services you could use on Bluemix developing your application:
the first thing I think about is the IBM Graph service: it is an easy-to-use, fully-managed NO-SQL graph database service for storing and querying data points, their connections, and properties. IBM Graph offers an Apache TinkerPop3 compatible API and plugs into your Bluemix application seamlessly. This service can be used for building recommendation engines, analyzing social networks, and fraud detection.
Insights for Twitter: this could be useful if you need to integrate with Twitter for example analyzing the trends and providing your users updated news.
You could take a look at the Watson cognitive services in the Bluemix Catalog, some of them can be useful for social networking purposes (eg. Language Translation to connect people speaking different languages, or Personality Insights to identify psychological traits which determine purchase decisions, intent and behavioral traits).
The application can entirely run on Bluemix (you can choose the Runtime you prefer for the server-side code). The benefits, in addition to the services listed above (there are actually many others that could result useful), are the classic ones related to developing on a Cloud PaaS platform: scalability (both horizontal and vertical), availability, lower costs...
I found this guide in the google documentation for the cloud platform.
https://cloud.google.com/developers/articles/high-availability-lamp-stack-on-google-compute-engine
although the files it asks you to download, are not found when the link is clicked?
anyone know where they actually are?
Unfortunately we deprecated this sample application as it was focused on migrating applications around maintenance windows.
Now that we have live migration and transparent maintenance windows, developers no longer need to move components of their application around zones due to impeding maintenance. Additionally, Cloud SQL now supports MySQL wire protocol which significantly reduces the complexities of managing applications for high availability.
In the future we may develop a new application, but it will be greatly simplified since we can offload load balancing to Compute Engine load balancer and persistency to Cloud Datastore and Cloud SQL.
I was involved in couple of cloud computing platform recently.
First of all please note that I am not trying to criticize any platform.
Cloud computing is large area but to make my point simple and understandable. Let me come up with very simple scenario and that is data storage services hosted on the cloud.
If you take any storage service like Amazon EC2, SQL Data Service(SDS), Salesforce.com services.
If you want to consume any of such data storage service platform goal of all such service are same and that is to serve requested data on demand. Without warring about how it store and where it stored and who is maintaining it etc... (all cloud goodies)
Now my area of concern is the way ANSI-SQL regulated platform venders to make sure they follow similar language across all the product can’t they regulate similar concept across
service providers?
Why no such initiatives??
Any thoughts appreciated
It seems to me like you're worried about vendor lock-in with cloud computing. I may be naive but I would normally choose technologies and then go look for cloud vendors that'd be able to deliver these technologies. And if I was aiming for a "write once run anywhere approach" I'd have to select technology that'd make this as realistic as possible.
With the fairly rapid speed of development I really think standardization committees would struggle to keep up. ANSI-SQL has had 20 + years of history. It seems to me like you're requesting for standardization long before we even know what the cloud is up to....
I think that this emerging cloud computing initiative is just too young in order to have standards.
Service providers right now just worry about rushing into the market, rather than interoperability and standards.
Later on, when the situation is more established, some common guidelines may emerge. But there is still a long way to go.
You seem to be asking specifically about cloud storage services, rather than cloud computing in general. So your Amazon example would be S3, not EC2.
I think the field is a little young to be standardising on an API just yet. The services differentiate themselves in ways which rule this out. For example, S3 trades sophistication for scalability/reliability/performance: you can't do a complex SQL LIKE query. You can store and retrieve blobs of data based on a key, and that's about it.
I think as such services become more and more the mainstream way to do things, standards will emerge. Users will want the freedom to switch providers on a whim, move their data around, test against free local storage, etc.
The APIs used are all based on Web Standards already. Making an abstraction layer to make them look the same is fairly trivial.