Just thought of pointing out that there is an option of optimizing UUIDs
stored in the DB to make them easier to sequence and reduce storage
size[1]. Though I doubt we will have such high volumes of data in a given
DB instance with the new C5 architecture so don't think we need to go down
this rout
Hi Lashantha
Few corrections according to WSO2 REST API guidelines [1].
1. The POST should return 201 Created response.
2. And as a practice we do not use 500 error codes in API interface.
3. If the tenant is already exist you can send a 400 Bad Rest with error
json explaining what went wrong.
I
@Dilan: I have investigated the Kubenetes API and as it seems Kubenetes
doesn't allow modifying the name of the namespaces once it has been
created. But in order to provide capabilities such as updating we may need
to go along with DB to store those metadata. @Imesh Any thoughts on this?
@Jo: Than
Few more suggestions to consider..
- Get all tenants : Don't we need to add limit/offset to support
pagination?
- Get a tenant by name : Response code 400 can be introduced if the name
is invalid
- Create new tenant: Response code 400 needed to notify the errors in
payload.
-
Hi All,
I have planned to implement SMPP inbound endpoint to consume SMPP messages
from the SMSC as described below. The behaviour of this inbound endpoint is
Event Based. Because, inbound endpoint polls only once to establish a
connection with the SMSC and then It listens on a given port for mess
Hi Uvindra,
One aspect to keep in mind is that if you have a lot of foreign key
references referring this table, all those tables will have a UUID if you
choose UUID as the primary key. This might affect the storage space and
indexing of those tables as well.
Thanks,
Akalanaka.
On Sun, Nov 20, 2
Yes Akalanka, that is one disadvantage that has been highlighted. But going
by the fact that the volume of data in a given DB instance reduces
drastically in C5 this may not be an issue. But only a perf test with real
data will reveal this for sure
On 21 November 2016 at 12:27, Akalanka Pagoda Ara
On Mon, Nov 21, 2016 at 11:36 AM, Biruntha Gnaneswaran
wrote:
> Hi All,
>
> I have planned to implement SMPP inbound endpoint to consume SMPP messages
> from the SMSC as described below. The behaviour of this inbound endpoint is
> Event Based. Because, inbound endpoint polls only once to establis