The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I just had an email to say that two items I ordered on Tuesday would be delivered today! (It's 21:19 local time, BTW) That's not bad - I know they are extra busy what with the lockdown, so an extra day isn't too bad at all.
But ... the items were delivered around 7 hours ago ... and they track the drivers to within meters for every delivery, so they normally report delivery in minutes via email.
I do hope they aren't using AWS - that wouldn't look at all good for it's expansion capability, would it?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
Current circumstances aside, Amazon delivery is fairly good, but not as good as they think they are in my opinion.
Delivery slot? That will be between 7am and 10pm. DPD can text me in the morning to provide me with an estimated hour slot for their deliveries, which they have yet to miss. Amazon, how about a 3 hour slot which will help a bit?
"Amazon locker delivery will be made before 9pm". 8:55pm I get a text to say they will not be delivering today, just as I am pulling into the locker location.
...and the number of missed home deliveries (as in they fail to turn up) is countless. Yes, they usually extend prime for an extra month in return, but I have to contact them every time for this.
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.
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
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.
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
Last Visit: 28-Oct-20 12:45 Last Update: 28-Oct-20 12:45