Friday, July 24, 2020
What was my Wifi password?
netsh wlan show profile
This will show the known profiles. Copy the name of any profile you need to know its password.
Then call the next command to see the password in clear text:
netsh wlan show profile <name> key=clear
What is my IP-number in Azure
It is pretty simple when you do this on your laptop where you can open up a browser and find your outbound ip-number in Google. When you run your request within an Azure Web App which is running on an ASP, you might want to open up a console in Azure Portal and use the following PowerShell command:
(Get-AzWebApp -ResourceGroup <group_name> -name <app_name>).OutboundIpAddresses
See also: find-outbound-ips
Tuesday, June 30, 2020
How to Ping in Azure Console
Tools
You can use nameresolver to check the hostnames that your app depends on. This way you can test if you have anything misconfigured with your DNS or perhaps don't have access to your DNS server. You can see the DNS server that your app uses in the console by looking at the environmental variables WEBSITE_DNS_SERVER and WEBSITE_DNS_ALT_SERVER.
You can use the next tool to test for TCP connectivity to a host and port combination. This tool is called tcpping and the syntax is:
tcpping.exe hostname [optional: port]
The tcpping utility tells you if you can reach a specific host and port. It can show success only if there's an application listening at the host and port combination, and there's network access from your app to the specified host and port.
Additional debug steps include:
Connect to a VM in your virtual network and attempt to reach your resource host:port from there. To test for TCP access, use the PowerShell command test-netconnection. The syntax is:
1test-netconnection hostname [optional: -Port]Bring up an application on a VM and test access to that host and port from the console from your app by using tcpping.
Thursday, May 14, 2020
Think before going Microservices
The goal of microservices is to sufficiently decompose the application in order to facilitate agile application development and deployment.
The following is based on the book Microservices from Design to Deployment from NGINX. My goal is to know the difficaulties that this inevitable is bringing with in order to be prepared for.
The Drawbacks of Microservices
One drawback is the name itself. The term microservice places excessive emphasis on service size. While small services are preferable, it’s important to remember that small services are a means to an end, and not the primary goal.
Another major drawback of microservices is the complexity that arises from the fact that a microservices application is a distributed system. Developers need to choose and implement an inter-process communication mechanism based on either messaging or RPC. Moreover, they must also write code to handle partial failure, since the destination of a request might be slow or unavailable.
Another challenge with microservices is the partitioned database architecture. Using distributed transactions is usually not an option, and not only because of the CAP theorem. They simply are not supported by many of today’s highly scalable NoSQL databases and messaging brokers. You end up having to use an eventual consistency-based approach, which is more challenging for developers.
Testing a microservices application is also much more complex. A simple test class for a service
would need to launch that service and any services that it depends upon, or at least configure stubs for those services.Another major challenge with the Microservices Architecture pattern is implementing
changes that span multiple services. Fortunately, most changes typically impact only
one service; multi-service changes that require coordination are relatively rare.Deploying a microservices-based application is also much more complex.
Each service will have multiple runtime instances. That’s many more moving parts that
need to be configured, deployed, scaled, and monitored. In addition, you will also need to
implement a service discovery mechanism that enables a service to discover the locations
(hosts and ports) of any other services it needs to communicate with.
Sunday, June 24, 2018
Writing That Works
- The foundations of effective business writing are simplicity and accuracy.
- emails:
- subjects are adequate
- use positive tone
- get to the point quickly and write only what's relevant
- etiquette is key
- be explicit about your questions and requests
- well-structured and focused presentations and speeches
- engage your audience
- finish with small memorable notes
- use titles that builds anticipation
- Drive people to action with clear plan and reports
- purpose statement
- facts
- recommendations
- purpose of the report should be clear and interesting
- Speak to your reader's desire and concerns
- State what you want and offer your reasoning after the facts
- demonstrate your competence with background information
- grab reader's attention
- Write a summary in bold
- Edit and format your final product
- cut out anything you think is not essential
- is the order correct
- fact check
- give yourself enough time between drafts, and have another person review
- format for smooth and appealing experience
How to: Write documentation
Questions to ask:
- Does the document fulfill its purpose?
- Is anything missing?
- Can anything be taken out?
- What questions will the reader have? And answer them.
- Is the writing easy to understand?
Also Check:
- Sentence and paragraph structure
- Grammar
- Word choice
- Spelling
Monday, February 20, 2017
Force HTTPS Rule
<system.webServer> <rewrite> <rules> <rule name="Force HTTPS" enabled="true"> <match url="(.*)" ignoreCase="true"/> <conditions> <add input="{HTTPS}" pattern="off"/> </conditions> </rule> </rules> </rewrite></system.webServer>