Alternatives to Microsoft SSRS logo

Alternatives to Microsoft SSRS

Tableau, Power BI, Metabase, Metabase, and Looker are the most popular alternatives and competitors to Microsoft SSRS.
43
41
+ 1
0

What is Microsoft SSRS and what are its top alternatives?

It provides a set of on-premises tools and services that create, deploy, and manage mobile and paginated reports.
Microsoft SSRS is a tool in the Business Intelligence category of a tech stack.

Top Alternatives of Microsoft SSRS

Microsoft SSRS alternatives & related posts

Tableau logo

Tableau

349
290
0
349
290
+ 1
0
Tableau helps people see and understand data.
    Be the first to leave a pro
    Tableau logo
    Tableau
    VS
    Microsoft SSRS logo
    Microsoft SSRS
    Power BI logo

    Power BI

    125
    121
    0
    125
    121
    + 1
    0
    A business analytics service
      Be the first to leave a pro
      Power BI logo
      Power BI
      VS
      Microsoft SSRS logo
      Microsoft SSRS
      Looker logo

      Looker

      198
      160
      9
      198
      160
      + 1
      9
      Pioneering the next generation of BI, data discovery & data analytics
      Looker logo
      Looker
      VS
      Microsoft SSRS logo
      Microsoft SSRS
      Data Studio logo

      Data Studio

      192
      162
      0
      192
      162
      + 1
      0
      Your data is powerful. Use it
        Be the first to leave a pro
        Data Studio logo
        Data Studio
        VS
        Microsoft SSRS logo
        Microsoft SSRS
        Redash logo

        Redash

        168
        170
        5
        168
        170
        + 1
        5
        Easily query an existing database, share the dataset and visualize it in different ways
        Redash logo
        Redash
        VS
        Microsoft SSRS logo
        Microsoft SSRS

        related Superset posts

        Julien DeFrance
        Julien DeFrance
        Principal Software Engineer at Tophatter | 16 upvotes 1.3M views
        atSmartZipSmartZip
        Rails
        Rails
        Rails API
        Rails API
        AWS Elastic Beanstalk
        AWS Elastic Beanstalk
        Capistrano
        Capistrano
        Docker
        Docker
        Amazon S3
        Amazon S3
        Amazon RDS
        Amazon RDS
        MySQL
        MySQL
        Amazon RDS for Aurora
        Amazon RDS for Aurora
        Amazon ElastiCache
        Amazon ElastiCache
        Memcached
        Memcached
        Amazon CloudFront
        Amazon CloudFront
        Segment
        Segment
        Zapier
        Zapier
        Amazon Redshift
        Amazon Redshift
        Amazon Quicksight
        Amazon Quicksight
        Superset
        Superset
        Elasticsearch
        Elasticsearch
        Amazon Elasticsearch Service
        Amazon Elasticsearch Service
        New Relic
        New Relic
        AWS Lambda
        AWS Lambda
        Node.js
        Node.js
        Ruby
        Ruby
        Amazon DynamoDB
        Amazon DynamoDB
        Algolia
        Algolia

        Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

        I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

        For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

        Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

        Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

        Future improvements / technology decisions included:

        Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

        As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

        One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

        See more