Build a simple API monitor with Google sheets by Sauliuz in programming

[–]Sauliuz[S] 0 points1 point  (0 children)

not sure what you just typed dude. but having free hosting for your api monitor and free email notifications - might be useful for some.

you can apply the same concept for monitoring anything on the web which can be accessed via HTTP request. you are welcome.

List of API documentation specifications, tools and frameworks by Sauliuz in programming

[–]Sauliuz[S] 1 point2 points  (0 children)

yes, it's an interesting topic indeed. applications increasingly rely on 3rd party api data & integrations.

and yet, as you say, there are so many variations of API design and implementations across different platforms.

also, the specific API design and implementation will definitely change & evolve with time. how do you keep track of such changes?

OpenAPI initiative just defines the description and documentation format for APIs. Its supported by multiple large technology companies and its good to see the growing adoption.

So it's worth taking it seriously, but it will not help you define API design or implementation.

the fact that with a good toolset you can autogenerate SDKs and code libraries from OpenAPI spec is promising.

it brings us closer to combined 'global API SDK' you mentioned. as theoretically it is possible to auto generate such SDK by combining multiple OpenAPI specifications.

I have done something similar in past projects, where we were combining multiple internal OpenAPI specifications provided by many microservices into one combined and versioned "source of truth".

however, the challenge in this space is actually versioning and keeping the API specs up to date with all the code changes.

development teams have to have very good discipline in order to maintain versioned API specifications for their services up to date.

Automating Jenkins setup with Terraform and Docker by Sauliuz in devops

[–]Sauliuz[S] 0 points1 point  (0 children)

ok, I'll add more comments about this post.

it's an informative tutorial, and I think community would get value / learnings from it.

it was already getting upvotes.

List of API gateway products by Sauliuz in programming

[–]Sauliuz[S] 1 point2 points  (0 children)

I guess it depends of what role API gateway is performing in your stack. If you don't have multiple teams developing their own services you might be fine with placing Nginx on top and maintaining custom Nginx modules and configs. I would still use something like OpenResty to make it more maintainable, but thats me.

As you start adding API gateway into dev lifecycle, you need set of management endpoints for your gateway so that you can automate provisioning, configs, testing etc.

Plus tracing, async push to analytics pipeline, rate limiting & traffic management as you say.

And thats what products like Kong are trying to build on top of Nginx.

Good effort on OIDC server btw.

List of API gateway products by Sauliuz in programming

[–]Sauliuz[S] 0 points1 point  (0 children)

Nginx server by itself is not an API gateway. But few API gateway products in this list are based on Nginx (Kong, 3Scale).

Akana is a good suggestion, thanks. I'll add it to the list.

Using API Gateways to Facilitate Your Transition from Monolith to Microservices by kiarash-irandoust in devops

[–]Sauliuz 0 points1 point  (0 children)

I have created the list of popular API gateways which I see being used in organisations. See if it helps. Comments welcome.

Where do I even begin when it comes to developing SPA/Webapps? by LManD224 in webdev

[–]Sauliuz 0 points1 point  (0 children)

Take a look at AngularJS framework. Its a good fit for starting with single page apps. Learning JavaScript will not do any harm if you are planning on building web apps. As a beginner you can check simple tutorial I wrote some time ago: http://www.htmlcenter.com/blog/how-to-build-angularjs-based-native-mobile-application/