It appears that one of the latest hot buzzwords is SaaS (Software as a
Service). From what I can tell, this looks like nothing more than rebranding
of the old ASP model, which fell out of favor. Am I correct, or is there
really something new and interesting here?
15  1219 
Bill Fuller wrote:
It appears that one of the latest hot buzzwords is SaaS (Software as a
Service). From what I can tell, this looks like nothing more than rebranding
of the old ASP model, which fell out of favor. Am I correct, or is there
really something new and interesting here?
Whatever there is, it's not C#. Or .NET, even. Try a more general ng. (I
don't know which ones specialize in buzzwords.)
--
J. http://symbolsprose.blogspot.com
Actually, it came up in discussions on how to deploy a multitier C# Winforms
app.
"Jeroen Mostert" <jm******@xs4all.nlwrote in message
news:48***********************@news.xs4all.nl...
Bill Fuller wrote:
>It appears that one of the latest hot buzzwords is SaaS (Software as a
Service). From what I can tell, this looks like nothing more than
rebranding of the old ASP model, which fell out of favor. Am I correct,
or is there really something new and interesting here?
Whatever there is, it's not C#. Or .NET, even. Try a more general ng. (I
don't know which ones specialize in buzzwords.)
--
J.
http://symbolsprose.blogspot.com
Software as a Service is a logical concept of breaking out your
"applications" into reusable parts. It is similar to n-tier development,
which was popular with traditional ASP, but we also use n-tiers with ASP.NET
applications, Silverlight applications, etc.
When you treat software as a service, you group like concerns and, if
necessary, add a service layer so they can be consumed outside of library
calls. WHen you think this way, you can have completely different types of
applications accessing the same bits, as you are thinking in terms of
delivering the goods for a particular requirement no matter who desires it.
There really is nothing new here.
But, it does go contrary to the way the typical developer operates, which is
from database to UI or UI to database, charting a path, not for reuse, but
from point A to point Z. If we are lucky, this developer will one day
refactor for reuse, but it is more likely he will build the same logic into
his next application rather than reuse bits. If he were thinking as the
output of the classes he was building as products, he can see how this
particular bit would service other applications or services.
Hope that is clear.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog http://gregorybeamer.spaces.live.com/lists/feed.rss
or just read it: http://gregorybeamer.spaces.live.com/
*************************************************
| Think outside the box!
|
*************************************************
"Bill Fuller" <so*****@nospam.comwrote in message
news:Om**************@TK2MSFTNGP06.phx.gbl...
It appears that one of the latest hot buzzwords is SaaS (Software as a
Service). From what I can tell, this looks like nothing more than
rebranding of the old ASP model, which fell out of favor. Am I correct, or
is there really something new and interesting here?
Bill Fuller wrote:
Actually, it came up in discussions on how to deploy a multitier C# Winforms
app.
Yes, I see how that makes it a C# question.
This group isn't a stickler for topicality and your question's already been
picked up, so no point in belaboring the obvious (and annoying), but still.
--
J.
Hmmmm... Interesting. We have designed our solution as a cluster of
specialized WCF modules in a 5-tier logical architecture based upon Rocky's
CSLA framework, so it sounds like we can hype the app using this new
marketing.
Thanks for your feedback. It was helpful.
"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamMwrote in
message news:O2**************@TK2MSFTNGP03.phx.gbl...
Software as a Service is a logical concept of breaking out your
"applications" into reusable parts. It is similar to n-tier development,
which was popular with traditional ASP, but we also use n-tiers with
ASP.NET applications, Silverlight applications, etc.
When you treat software as a service, you group like concerns and, if
necessary, add a service layer so they can be consumed outside of library
calls. WHen you think this way, you can have completely different types of
applications accessing the same bits, as you are thinking in terms of
delivering the goods for a particular requirement no matter who desires
it.
There really is nothing new here.
But, it does go contrary to the way the typical developer operates, which
is from database to UI or UI to database, charting a path, not for reuse,
but from point A to point Z. If we are lucky, this developer will one day
refactor for reuse, but it is more likely he will build the same logic
into his next application rather than reuse bits. If he were thinking as
the output of the classes he was building as products, he can see how this
particular bit would service other applications or services.
Hope that is clear.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss
or just read it:
http://gregorybeamer.spaces.live.com/
*************************************************
| Think outside the box! |
*************************************************
"Bill Fuller" <so*****@nospam.comwrote in message
news:Om**************@TK2MSFTNGP06.phx.gbl...
>It appears that one of the latest hot buzzwords is SaaS (Software as a
Service). From what I can tell, this looks like nothing more than
rebranding of the old ASP model, which fell out of favor. Am I correct,
or is there really something new and interesting here?
Cowboy (Gregory A. Beamer) wrote:
Software as a Service is a logical concept of breaking out your
"applications" into reusable parts. It is similar to n-tier development,
which was popular with traditional ASP, but we also use n-tiers with ASP.NET
applications, Silverlight applications, etc.
When you treat software as a service, you group like concerns and, if
necessary, add a service layer so they can be consumed outside of library
calls. WHen you think this way, you can have completely different types of
applications accessing the same bits, as you are thinking in terms of
delivering the goods for a particular requirement no matter who desires it.
I think what you have described is SOA not SaaS.
Arne
Bill Fuller wrote:
Hmmmm... Interesting. We have designed our solution as a cluster of
specialized WCF modules in a 5-tier logical architecture based upon Rocky's
CSLA framework, so it sounds like we can hype the app using this new
marketing.
No.
You may be able to market it as a SOA architecture.
But to make is SaaS you will need to deliver it to your customers
as a subscription service over the internet instead of selling
them software to run on their own systems.
Arne
Bill Fuller wrote:
It appears that one of the latest hot buzzwords is SaaS (Software as a
Service). From what I can tell, this looks like nothing more than rebranding
of the old ASP model, which fell out of favor. Am I correct, or is there
really something new and interesting here?
Same.
Arne
Actually, it is a hybred. The primary business logic is built into
mobile/anchored business objects from the central application tier. WinForm
is primarly for UI robustness. Altough we provide this as a ClickOnce ERP
app, it is not a requirement and the service can, in principle, be accessed
via WCF for M2M processing, integrating iinto another app, etc.
"Arne Vajhøj" <ar**@vajhoej.dkwrote in message
news:48***********************@news.sunsite.dk...
Bill Fuller wrote:
>Hmmmm... Interesting. We have designed our solution as a cluster of
specialized WCF modules in a 5-tier logical architecture based upon
Rocky's CSLA framework, so it sounds like we can hype the app using this
new marketing.
No.
You may be able to market it as a SOA architecture.
But to make is SaaS you will need to deliver it to your customers
as a subscription service over the internet instead of selling
them software to run on their own systems.
Arne
Bill Fuller wrote:
Actually, it is a hybred. The primary business logic is built into
mobile/anchored business objects from the central application tier. WinForm
is primarly for UI robustness. Altough we provide this as a ClickOnce ERP
app, it is not a requirement and the service can, in principle, be accessed
via WCF for M2M processing, integrating iinto another app, etc.
Maybe you can call it S+S !
:-)
Arne
If you want to use it as a marketing ploy, go for it. :-)
Yes, a bit humorous, but there is really not a lot in software that is NEW,
at least not underneath the hood. The observation that this was the ASP
model was correct, in some ways. Separation of concerns was important in
both.
In reality, much of the SOA SAAS BS (I love acronyms) is just a "new" way of
looking at two old concepts:
1. Process boundaries
2. Separation of concerns
By thinking as a service, you work towards reuse up front, separating
concerns not only on vertical tiers, but horizontal tiers, as well.You are
creating boxes. How you link them (process boundaries: library calls,
service interfaces, etc.) is dependent on what you need at the time, but it
shoudl be easy to switch the type of boundary (library call to service call,
for example) without retooling the logic. That is SAAS in a nutshell.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog http://gregorybeamer.spaces.live.com/lists/feed.rss
or just read it: http://gregorybeamer.spaces.live.com/
*************************************************
| Think outside the box!
|
*************************************************
"Bill Fuller" <so*****@nospam.comwrote in message
news:Oz**************@TK2MSFTNGP05.phx.gbl...
Hmmmm... Interesting. We have designed our solution as a cluster of
specialized WCF modules in a 5-tier logical architecture based upon
Rocky's CSLA framework, so it sounds like we can hype the app using this
new marketing.
Thanks for your feedback. It was helpful.
"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamMwrote in
message news:O2**************@TK2MSFTNGP03.phx.gbl...
>Software as a Service is a logical concept of breaking out your
"applications" into reusable parts. It is similar to n-tier development,
which was popular with traditional ASP, but we also use n-tiers with
ASP.NET applications, Silverlight applications, etc.
When you treat software as a service, you group like concerns and, if
necessary, add a service layer so they can be consumed outside of library
calls. WHen you think this way, you can have completely different types
of applications accessing the same bits, as you are thinking in terms of
delivering the goods for a particular requirement no matter who desires
it.
There really is nothing new here.
But, it does go contrary to the way the typical developer operates, which
is from database to UI or UI to database, charting a path, not for reuse,
but from point A to point Z. If we are lucky, this developer will one day
refactor for reuse, but it is more likely he will build the same logic
into his next application rather than reuse bits. If he were thinking as
the output of the classes he was building as products, he can see how
this particular bit would service other applications or services.
Hope that is clear.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss
or just read it:
http://gregorybeamer.spaces.live.com/
*********************************************** **
| Think outside the box! |
*********************************************** **
"Bill Fuller" <so*****@nospam.comwrote in message
news:Om**************@TK2MSFTNGP06.phx.gbl...
>>It appears that one of the latest hot buzzwords is SaaS (Software as a
Service). From what I can tell, this looks like nothing more than
rebranding of the old ASP model, which fell out of favor. Am I correct,
or is there really something new and interesting here?
SAAS may, in marketing terms, require selling as a service, but underneath
the hood, if the separation of concerns are there and the ability to offer
it is there, he is already in SAAS land, sans the marketing BS. :-)
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog http://gregorybeamer.spaces.live.com/lists/feed.rss
or just read it: http://gregorybeamer.spaces.live.com/
*************************************************
| Think outside the box!
|
*************************************************
"Arne Vajhøj" <ar**@vajhoej.dkwrote in message
news:48***********************@news.sunsite.dk...
Bill Fuller wrote:
>Hmmmm... Interesting. We have designed our solution as a cluster of
specialized WCF modules in a 5-tier logical architecture based upon
Rocky's CSLA framework, so it sounds like we can hype the app using this
new marketing.
No.
You may be able to market it as a SOA architecture.
But to make is SaaS you will need to deliver it to your customers
as a subscription service over the internet instead of selling
them software to run on their own systems.
Arne
There is really not much to SAAS that is not SOA, except that someone has
added a new marketing term to clarify best practices in software
architecture. And, there is not too much to SOA, other than forcing proper
grouping of classes and a service boundary, between SOA and n-tier
applications. And, there is not much difference from n-tier (DNA) to
properly refactored functional applications, other than organization of bits
into libaries.
BTW, this is not a new observation:
Ecclesiastes 1:9
What has been will be again, what has been done will be done again; there is
nothing new under the sun.
*big grin*
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog http://gregorybeamer.spaces.live.com/lists/feed.rss
or just read it: http://gregorybeamer.spaces.live.com/
*************************************************
| Think outside the box!
|
*************************************************
"Arne Vajhøj" <ar**@vajhoej.dkwrote in message
news:48***********************@news.sunsite.dk...
Cowboy (Gregory A. Beamer) wrote:
>Software as a Service is a logical concept of breaking out your
"applications" into reusable parts. It is similar to n-tier development,
which was popular with traditional ASP, but we also use n-tiers with
ASP.NET applications, Silverlight applications, etc.
When you treat software as a service, you group like concerns and, if
necessary, add a service layer so they can be consumed outside of library
calls. WHen you think this way, you can have completely different types
of applications accessing the same bits, as you are thinking in terms of
delivering the goods for a particular requirement no matter who desires
it.
I think what you have described is SOA not SaaS.
Arne
Cowboy (Gregory A. Beamer) wrote:
There is really not much to SAAS that is not SOA, except that someone has
added a new marketing term to clarify best practices in software
architecture.
SOA is an architecture.
SaaS is a business model.
SOA is multiple system interfaces.
SaaS is one human or one system interface.
In fact most of the most known SaaS solutions are with human
interfaces not system interfaces.
SOA and SaaS are completely orthogonal.
Arne
Cowboy (Gregory A. Beamer) wrote:
SAAS may, in marketing terms, require selling as a service, but underneath
the hood, if the separation of concerns are there and the ability to offer
it is there, he is already in SAAS land, sans the marketing BS. :-)
Not really.
I am not in the tomato business even though I could sell
tomatos. Because I do not sell tomatos.
You are in the SaaS business if you sell software as a service
not if you could but does not.
Arne This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Dave Anderson |
last post by:
Last September, some of us engaged in a discussion of freeing resources in
ASP scripts written in JScript. It can be seen here:
http://tinyurl.com/2flzt
I recently read Eric Lippert's article on...
|
by: BadPony |
last post by:
Anyone using Peoplesoft on a Federated UDB
(shared nothing)Environment on Open System Platforms?
Preferably AIX, but any war stories would be good.
TEA
EB-C
|
by: JohnZing |
last post by:
hi
if i have IsAdmin=True or IsAdmin=False why
(IsAdmin = Nothing) is True???
i have
function test(byval IsAdmin as boolean)
If Not (IsAdmin = Nothing) Then
End if
|
by: Shane Saunders |
last post by:
I have a menu option that loads a form and displays infomation. if you go to
main form and try to load something else from that same menu, it does a
check to see if the form in exist and then...
|
by: academic |
last post by:
When I declare a reference variable I initialize it to Nothing.
Now I'm wondering if that best for String variables - is "" better?
With Nothing I assume no memory is set aside nor GC'ed
But...
|
by: Mike Cain |
last post by:
Hi all! I'm looking to offer a software product using the SaaS model. This
of course will require that I build a web site where customers can sign up,
log in, manage their membership and billing...
|
by: DippyDog |
last post by:
This is an old old post that I'm referencing regarding what happens
when you set an integer variable to Nothing. It gets set to zero, not
"Nothing."
...
|
by: anaz |
last post by:
Hi all,
I recently moved south to Bangalore and I am working for a large
software integrator. My project team is working on a project that
applies TOGAF to SOA. Are you able to point me to...
|
by: =?Utf-8?B?Tkg=?= |
last post by:
Hi,
I would to learn how to build multi-tenant saas applications using asp.net
and sql server. Besides LitwareHR (microsoft example) are there other
resources, books, blogs or any other good...
|
by: isladogs |
last post by:
The next Access Europe meeting will be on Wednesday 4 Oct 2023 starting at 18:00 UK time (6PM UTC+1) and finishing at about 19:15 (7.15PM)
The start time is equivalent to 19:00 (7PM) in Central...
|
by: giovanniandrean |
last post by:
The energy model is structured as follows and uses excel sheets to give input data:
1-Utility.py contains all the functions needed to calculate the variables and other minor things (mentions...
|
by: NeoPa |
last post by:
Hello everyone.
I find myself stuck trying to find the VBA way to get Access to create a PDF of the currently-selected (and open) object (Form or Report).
I know it can be done by selecting :...
|
by: NeoPa |
last post by:
Introduction
For this article I'll be using a very simple database which has Form (clsForm) & Report (clsReport) classes that simply handle making the calling Form invisible until the Form, or all...
|
by: Teri B |
last post by:
Hi, I have created a sub-form Roles. In my course form the user selects the roles assigned to the course.
0ne-to-many. One course many roles.
Then I created a report based on the Course form and...
|
by: isladogs |
last post by:
The next Access Europe meeting will be on Wednesday 1 Nov 2023 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM)
Please note that the UK and Europe revert to winter time on...
|
by: NeoPa |
last post by:
Introduction
For this article I'll be focusing on the Report (clsReport) class. This simply handles making the calling Form invisible until all of the Reports opened by it have been closed, when it...
|
by: isladogs |
last post by:
The next online meeting of the Access Europe User Group will be on Wednesday 6 Dec 2023 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM).
In this month's session, Mike...
|
by: SueHopson |
last post by:
Hi All,
I'm trying to create a single code (run off a button that calls the Private Sub) for our parts list report that will allow the user to filter by either/both PartVendor and PartType. On...
| |
