Sunday, July 31, 2016
Saturday, July 30, 2016
AWS RDS SQL SERVER with Back up and Restore Option - WOW
https://aws.amazon.com/blogs/aws/amazon-rds-for-sql-server-support-for-native-backuprestore-to-amazon-s3/
http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/SQLServer.Procedural.Importing.html#SQLServer.Procedural.Importing.Native.Using.Restore
https://www.quora.com/What-is-the-fastest-way-to-transfer-200GB-to-AWS
http://s3-accelerate-speedtest.s3-accelerate.amazonaws.com/en/accelerate-speed-comparsion.html
https://www.brentozar.com/archive/2016/07/holy-cow-amazon-rds-sql-server-just-changed-everything/
Schema Conversion
http://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/Welcome.html
Data Migration
http://docs.aws.amazon.com/dms/latest/userguide/CHAP_GettingStarted.html
Tested DMS Service, and that chocked with error no info found
Client
CloudBerry Explorer for Amazon S3 PRO
Api Monitoring
Evaluating few Api monitoring tools, seems Runscope is the best for our needs
http://stackshare.io/runscope
https://www.runscope.com/docs/api-testing/assertions
The scripting ability is what I was looking far
Thursday, July 28, 2016
Load Testing
http://www.c-sharpcorner.com/UploadFile/pandeypradip/load-testing-of-web-api/
https://github.com/Samuel29/NodeStressSuite
https://github.com/jeffbski/bench-rest
https://loader.io/
http://www.telerik.com/campaigns/teststudio/fiddler-powered-load-testing
http://zenprogramming-it.blogspot.it/search/label/RESTful%20Stress
https://strongloop.com/strongblog/monitoring-stress-testing-nodejs-apps/
https://www.npmjs.com/package/loadtest
https://github.com/benschmaus/nodeload
Monday, July 25, 2016
Android,Java
http://jd.benow.ca/
https://github.com/pxb1988/dex2jar
Continous Integration:
https://www.quora.com/Hosted-Continuous-Integration-for-iOS-Apps
Game Framework
http://www.cocos2d-x.org/
Code Deploy
Code Deploy Setup (IAM, EC2)
https://www.youtube.com/watch?v=qZa5JXmsWZshttps://www.youtube.com/watch?v=KzziRHOa5X4
Codeship AWS CodeDeploy integration
D3
SVG
http://www.w3schools.com/svg/default.asp
http://alexandros.resin.io/angular-d3-svg/
https://www.npmjs.com/package/svg2png
https://github.com/ariutta/svg-pan-zoom
https://www.npmjs.com/package/svg2png
Using this for UI components currently:
https://angular-ui.github.io/bootstrap/
UI-Router
http://www.funnyant.com/angularjs-ui-router/
And this for the toolbars / footer:
https://github.com/angular-ui/ui-router/wiki/Multiple-Named-Views
Demo: https://f1lt3r.github.io/angular-ui-router-examples/multi-nested/
Repo: https://github.com/f1lt3r/angular-ui-router-examples/
Build Process
https://github.com/zont/gulp-usemin
https://github.com/taptapship/wiredep
https://github.com/klei/gulp-inject
SqlLite
http://objection-framework.org/
http://blog.tigrangasparian.com/2012/02/09/getting-started-with-sqlite-in-c-part-one/
Install-Package System.Data.SQLite
What makes it difficult to match the standard of MacBooks
Balaji Viswanathan, Product Manager, Teacher.
93.6k Views • Upvoted by Alex Cherry, Systems Administrator with a decade experience integrating Apple and Windows
A decade ago, I was a developer at the Core OS Division at Microsoft and as Apple was rising, these were similar questions that were raised internally. How come Apple is suddenly able to kick-ass while PCs are still fraught with a variety of problems.
Some possible reasons:
Some possible reasons:
- Any software accumulates crap over time. It needs to be periodically refactored. OS X went through a major reset in 1999 and took the decision not to support earlier Mac OS. Given that Apple had so few users back then, it was no big deal. Using the Unix BSD, Apple was able to be much more agile in releasing new versions with better quality. Windows has been burdened with crap running to early 1980s. I have seen many of the code written in mid 1980s in my component and had very little idea of how it worked. I just treated it as a blackbox that just worked [until it didn't]. There have been numerous attempts to reset Windows and significantly refactor stuff but it never happened. Thus, you are running massive amounts of unwanted crap in your PC.
- When you buy a PC, it is very likely to be burdened with bloatware and crapware added by everyone in the supply chain that would reduce your battery life and cause your laptop to heat up [extra computing cycles and memory would cause both]. Apple has a tight control over the entire supply chain - basically no other company touches the Mac after it is manufactured. This means very little crapware to overburden your PC.
- Apple has a much more well defined customer segment - educated, rich and tolerant. Apple could afford to prioritize quality over everything.Dell's and Microsoft's customer could range from the kid in a slum in India to a trader in wall street to a CEO of a Fortune 500 firm. People are using Windows for everything from nuclear reactors to trading terminals to your grandma's desk. This puts a lot of stress on the developers and makes for a variety of complex tradeoffs. Quality is not always the top priority if you have to sell a $250 laptop to a school in subsaharan Africa.
- Apple doesn't have to deal with pesky business users. Enterprises are great - in that they are a stable source of $$. They are the biggest chunk of revenue providers for Microsoft & PC makers. Apple, on the other hand, is predominantly consumer. However, enterprise adds a lot of challenges - such as all the backward compatibility requirements. Business users can be very vocal [as it impacts their workflow and productivity] and that means Microsoft and PC manufacturers have lesser ability to innovate. [Although Apple adoption is fast growing the enterprise, Macbook+iPad new purchases don't even come up to 20% of the market in 2015 - leave alone the existing install base. ]
- Apple is the only major personal computer maker who doesn't have a vast explosion of models. Dell, Lenovo, HP, Toshiba all have a variety of random models and spread themselves too thin. The hardware explosion makes it very hard to test and makes for poor quality hardware running under not so-well tested software.
Testing Frameworks Review
Tools
|
Pros
|
cons
| |
Selenium
| |||
Sikuli
| |||
autoit
| |||
QTP
| |||
Watir
| |||
flex
|
| ||
Selenium : https://www.youtube.com/watch?v=nSjD0HVKaAA
for Magento
JMeter
brew install jmeter --with-plugins
Locust
To Review:
Sunday, July 24, 2016
Continuous Delivery
https://blog.assembla.com/AssemblaBlog/tabid/12618/bid/92411/Continuous-Delivery-vs-Continuous-Deployment-vs-Continuous-Integration-Wait-huh.aspx
The Steps
- Continuous Build
- Continuous Deployment
- Continuous Integration
- Continuous Delivery
Friday, July 22, 2016
Load testing : Calculating the number of concurrent users to test
http://support.loadimpact.com/knowledgebase/articles/265461-calculating-the-number-of-concurrent-users-to-test
Hourly Sessions x Average Session Duration (in seconds) / 3,600
Simultaneous Visitors = Hourly visitors * Average Time Spent on Site (in seconds)
/ 3600
=8000*(27*60)/3600
=3600 cocurrent users persecond for ds
Subscribe to:
Posts (Atom)