Yes, you read it right. I will be at the TechEd 2012 India event (March 21-23, 2012) in Bangalore again and this is one event that is exciting for me every year. This will be the 9th year that I will be presenting here at TechEd India. It is nostalgic and brings fond memories of connecting with each one of you out there.
Just l try to prepare something completely new and interesting every TechEd. In the past 3 years on the SQL Server track I have become the defacto person to deliver a session around Backups and Recovery. This year I will also be at the Architecture Track delivering a session. Tough the specifics of the session will come out soon on the website, I wanted to take a moment to give you a sneak preview of what you can expect coming your way in that track.
Being as part of Microsoft – MTC Team I have had the privilege of meeting a number of customers and solve their technology and architecture problems. Most of them are generic learning and these will be discussed at length in the session. We will touch on some of the basic concepts of performance and scalability in mind. Below are some of the high-level discussions you can expect from the session.
- If you care about speed & scalability, your web service will always check the distributed cache before querying the database.
- If you have to get your answer from your database, make sure to add the answer to your distributed cache concurrently with returning it to the user.
- Don’t ever call your primary database directly. Call one of your horizontally-scaled relational or NoSQL replicas.
- Use download-only replication to create as many read-only replicas as you need. Your replicas can contain complete copies of the primary database or just shards of data as appropriate. (SQL Server 2012 – AlwaysON technologies can help here)
- When sending data up from the clients to your servers, never insert, update, or delete directly against the primary database or the replicas. (think Scale-outs)
- Have your web services drop that data in a queue and let worker processes update the distributed cache and perform those DML operations against the primary database.
- Use peer-to-peer replication to maintain more than one read/write primary database at the top of your hierarchy. This is architecture problem and not a database deployment problem.
- Remember to create and maintain more than one hierarchy in different geographies using the same peer-to-peer replication to provide even more availability, scalability, and performance to your mobile users all around the world.
- Have clear expectation on what works on mobile devices as an functionality. Using plugin frameworks are great, but use them with caution if scalability and performance is needed.
- Your mobile users will be connecting to your service via slow, intermittent, unpredictable wireless data networks so always use small, efficient wire protocols like REST and data serialization like JSON.
So now that you get the drift where we are taking this conversation. Are you excited to be at the session? I will also be at the database track doing some session, but these sessions and I will post what you will expect from those sessions too. BTW, if you are excited with these sessions, there are sessions on Architecture track on Big Data and beyond too – so much to look forward and not to be missed.
Do drop me a line if you will be at the event – will surely make sure to pass an HI :).Share this article
This entry was posted on Monday, February 6th, 2012 at 09:24 and is filed under Personal, Technology. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.