1.
ifesenko.com

2.
I went to an all night JavaScript
hackathon and by morning we finally
had the build process configured!

3.
Clean
Build
Unit Tests
(NUnit, xUnit,
MSTest)
Test Coverage
Static Analysis SonarQube
Versioning StyleCop
Package
Publish
Package
Restore

4.
Why do I need that?
Why was my VM’s
CPU% so high? Do we
need to throw in more
VMs process this load?
Can you download and
send me the logs next
time this happens?
Who shut down this
database and when?

5.
Record Transmit Analyze Store Delete

6.
Record Transmit Store Delete

7.
Record Delete

8.
“Show me all the error log messages
where the order values is more
than $20,000 or the customer is a VIP”

9.
“Show me all the failed login
attempts for user Igor where
the server name was LoginServer4”

10.
“Show me all the login attempts for
loginServer4 where the database
read time was more than 250ms”

11.
“How many users used the export to
CSV feature of ApplicationX where
the total order value was
less than $100,000”

12.
Semantic Logging is creation of logs
with machine’s consumption in mind

13.
• Be careful
• CDNs fail, but you scripts don’t have to (or you use eCDN)
• Do NOT include files directly from GitHub in PRODUCTION (via
https://rawgit.com/)
• Use Subresource Integrity

14.
• Be careful
• Do NOT cache any of resources/responses for Auth/Authz flow
• Do NOT remove old version of assets when you are deploying new ones

15.
prefetching, preloading, prebrowsing

16.
• Peak CPU utilization
• Allocated and peak RAM usage
• Storage capacity
• Occupancy
• Input/output Operations Per Second (IOPS)
• and more…

17.
Azure Advisor

18.
what size of VM would you create?

19.
your bill
will be paid by someone
else

20.
Does your answer change?

21.
Questions
@ky7m | ifesenko.com | ifesen@softserveinc.com