Recomendados
Más contenido relacionado
Destacado
Destacado (18)
Similar a Developing Cloud Coffee Infrastructure
Similar a Developing Cloud Coffee Infrastructure (20)
Último
Último (20)
Developing Cloud Coffee Infrastructure
- 1. Cloud Coffee Developing in the clouds… Dominic Green Cloud Consultant www.domgreen.com @domgreen dominic.green@microsoft.com
- 3. Eye On Earth … head in the clouds
- 4. Cloud bursting with RiskMetrics
- 5. Hi, can I get your order started...
- 9. storage within the cloud
- 12. ISerializable
- 15. idemptoency
- 17. poison messages
- 21. What's going on at Cloud Coffee?
- 23. debugging in the cloud
- 24. WADLogsTable
- 26. I’m still here…
- 27. Infrastructure of a coffee shop
- 28. it’s all about the money
- 29. … … $
- 30. make use of the cloud
- 32. cache cache
- 35. Try before you buy…
- 36. testing in the wild
- 38. scale testing
- 40. unit … testing?
- 41. j 3 121
- 42. Scale Fast, Fail Fast
- 43. many hands make light work
- 45. thinking in “scale units”
- 49. need more … bandwidth
- 50. Building shops…
- 53. Autobots, transform and roll out!
- 56. Thank you!| | Questions? Dominic Green Cloud Consultant www.domgreen.com @domgreen dominic.green@microsoft.com
Notas del editor
- Different types of storage - queue - blob - table
- Azure Diagnostics logs locally firstIf you really want to use debugging in the cloud and have the money use the service bus
- Cloud computing and the utility model leading to lower priceArchitects / devs now have to start considering the cost of azureJumping outside of the datacentre costs moneyOriginally designed to use the service bus – moved to interrole
- Use the cloud as early into the development cycle as possiable - subtle differences in the way the dev fabric and the real cloud works - certifices are also a massive problem
- Using memcached in azureVelocity will be in the future, hopefully will make cloud caching easy
- Contain your cloudKeep from spreading around your applicationMuch like using a DALSingle point of contact for all your infrastructure needs
- Multiple accounts on azure (can have dev test qa) - allows testing in the real environment no surprises here
- Problem with testing out to large scaleDOS attacks assumed by cloudWill have to make the requests from within the cloud to get around thisNumber of tools currently being developed internally at MS
- API is not testableNo interfaces (no mocking)Official line is that you should run in the fabric would add a lot of overhead to your build fileTime taken to spin this up added to running testsNeed to basically abstract all the api / libraryUnit testing in the cloud possibilities