AzureCAT – Technical Customer Profiles


Last Updated: 5/25/18

Over in this blog post, we mentioned why we're named AzureCAT:

CAT stands for “Customer Advisory Team.” We work with customers who act as feedback Advisors back to our product teams, by working on engagements with those customers and building ground-breaking solutions!

 

While we help customers architect those solutions, we learn a ton in the process! And so we want to share those customer architectures with you. We call these technical customer profiles (TCPs).

This blog lists out the SQLCAT and AzureCAT TCPs. These are customer architectures from engagements led by our CAT and CSA (Cloud Solution Architect) teams. They are journeys into architectural design decisions that led these customers into highly successful solutions.

 

    Service Fabric:

    1. ABBYY - Case Study | Blog
    2. Alaska Airlines - Case Study | Blog
    3. BMW - Case Study | Blog
    4. Citrix - Case Study | Blog
    5. D+H - Blog
    6. Digamore Entertainment - Case Study | Blog
    7. FunRock - Case Study | Blog
    8. Honeywell (new; published on 3/20) - Case Study | Blog
    9. Info Support & Fudura - Case Study | Blog
    10. Mesh Systems - Case Study | Blog
    11. P2ware - Casey Study | Blog
    12. Proactima Solutions - Case Study | Blog
    13. Quorum Business Solutions - Case Study | Blog
    14. Schneider Electric - Case Study | Blog
    15. SiriusIQ (new; published on 4/12) - Case Study | Blog
    16. Societe Generale and Qarnot Computing - Case Study | Blog
    17. TalkTalk TV - Case Study | Blog
    18. Wolters Kluwer - Blog

    Cosmos DB:

    SAP to Azure:

    SQL Server:

    1. BNW Consulting + Large Australian Energy Company
    2. Bwin

     

    All our Technical Case Studies are also featured on Azure.com.

     

    Each customer profile includes the following sections (mostly):

    1. A brief description of the company and their general business
    2. A deeper dive into the product or service that they are developing.
      1. If applicable, a look at the previous architecture of their service.
      2. Any requirements, weaknesses, or obstacles they wanted to fix by re-architecting their solution.
    3. An overview of their new architecture on a given service (such as Service Fabric).
      1. The specifics of how they implemented that architecture.
    4. How that service fits into their other services and technologies used to build their system.
    5. A summary that concludes with the benefits gained from the new architecture.

     

    Leave us a comment if anything is helpful, or if you have a question. Thanks!

    - Ninja Ed

     

    See Also

     

    Azure CAT Guidance

    "Hands-on solutions, with our heads in the Cloud!"

     

    Comments (13)

    1. star wars lego says:

      As I site pоssesѕor I bepieve thhe contᥱnt materіal here
      is rattⅼing wonderful , appreciate it for your haгd work.
      Yoᥙ should keep it up forever! Good Luck.

      1. Thank you, star wars lego.

    2. Bard says:

      Алюминиевый реечный потолок БАРД Нижний Новгород

    3. Nadav says:

      Thanks for sharing the useful learnings!

      1. My pleasure, Nadav. Let me know if you have any questions!

    4. UPDATE: I added two new TCPs… D+H and Wolters Kluwer. Both are in the Service Fabric category.

    5. We added two new customer profiles for the Ignite event: ABBYY and FunRock!

    6. Added the new Alaska Airlines profile!

    7. Added the new technical profile for Societe Generale and Qarnot Computing!

    8. I added the Jet.com TCP!

    Skip to main content