Privacy policy

-

By accessing www.blingtechs.blogspot.com you are agreeing to be legally bound by these terms as modified from time to time (“Terms”). Any use of the site by you after such changes are posted constitutes your agreement to these Terms as modified.

All intellectual property rights, including copyright, in the content displayed on the Website (“Content”) belong to Blingtechs. All rights are hereby reserved.

The Website and the Content may only be used for your personal, non-commercial use.

You may use the Content online and solely for your personal, non-commercial use, and you may download or print a single copy of any portion of the Content for your personal, non-commercial use, provided you do not remove any trademark, copyright or other notice contained in such Content. No other use is permitted.

Blingtechs obtains the Content from a wide range of sources and it includes facts, views, opinions and information likely to be of interest to users of the Website. While all reasonable care is taken, we do not guarantee the accuracy, completeness, timeliness, performance or fitness for any purpose of the Content or the Website, nor do we endorse or accept any responsibility for any views, advice, recommendations or opinions expressed on the Website or any website to which we link.

The Content should only be used for your general information and use and not by way of specific recommendation or advice as every individual’s circumstances are different.

Blingtechs shall not be liable for any claims, losses, injuries, penalties, damages, costs or expenses arising from the use of, or inability to use the Website or Content or from any action taken, or omitted to be taken, as a result of using the Website or Content.

Blingtechs reserves the right to make changes to any part of the Website and to add to or change these Terms or the Privacy Policy. It is your responsibility to refer to the Terms whenever you access the Website. Every time you access the Website you agree to be bound by the Terms and the Privacy Policy as varied or amended from time to time.

Comments

Post a Comment

Popular posts from this blog

Hash Functions

-
Image
One way functions that transfer character inputs to compressed output value named as hash functions. The input can be infinite(arbitrary), but the output always has a finite(fixed) set of characters. This produces a fingerprint of the file/message/data source: Wikipedia You cannot reverse the function and get the input value in Hash functions. If you have the content, you can use the hash function to calculate the hash value, but the other way around is not possible. If you have the hash value and the function, you can’t use it to get the input text. Below are sample scenarios that hash functions may become useless. If the function is reversible, it’s not secure. Hash values can be exposed to the public. Hence we don’t want someone seeing the hash value. The values may not collision resistant. There may be use cases with two unique input values return the same hash value. Since digital certificates/Signatures using hash fun
Read more

CAP THEOREM

-
Image
What’s C, A and P? Consistency is the easiest one. It roughly means that the clients get the same view of data. By saying that a system is consistent we often mean strong consistency, but it also can come in different flavors. Availability is a property saying that every request to a non-failing node will return a (meaningful) response. The response may not contain all data (so the harvest will not be 100%), but it should be useful for the client. Partition tolerance means that the system will continue working even if any number of messages sent between nodes is lost. This can be e.g. a network failure between two data centers, where nodes in each data center form a partition. Also note that a failure of any number of nodes forms a partition (it is not possible to distinguish between a network failure and a node failing and stopping to respond to messages). The basic statement of the CAP theorem is that, given the three properties of Consistency, Availability, and Pa
Read more

How you can manage throttle out errors in WSO2 API Manager

-
Image
You might face the above-mentioned error if you have an application in Dialog Ideabiz platform.Let’s start from the beginning. Once you create an application on Ideabiz, you need to subscribe to the APIs you require. We use WSO2 API manager to manage the APIs . When admin approves your API subscriptions, he/she will assign a tier value for each API(5tps, 10 tps etc.). Also, they will assign a tier value for the application as well. Let’s assume you wanted to create an application by using SMS and Payment API. The team has assigned 5tps for each API and 10tps for your application. You use SMS API only to send SMS to the users and payment API to charge the users on daily basis. When considering each API, (as per above example) you should manage  5 transactions per second in the SMS API. Which means you can have 5 API calls per second. Let’s assume before you send the SMS, you want to charge Rs 1 from the user. Therefore you need to call payment API as well. Since the Pa
Read more