|
SInce the start of the crisis, Germany has been stockpiling sausages and cheese – it's the Wurst Käse scenario.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
smart thinking, would make it far more ![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif) able for the natives
pestilence [ pes-tl-uh ns ] noun
1. a deadly or virulent epidemic disease. especially bubonic plague.
2. something that is considered harmful, destructive, or evil.
Synonyms: pest, plague, CCP
|
|
|
|
|
So long as they maintain social distancing and don't kraut to closely together!
In case the beer drinking gets out of hand, they hired a lady and Leder Hosen down the streets to wash away the mess.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
|
It's a funny thing that the Brits complain about German humour. 
|
|
|
|
|
Wait. Germans have humor?
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
Well ... they watch Dinner for One[^] every single Christmas ...
And find it funny each time, apparently.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
We have the same tradition in Norway: This piece has been broadcast every Dec. 23rd since 1980.
The history books tell that in 1992, by a mistake the play started 15 minutes earlier than announced. People who sat down to watch it at the announced time, discovering that it was already over, made furious phone calls to the broadcaster - there were so many complaints that it was set up for a rerun immediately after the last newscast of the night.
|
|
|
|
|
Don't KnockWurst case it could always be Wurst!
Young enough to know I can.
Old enough to know I shouldn't.
Stupid enough to do it anyway!
JaxCoder.com
|
|
|
|
|
At work there is a push to move our web apps to Azure...
Can't say I have done it before hence I don't have an informed opinion...
Although I can't help but wonder.. if you have a read and write database used by almost any page you serve, wouldn't you say both assertion below are true?
- since the DB is read/write you can't spawn multiple copy of it on multiple server
- since this one server is used for all your queries, you can't really scale your website
Hence, I don't see the point in cloudifying many business app, and certainly ours... Any thoughts and feedback?
|
|
|
|
|
Scale-up and scale-out your DB are both options in Azure - the technicality behind it should not bother you, if you are not the maintainer...
As for using Azure... A small bedtime story... We started to use Azure to build or Angular application on every pull request on the Git... We close it every evening and start every morning, as we do not want to pay for hours when noone uses it...
It works perfectly... Except that one day - just after Corona-virus boosted the internet-usage - when we tried to start the machine Azure failed to do so because lack of resources... And that's to prove you that the cloud is only a glorified (partially rightly) hosting plan, that can go very wrong...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
|
It is not about knowing more... But what...
Of course if it is in you time-frame and interest you... Up to you...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
Well someone ask me, "is there any point to migrating to azure" and until proven otherwise I see no reason other than sheer daredevil curiosity...
Anyway, I am paid either way... so
|
|
|
|
|
shiny? I think you forgot shiny.
pestilence [ pes-tl-uh ns ] noun
1. a deadly or virulent epidemic disease. especially bubonic plague.
2. something that is considered harmful, destructive, or evil.
Synonyms: pest, plague, CCP
|
|
|
|
|
We have found it to be cheaper than trying to maintain our own servers and hiring people to keep them updated, patched, running, etc.
Super Lloyd wrote: since the DB is read/write you can't spawn multiple copy of it on multiple server
This is true regardless of cloud or not. If you want multiple machines you can use load balancing. I believe load balancing is actually easier in Azure than doing it manually.
Super Lloyd wrote: the point in cloudifying
For us, we'd rather let someone make sure the servers are patched, up and running, etc, etc. But if that is not important to you than it may not make sense.
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
The db issue you point out with cloud is a main reason micro services have become popular. Each micro service generally has its own db. Designing micro services for an application requires some of the same skills as partitioning a db...you have to break them up such that you minimize the number of db updates required to get your micro services into a consistent state. It can become quite complex and if not done well, can end up in a tangled db mess.
Fortunately, I write internal apps, and have only a few thousand users, so have not had to go the micro service route.
|
|
|
|
|
Scott Serl wrote: It can become quite complex and if not done well, can end up in a tangled db mess.
And it's the Latest Shiny Thing, so it's going to be done incredibly badly 99% of the time ... by students who think a single lecture they spent on FarceBok makes them a consultant. 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
That's OK, they gets the codez on QA.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
Brilliant explanation!
It kills 2 birds with one stone!
- how to make scalable Cloud service!
- what's the deal with this newfangled micro service thing! 
|
|
|
|
|
We have been using Azure for almost 5 years to host a web-based timeclock system for a client. It consists of 2 web apps and 1 database, all azure services. The decision to 'cloudify' instead of self-host (which we normally do) was based on the nature of the application with the most weight on availability. About two years ago, we added another client for the same system/setup. They weren't as demanding as the original client so I was able to keep them on the free plan with a minimum S0 database.
In hindsight, it would have been better and cheaper to have created an Azure VM, hooked it up to a domain name, and hosted the apps from it with the database(s) local. In fact, before the CV hit, I had already scheduled a migration to the new host so that I can save around $100 a month. In addition, the apps perform better and it opens up a lot more options when you have complete control of the hosting environment.
The free plans are nice but have limitations. Our biggest pain was finding a reporting tool that allowed printing and exporting in the Azure environment. The quick and dirty way (still being used) was to host the ssrs reports (in anonymous mode) on our webserver and hook them to the azure sql databases...slow, but it works. I'm looking forward to removing that link from the process and use a proper reporting tool.
As for scaling, once I have everything running on the VM, if I need more horsepower (not likely) then I can bump it up to the next paid level. (currently costing me around 70 usd/month and more than adequate for what I'm doing now) btw, I'm renting a windows server 2016 datacenter with a moderate 8GB of ram. Obviously, you can save money if you go the 'nix route.
"Go forth into the source" - Neal Morse
|
|
|
|
|
Super Lloyd wrote: since the DB is read/write you can't spawn multiple copy of it on multiple serversince this one server is used for all your queries, you can't really scale your website
I agree. These two statements contradict each other. I will go further and say that all client/server architectures suffer the same inherent flaw of not being scalable. Can you make them "scale"? Yes, but it is also true that anything can fly if you give it enough power. Hmmm, I wonder what would happen if Azure one day didn't have enough "power"? Hint: not good. Hint2: study the shipping giant Maersk NotPetya hack in Andy Greenberg's book "Sandworm" chapters 20-28. Hint3: think pandemic, only on 'cloudy thing' computers. Hint4: again, not good.
|
|
|
|
|
The cloud isn't magic. Any of your alarmist scenarios apply to in house hosting also. Except of course that you must then either have already hired and have been paying your in house experts for years to deal with that or do a mad emergency scramble to find a consultant when your servers are taken out. A full service hosting, such as a cloud server, but true of any full service hosting company already has those experts.
|
|
|
|
|
I see your point and agree. However, I don't think I'm being too alarmist. I don't think the Maersk concern would think I am being too alarmist either. But your point still stands. My bias comes from having developed a decentralized software framework that has the potential of solving the scalability and resiliency issues centralized client/server architectures chronically suffer from. From that viewpoint, clouds look very risky indeed and again, the OPs original statements still stand. Decentralized computing resolves the OP's truth statements.
|
|
|
|
|
My preliminary calculations are that the cloud costs the same as if we were to buy all new servers every year. The benefits are automatic scaling as needed, and lack of need to maintain hardware. A drawback is controlling costs. With Amazon, it was impossible. With Azure, it's better, but still not good.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
