Tag Info

New answers tagged

0

State management (potentially a database) can be deployed in the Microservice's container and exposed via an API. The a Microservice's database is not visible to other systems outside the container - only the API. Alternatively you could have another service (e.g. a cache) manage state via an API. Having all the Microservice's dependencies (other than API ...


0

The reason you are probably not finding those examples is because that would mean implementing a complete templating system in PHP, which is far beyond the scope of a lot of tutorials. A good templating engine does not mingle PHP into the view, but there will always be binding logic in your views. There are plenty of templating frameworks out there and ...


0

Server has Mainly Three Tier or layer Presentation tier Application tier (business logic, logic tier, or middle tier) Data tier Presentation tier or front end client communication done here. client never use DBMS or File System directly it connect to presentation layer. this where authentication is performed. Application tier is main tier where all the ...


1

In broad, general terms, the layers are: Data Store <--> Repository <--> Domain <--> Interface <--> (Actor) The data store can be anything... An XML file, a memory stream, a database, a key/value store. The repository typically converts from the data store to domain objects, and can include the use of a DAL. The domain is where ...


1

I'm assuming that this isn't the best practice as the smart but naughty user could loop through all the possible combinations of the PIN code and wait which one will give him true as a response. This is called a "brute-force" attack. In principle, it is impossible to prevent brute-force attacks. There is simply no way to set up a password scheme that ...


3

Since you mention that "It's business critical that we don't lose any, or very minimal, data" IMHO buffering in memory is not really a good idea - it's volatile and if your machine/process dies for whatever reason that data is lost. Plus in-memory buffering needs extra care (unknown downtime duration, chewing memory resources, etc). On upload failure I'd ...


3

It sounds like you are looking to implement push notifications from your back-end service to each front-end client. Two options come to mind: WebSockets will allow your clients to maintain a persistent two-way communication channel with the server. Updates on the client can be sent along the persistent channel, and when the web-server receives a change ...


2

The intention of the GPL is to ensure the maximal possible freedom for the (end-)users of GPLed code. Therefore: you may freely use GPLed software, even in closed source applications. The GPL does not require that you open-source your code. when you re-distribute/convey GPLed software, you must use the GPL license so that your users enjoy the same freedom ...


0

Having provided firewall and VPN support for a couple of years now, I can tell you with confidence that applications which keep ports open for an extended period of time are not stable from both the local server perspective and the network point of entry perspective. It can also be a security risk (if that is a consideration in your case). Leaving a ...



Top 50 recent answers are included