इस एपिसोड के बारे में
When you’re building applications in the cloud, there are knowns, known unknowns, and the unknown unknowns.
You can read documentation, scour blogs, talk to colleagues, and draw on your own experience, but sometimes you just to have to sail off the map and into territory marked “Here there be dragons.”
Or maybe puppies. Hopefully it’s puppies.
Today’s episode looks at how one developer dealt with surprises and unexpected issues that arose as his company built an Orchard-based Content Management System (CMS) application on Azure. The goal was to replace an existing CMS running on premises.
My guest is Jamie Phillips, a Senior Software Development Engineer at SentryOne. During the day he works on Windows, but at night he’s all about Linux.
We discuss issues that the project ran into, including quirks of Azure’s App Service; why the application ran into performance problems and how they fixed it; storage challenges; and how Azure AD, while useful, caused maintenance problems because of password resets.
You can find Jamie on Twitter @phillipsj73, on GitHub as phillipsj, and read his blog at phillipsj.net.
You can read documentation, scour blogs, talk to colleagues, and draw on your own experience, but sometimes you just to have to sail off the map and into territory marked “Here there be dragons.”
Or maybe puppies. Hopefully it’s puppies.
Today’s episode looks at how one developer dealt with surprises and unexpected issues that arose as his company built an Orchard-based Content Management System (CMS) application on Azure. The goal was to replace an existing CMS running on premises.
My guest is Jamie Phillips, a Senior Software Development Engineer at SentryOne. During the day he works on Windows, but at night he’s all about Linux.
We discuss issues that the project ran into, including quirks of Azure’s App Service; why the application ran into performance problems and how they fixed it; storage challenges; and how Azure AD, while useful, caused maintenance problems because of password resets.
You can find Jamie on Twitter @phillipsj73, on GitHub as phillipsj, and read his blog at phillipsj.net.
अंग्रेज़ी
संयुक्त राज्य अमरीका
अनुलिपि 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
पिछले एपिसोड्स खोजें
Packet Pushers - Community Show के पिछले एपिसोड खोजें।
इस पॉडकास्ट के अन्य एपिसोड
Welcome to the inaugural episode of Day Two Cloud, a new podcast on the Packet Pushers network.
For new listeners–a.k.a everyone since this is the first episode–here’s a little background on what we’re going to cover on the podcast.
There have been countless articles, market…
Welcome to the second episode of Day Two Cloud. This podcast is a frank discussion of what happens when cloud stops being polite and starts getting real.
The promise of the public cloud is both tantalizing and frightening. There’s the promise of moving all your infrastructure to the cloud an…
It’s the end of the month. Your new shiny application has been running the cloud. Customers are happy, the performance seems great. What could possibly go wrong?
Did I mention it’s the end of the month? You know what comes at the end of the month? Your bill. And just like sticking a fork in a…
Today’s Day Two Cloud episode is all about the perceptions and realities of building a startup in the cloud era. My guest Adam Bertram shares his experiences launching an online learning company called TechSnips.
Entrepreneurs can choose a variety of ready-made Web and cloud tools to launch a site …
Automation is awesome! You build your intricate scripts and configuration files. You deploy out your infrastructure and applications. And then celebrate, because your job is done.
Except there’s going to come a day when business requirements change, your infrastructure doesn’t behave t…
अस्वीकरण: इस पृष्ठ पर एम्बेडेड पॉडकास्ट और कलाकृति Packet Pushers Interactive LLC से हैं, जो इसके मालिक की संपत्ति है और Listen Notes, Inc. से संबद्ध या समर्थित नहीं है।
संपादित करें
पॉडकास्ट डेटाबेस को अपडेटेड रखने में मदद के लिए धन्यवाद।
