SwaggerHub for AWS

Positive

We still use SwaggerHub , but we did not change much in the way we are using it, meaning just limited functionality.

For us, SwaggerHub  serves as a central place to publish the documentation for our API, and we stick with it because we built infrastructure around it to automatically upload the specification. Because of that small ecosystem we built, it was easy for us to keep it going. If we were to move to a different platform, it would cost us quite an important effort, and we did not want to do that. SwaggerHub is there and working for us, and we did not look for alternatives; I am sure there will be others, but we simply did not want to spend engineering time on it.

API documentation is a very simple use case we have, and it is just enough for now. We basically put the APIs there and just use the rendering they have.

As a SaaS product, SwaggerHub does not require us to do deployment; they manage the whole deployment and management, so we just access the functionality in the browser.

SwaggerHub is helping with team collaboration, as all the people now know the link. They just go there and get the information they need. SwaggerHub is helping with collaboration and also helping with staying focused on your to-do list and not asking questions again and again to colleagues. For us, it is really a documentation tool for sharing documentation information about the API we support.

Versioning controls are important because we do versioning of the APIs, and we are quite particular with the versioning. The fact that SwaggerHub supports the versioning of our versions is a good thing. We upload each and every version we produce.

We have tried automated code generation several times, and I think maybe some people are still using it somewhere, but it is not something that we do as a consolidated practice.

At some point, we were missing some tagging of the APIs, and we could not do that. We asked the provider, but I do not believe they added that kind of support. However, we somehow gave up a bit because we are now in the process of moving to different platforms ourselves, so most likely we are not going to invest in improving this integration with SwaggerHub or how we are using it. We will just keep it going for the platform we are leaving, and then because our focus is in a different place, we are not looking to change or do other things.

I am not using SwaggerHub's OpenAI management feature. We are not looking much at what they added new. We got some notification that they added things, but we have so many other things to do.

I have been using SwaggerHub for probably more than five years; it would probably be around seven years.

The feedback process does not take much time.

We did not actually access much of SwaggerHub's technical support, so it is hard to characterize, as we did not really need to. At some point, they wanted some discussions with us to understand us and get our feedback, which we did. We tried to be good citizens, but other than this, they were nice people; it is nice to have a chat from time to time with people in different organizations. However, as we did not have much need for support, we did not ask for it.

We did not make a decision yet on which platform we are thinking of switching to, as we are changing our software and moving what we do to a different place. In the new place, it is still a place where we still need to make decisions.

As a technical person, I cannot comment on the money side, but we did not necessarily look to use the whole feature set of SwaggerHub. We do not do editing of the APIs in SwaggerHub; we basically use just a limited number of features from what they provide.

SwaggerHub is a development tool for us. SwaggerHub is a way where we align between API producers and API consumers, and the impact is that of a documentation or a developer tool's usual introduction. It is important in a sense, but not something that we cannot live without. We want to keep it going, but there are other more important things.

We do see some positive impact from SwaggerHub, but that is only because we are doing versioning of our API, so we have versioned documentation. We could not use SwaggerHub if they would not support versions. It is not driving our practices, but it is good they have it so we can continue with our practices while using SwaggerHub. If they would not have versioning, we would not use it because we would not have gotten the subscription in the first place, as we have had these versioning practices even before we had SwaggerHub.

The licensing is subscription-based, which is okay. Most of the software these days is subscription-based, so it is just the standard these days.

Our overall review rating for SwaggerHub is nine out of ten.

SwaggerHub  includes multiple tools such as Swagger Editor, Swagger UI, and Swagger Codegen . We use SwaggerHub  mainly to test our APIs, build and support, extend the APIs, and we generally test them with our applications or tools to determine if we can fetch something or perform activities towards our company's portal.

We use this mainly on SwaggerHub where we build APIs, test them, publish them, and we let developers and other users use it for their internal automations or whatever they want to use.

We have a third-party tool called IP management and operations where we wanted to get the list of IPs and allocate to the servers to determine the available IPs we have and how much capacity we can assign to individual servers. Using that IPAM tool or the IP tool, we created an API using SwaggerHub where we added some scripts and tasks to get the relevant details and we published that API integrating with that tool.

Once we completed that publishing, the developers can access the list of available IPs from the IPAM tool using that API and then they can fetch how many available IPs exist in that particular pool and what next available IP they can allocate to their servers which they want to spin up or create anything.

Being a DevOps engineer, we don't do end-to-end things on SwaggerHub, but we mainly interact with fixing things, implementing things, and working with SwaggerHub and using their APIs or publishing the APIs and doing documentation. The recent use case that I have interacted with where our SSL certificate had gone haywire, so we wanted to fix something on SwaggerHub, and we followed their documentation in order to fix it, and we finally  were able to achieve it. That is the last thing that we worked on SwaggerHub because our SwaggerHub is running on an AWS  server, which is a standalone server.

There are multiple features, but the main feature that I appreciate about SwaggerHub is their documentation part, where you can easily get the documentation for any API you have created. You can easily publish the documentation and share it with your developers or team members.

The second feature is their UI, which is very easy to use and very interactive. You can easily drag and drop things, create APIs, test APIs, and publish APIs. The third feature is their integration part. You can easily integrate SwaggerHub with other third-party tools or applications, as we have integrated with the IPAM tool.

Most companies mainly rely on automations to get things done better rather than doing it in a manual way. SwaggerHub provided us an interface to interact with other tools and collaborate and work with the developers and the cross teams.

That is where all teams can combine and work productively and effectively and reduce many man-hours to fix things and make things easier and quicker. In this way, SwaggerHub plays a crucial role in order to bring teams and automate things faster and also reduce the man-hours and increase the work efficiency.

By building the collective APIs and endpoints, SwaggerHub has roughly downgraded the user operations by about 40% of manual needs by bringing the automations and interacting the APIs and open API endpoints.

This part has saved many hours of fixing the errors and going through every part and understanding where exactly this has caused. SwaggerHub plays a crucial role here by giving crisp solutions where we can interact with other tools and technologies using the API ecosystems. This can reduce around 40 to 50% of man-hours using their tool and automation.

Documenting SwaggerHub has a standard and consistent structure of API definitions, and it automatically generates interactive documentation which helps the developers to understand everything. There are certain areas where SwaggerHub can go beyond here as formatting options for documentation pages are restricted, and the import and export options of API collections are complex in SwaggerHub. It provides various collaboration tools where we can work and do it.

The strong validation against the API maintains conformity and reduces errors. That part is very great in SwaggerHub. Overall, scalability and stability-wise, it varies high compared to the competitors, but there are still certain areas where competitors are providing various customizations. SwaggerHub can understand those aspects and implement them as well.

The complex import and export of API calls and collaborations can be challenging in SwaggerHub. If they can make it easier for us, that would be great. Their performance is degraded if there is too much load on the API. The customization and doc formatting options for documentation pages are restricted in SwaggerHub. A few of my teammates have complained that they find the UI unintuitive where it requires multiple clicks for simple tasks. SwaggerHub is a great tool, but these limitations can be addressed to make things better and easier.

I have used SwaggerHub for over two years, where we usually create and manage APIs in SwaggerHub, company-level APIs where we interact with some other tools, the third-party tools where we wanted to integrate and test them.

I have used SwaggerHub for around two to three years and my last interaction with SwaggerHub was around six months back, where I hosted SwaggerHub on an AWS  server.

If they wanted to build or customize anything related to APIs or whatever they wanted to achieve, SwaggerHub is the best option and I feel they can absolutely go for it compared to the other tools which are existing in the market.

SwaggerHub stands great at the enterprise level. The way it is performing right now is solid and great. I rate SwaggerHub 8.5 out of 10.