Alternatives to WSO2 logo

Alternatives to WSO2

Talend, Kong, Apigee, Fuse, and Kafka are the most popular alternatives and competitors to WSO2.
83
163
+ 1
0

What is WSO2 and what are its top alternatives?

WSO2 is an open-source integration platform that enables developers to build, integrate, manage, and secure APIs and applications. Key features include support for microservices, cloud-native architecture, and centralized API management. However, some limitations of WSO2 include a steep learning curve due to its complexity and a lack of extensive documentation for beginners.

  1. MuleSoft Anypoint Platform: MuleSoft offers a unified platform for API-led connectivity that enables organizations to connect data, devices, and applications. Key features include a drag-and-drop interface, reusable API fragments, and comprehensive analytics. Pros include a user-friendly interface and a large developer community, while cons include high pricing for enterprise features.

  2. Apigee: Apigee, powered by Google Cloud, provides a full lifecycle API management solution for securely delivering and analyzing APIs. Key features include advanced security controls, traffic management, and analytics dashboards. Pros include seamless integration with Google Cloud services, while cons include limited customization options.

  3. IBM API Connect: IBM API Connect offers a complete API lifecycle management solution, including creating, securing, and managing APIs. Key features include automated API creation, built-in security policies, and advanced analytics. Pros include seamless integration with IBM Cloud services, while cons include a complex setup process.

  4. Azure API Management: Microsoft Azure API Management provides a scalable API gateway for building and managing APIs. Key features include developer portal customization, policy enforcement, and monitoring and analytics. Pros include seamless integration with Azure services, while cons include limited support for non-Microsoft technologies.

  5. TIBCO Cloud Integration: TIBCO offers a cloud-based integration platform that enables organizations to connect applications, data, and APIs. Key features include visual data mapping, real-time monitoring, and hybrid integration capabilities. Pros include a unified platform for data and application integration, while cons include a high price point.

  6. Dell Boomi: Dell Boomi is a cloud-native integration platform that simplifies API design, deployment, and management. Key features include drag-and-drop interface, low-code development, and pre-built connectors. Pros include rapid deployment and scalability, while cons include limited customization options.

  7. Red Hat Integration: Red Hat offers an open-source integration platform that enables organizations to connect applications, data, and devices. Key features include support for microservices architecture, containerization, and API gateways. Pros include robust security features, while cons include a complex setup process.

  8. AWS API Gateway: Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs. Key features include built-in security, traffic management, and API versioning. Pros include seamless integration with AWS services, while cons include high pricing for heavy usage.

  9. Kong: Kong is an open-source API gateway and microservices management layer that enables organizations to create and manage APIs. Key features include request throttling, authentication, and rate limiting. Pros include flexibility and extensibility through plugins, while cons include a steeper learning curve for beginners.

  10. Tyk: Tyk is an open-source API gateway that offers advanced features for API management, analytics, and security. Key features include rate limiting, developer portal, and access control policies. Pros include a robust set of features, while cons include limited enterprise support compared to other solutions.

Top Alternatives to WSO2

  • Talend
    Talend

    It is an open source software integration platform helps you in effortlessly turning data into business insights. It uses native code generation that lets you run your data pipelines seamlessly across all cloud providers and get optimized performance on all platforms. ...

  • Kong
    Kong

    Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform. ...

  • Apigee
    Apigee

    API management, design, analytics, and security are at the heart of modern digital architecture. The Apigee intelligent API platform is a complete solution for moving business to the digital world. ...

  • Fuse
    Fuse

    It is a set of user experience development tools that unify design, prototyping and implementation of high quality, native apps for iOS and Android. ...

  • Kafka
    Kafka

    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design. ...

  • Keycloak
    Keycloak

    It is an Open Source Identity and Access Management For Modern Applications and Services. It adds authentication to applications and secure services with minimum fuss. No need to deal with storing users or authenticating users. It's all available out of the box. ...

  • Okta
    Okta

    Connect all your apps in days, not months, with instant access to thousands of pre-built integrations - even add apps to the network yourself. Integrations are easy to set up, constantly monitored, proactively repaired and handle authentication and provisioning. ...

  • Spring Boot
    Spring Boot

    Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration. ...

WSO2 alternatives & related posts

Talend logo

Talend

150
247
0
A single, unified suite for all integration needs
150
247
+ 1
0
PROS OF TALEND
    Be the first to leave a pro
    CONS OF TALEND
      Be the first to leave a con

      related Talend posts

      Shared insights
      on
      TalendTalendSnapLogicSnapLogic

      SnapLogic Vs Talend: Which one to choose when you have a lot of transformation logic to be used huge volume of data load on everyday basis.

      . better monitor & support . better performance . easy coding

      See more
      Kong logo

      Kong

      634
      1.5K
      139
      Open Source Microservice & API Management Layer
      634
      1.5K
      + 1
      139
      PROS OF KONG
      • 37
        Easy to maintain
      • 32
        Easy to install
      • 26
        Flexible
      • 21
        Great performance
      • 7
        Api blueprint
      • 4
        Custom Plugins
      • 3
        Kubernetes-native
      • 2
        Security
      • 2
        Has a good plugin infrastructure
      • 2
        Agnostic
      • 1
        Load balancing
      • 1
        Documentation is clear
      • 1
        Very customizable
      CONS OF KONG
        Be the first to leave a con

        related Kong posts

        Shared insights
        on
        GrafanaGrafanaKongKongDatadogDatadog

        Hello :) We are using Datadog on Kong to monitor the metrics and analytics.

        We feel that the cost associated with Datadog is high in terms of custom metrics and indexations. So, we planned to find an alternative for Datadog and we are looking into Grafana implementation with kong.

        Will the shift from Datadog to Grafana be a wise move and flawless?

        See more
        Anas MOKDAD
        Shared insights
        on
        KongKongIstioIstio

        As for the new support of service mesh pattern by Kong, I wonder how does it compare to Istio?

        See more
        Apigee logo

        Apigee

        236
        687
        30
        Intelligent and complete API platform
        236
        687
        + 1
        30
        PROS OF APIGEE
        • 12
          Highly scalable and secure API Management Platform
        • 6
          Good documentation
        • 6
          Quick jumpstart
        • 3
          Fast and adjustable caching
        • 3
          Easy to use
        CONS OF APIGEE
        • 11
          Expensive
        • 1
          Doesn't support hybrid natively

        related Apigee posts

        A Luthra
        VP Software Engrg at Reliant · | 3 upvotes · 1M views
        Shared insights
        on
        ApigeeApigeeAmazon API GatewayAmazon API Gateway

        Amazon API Gateway vs Apigee. How do they compare as an API Gateway? What is the equivalent functionality, similarities, and differences moving from Apigee API GW to AWS API GW?

        See more
        Fuse logo

        Fuse

        63
        59
        0
        Mobile interfaces for your IT systems
        63
        59
        + 1
        0
        PROS OF FUSE
          Be the first to leave a pro
          CONS OF FUSE
            Be the first to leave a con

            related Fuse posts

            Kafka logo

            Kafka

            23.3K
            21.8K
            607
            Distributed, fault tolerant, high throughput pub-sub messaging system
            23.3K
            21.8K
            + 1
            607
            PROS OF KAFKA
            • 126
              High-throughput
            • 119
              Distributed
            • 92
              Scalable
            • 86
              High-Performance
            • 66
              Durable
            • 38
              Publish-Subscribe
            • 19
              Simple-to-use
            • 18
              Open source
            • 12
              Written in Scala and java. Runs on JVM
            • 9
              Message broker + Streaming system
            • 4
              KSQL
            • 4
              Avro schema integration
            • 4
              Robust
            • 3
              Suport Multiple clients
            • 2
              Extremely good parallelism constructs
            • 2
              Partioned, replayable log
            • 1
              Simple publisher / multi-subscriber model
            • 1
              Fun
            • 1
              Flexible
            CONS OF KAFKA
            • 32
              Non-Java clients are second-class citizens
            • 29
              Needs Zookeeper
            • 9
              Operational difficulties
            • 5
              Terrible Packaging

            related Kafka posts

            Nick Rockwell
            SVP, Engineering at Fastly · | 46 upvotes · 3.6M views

            When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

            So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

            React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

            Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

            See more
            Ashish Singh
            Tech Lead, Big Data Platform at Pinterest · | 38 upvotes · 3M views

            To provide employees with the critical need of interactive querying, we’ve worked with Presto, an open-source distributed SQL query engine, over the years. Operating Presto at Pinterest’s scale has involved resolving quite a few challenges like, supporting deeply nested and huge thrift schemas, slow/ bad worker detection and remediation, auto-scaling cluster, graceful cluster shutdown and impersonation support for ldap authenticator.

            Our infrastructure is built on top of Amazon EC2 and we leverage Amazon S3 for storing our data. This separates compute and storage layers, and allows multiple compute clusters to share the S3 data.

            We have hundreds of petabytes of data and tens of thousands of Apache Hive tables. Our Presto clusters are comprised of a fleet of 450 r4.8xl EC2 instances. Presto clusters together have over 100 TBs of memory and 14K vcpu cores. Within Pinterest, we have close to more than 1,000 monthly active users (out of total 1,600+ Pinterest employees) using Presto, who run about 400K queries on these clusters per month.

            Each query submitted to Presto cluster is logged to a Kafka topic via Singer. Singer is a logging agent built at Pinterest and we talked about it in a previous post. Each query is logged when it is submitted and when it finishes. When a Presto cluster crashes, we will have query submitted events without corresponding query finished events. These events enable us to capture the effect of cluster crashes over time.

            Each Presto cluster at Pinterest has workers on a mix of dedicated AWS EC2 instances and Kubernetes pods. Kubernetes platform provides us with the capability to add and remove workers from a Presto cluster very quickly. The best-case latency on bringing up a new worker on Kubernetes is less than a minute. However, when the Kubernetes cluster itself is out of resources and needs to scale up, it can take up to ten minutes. Some other advantages of deploying on Kubernetes platform is that our Presto deployment becomes agnostic of cloud vendor, instance types, OS, etc.

            #BigData #AWS #DataScience #DataEngineering

            See more
            Keycloak logo

            Keycloak

            720
            1.3K
            102
            An open source identity and access management solution
            720
            1.3K
            + 1
            102
            PROS OF KEYCLOAK
            • 33
              It's a open source solution
            • 24
              Supports multiple identity provider
            • 17
              OpenID and SAML support
            • 12
              Easy customisation
            • 10
              JSON web token
            • 6
              Maintained by devs at Redhat
            CONS OF KEYCLOAK
            • 7
              Okta
            • 6
              Poor client side documentation
            • 5
              Lack of Code examples for client side

            related Keycloak posts

            Shared insights
            on
            OktaOktaKeycloakKeycloakGitHubGitHub

            Hello,

            I'm trying to implement a solution for this situation:

            There is a restaurant in which users can access RestAPI, using Google, Facebook, GitHub. There is even the possibility to login inside using the SPID authentication. In the first case I was considering Keycloak as a better solution for this case, but then i've read about Okta and its pros.

            I cannot understand reading and searching on Google if SPID authentication is supported by OKTA. Looks like to be, because it should be using SAML, but I haven't found a clear solution.

            See more
            Joshua Dean Küpper
            CEO at Scrayos UG (haftungsbeschränkt) · | 7 upvotes · 838.4K views

            As the access to our global REST-API "Charon" is bound to OAuth2, we use Keycloak inside Quarkus to authenticate and authorize users of our API. It is not possible to perform any un-authenticated requests against this API, so we wanted to make really sure that the authentication/authorization component is absolutely reliable and tested. We found those attributes within Keycloak, so we used it.

            See more
            Okta logo

            Okta

            411
            815
            65
            Enterprise-grade identity management for all your apps, users & devices
            411
            815
            + 1
            65
            PROS OF OKTA
            • 14
              REST API
            • 9
              SAML
            • 5
              OIDC OpenID Connect
            • 5
              Protect B2E, B2B, B2C apps
            • 5
              User Provisioning
            • 5
              Easy LDAP integration
            • 4
              Universal Directory
            • 4
              Tons of Identity Management features
            • 4
              SSO, MFA for cloud, on-prem, custom apps
            • 4
              API Access Management - oAuth2 as a service
            • 3
              Easy Active Directory integration
            • 2
              SWA applications Integration
            • 1
              SOC2
            • 0
              Test
            CONS OF OKTA
            • 5
              Pricing is too high
            • 1
              Okta verify (Multi-factor Authentication)

            related Okta posts

            Shared insights
            on
            OktaOktaKeycloakKeycloakGitHubGitHub

            Hello,

            I'm trying to implement a solution for this situation:

            There is a restaurant in which users can access RestAPI, using Google, Facebook, GitHub. There is even the possibility to login inside using the SPID authentication. In the first case I was considering Keycloak as a better solution for this case, but then i've read about Okta and its pros.

            I cannot understand reading and searching on Google if SPID authentication is supported by OKTA. Looks like to be, because it should be using SAML, but I haven't found a clear solution.

            See more
            Shared insights
            on
            OktaOktaKeycloakKeycloak

            I want some good advice on which one I should prefer. (Keycloak or Okta) Since Keycloak is open source, it will be our first preference, but do we face some limitations with this approach? And since our product is SAAS based and we support the following authentications at present. 1. AT DB level 2. 3rd part IDP providers 3. LDAP/AD...

            See more
            Spring Boot logo

            Spring Boot

            25.6K
            23.3K
            1K
            Create Spring-powered, production-grade applications and services with absolute minimum fuss
            25.6K
            23.3K
            + 1
            1K
            PROS OF SPRING BOOT
            • 149
              Powerful and handy
            • 134
              Easy setup
            • 128
              Java
            • 90
              Spring
            • 85
              Fast
            • 46
              Extensible
            • 37
              Lots of "off the shelf" functionalities
            • 32
              Cloud Solid
            • 26
              Caches well
            • 24
              Productive
            • 24
              Many receipes around for obscure features
            • 23
              Modular
            • 23
              Integrations with most other Java frameworks
            • 22
              Spring ecosystem is great
            • 21
              Auto-configuration
            • 21
              Fast Performance With Microservices
            • 18
              Community
            • 17
              Easy setup, Community Support, Solid for ERP apps
            • 15
              One-stop shop
            • 14
              Easy to parallelize
            • 14
              Cross-platform
            • 13
              Easy setup, good for build erp systems, well documented
            • 13
              Powerful 3rd party libraries and frameworks
            • 12
              Easy setup, Git Integration
            • 5
              It's so easier to start a project on spring
            • 4
              Kotlin
            • 1
              Microservice and Reactive Programming
            • 1
              The ability to integrate with the open source ecosystem
            CONS OF SPRING BOOT
            • 23
              Heavy weight
            • 18
              Annotation ceremony
            • 13
              Java
            • 11
              Many config files needed
            • 5
              Reactive
            • 4
              Excellent tools for cloud hosting, since 5.x
            • 1
              Java 😒😒

            related Spring Boot posts

            Praveen Mooli
            Engineering Manager at Taylor and Francis · | 19 upvotes · 3.9M views

            We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

            To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

            To build #Webapps we decided to use Angular 2 with RxJS

            #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

            See more

            Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

            Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

            See more