Igeometry Podcast

Thank you so much guys for a great year! I love you. -Hussein 2018 was a great year:    Created, edited and posted 120 software engineering youtube videos with over 1.1 Million impressions   Published 75 podcasts with over 8k plays    Self Published a new GIS book   Published two programming online courses  #hustle --- Support this podcast: https://anchor.fm/hnasr/support

This is the final episode of 2018. We will discuss the difference between Availability vs Scalability in software services. Availability What does it mean for my software to be available?  software, service, application is designed in way so it can be available to consumers despite situation  Will your service be available if Host Failure Maintenance  Upgrading Security updates Available doesn’t necessarily mean performant. Scalability What does it mean for my software to be scalable?  The ability for the software to handle the increase of workload or data growth Assume photo sharing app, retrieving 1 photo with details. If in normal conditions you service can serve 100 requests per minute, will doubling resources double the output?u If the volume of data increases will your query still perform? A software is scalable when it is designed in a way so that adding more resources will handle more users   --- Support this podcast: https://anchor.fm/hnasr/supp

In this episode we discuss the concept of subtypes in the geodatabase, subtype layers and much more! --- Support this podcast: https://anchor.fm/hnasr/support

In this episode we discuss the difference between authentication and authorization. --- Support this podcast: https://anchor.fm/hnasr/support

Hussein's Courses

In this episode we discuss the ArcGIS scripting language Arcade. New to GIS? Checkout my books and courses here https://husseinnasser.com/books --- Send in a voice message: https://anchor.fm/hnasr/message

We discuss the difference between short and long transactions in the geodatabase --- Send in a voice message: https://anchor.fm/hnasr/message

We discuss consistency in this episode --- Support this podcast: https://anchor.fm/hnasr/support

In this episode I talk about how the feature service came to be. From local shape files through the enterprise geodatabase to the beautiful HTTP protocol services. Https://husseinnasser.com --- Support this podcast: https://anchor.fm/hnasr/support

Hussein's Courses

In this episode I explain the backend development, its history, how it came into existence and where it is going. I also share with you my latest online course Python on the Backend. http://www.husseinnasser.com/courses --- Support this podcast: https://anchor.fm/hnasr/support

We discuss the HTTP protocol and explain its elegance and how it is powering the microservices architecture. --- Support this podcast: https://anchor.fm/hnasr/support

Happy Thanksgiving! --- Support this podcast: https://anchor.fm/hnasr/support

Hussein's Courses

In this episode we discuss the difference between the HTTP client pull, server push and the long poll also known as #HTTP ASYNCHRONOUS polling. --- Support this podcast: https://anchor.fm/hnasr/support

As a software engineer, I like to reverse engineer applications and see how it was made. This episode we discuss how YouTube handles audio vs video streaming. When you minimize the app, --- Support this podcast: https://anchor.fm/hnasr/support

Port 6080 is interesting, we talk little bit about it in this episode. --- Support this podcast: https://anchor.fm/hnasr/support

If you go to the geoprocessing service in Manager you might have noticed that there is an option to run asynchronously. In this episode we explain when you might want to do this! --- Send in a voice message: https://anchor.fm/hnasr/message

Sde intercept Any operation performed on ArcGIS ends up eventually to the geodatabase as a set of one or more queries. A “zoom-in” or pan operation translates to multiple queries to the underlying geodatabase. SDE intercepts always you to intercept and take a look at those queries to diagnose slow operations in your enterprise geodatabase. It also helps pinpoint where the bottle neck is and how can you optimize your app or geodatabase. https://support.esri.com/en/technical-article/000010355 --- Send in a voice message: https://anchor.fm/hnasr/message

Most of the time a Load balancer is a reverse proxy but a reverse proxy is not necessary a load balancer. Reverse proxy takes a request from client and forward it to “a server” doesn’t care of the server is overloaded or down or not just forwards it. Load balancer stores state about each server behind it, how overloaded each server is, and what server is down, and smartly forward request to a server to balance the load across all the group. So a load balancer is a special case of a reverse proxy but smarter! --- Support this podcast: https://anchor.fm/hnasr/support