03 Wednesday Jul 2019
Posted in Dev Meetup, General
Tags
Want to join the Lisbon Oracle Developer Meetup? https://t.co/vVmq3zWjCg For Meetups across Europe please visit https://t.co/WyBwAjcsOF Thanks to @mp3monster to contribute the drone idea 😉 pic.twitter.com/D8jIWYrAK7
— Developer Community (@wlscommunity) June 27, 2019
Always great to see our crazy ideas take root.
03 Wednesday Jul 2019
Posted in API Platform CS, APIs & microservices, General, Oracle, Technology
The Oracle API Platform adopted an intelligent pricing model by basing costs on API call volumes and Logical gateway node groupings per hour. In our book about the API Platform (more here). We suggested that a good logical grouping would be to reflect the development, test, preproduction and production model. This makes it nice and easy to use gateway based routing to different environments without needing to change the API policy configuration as you promote your solution through environments.
We have also leveraged naming and Role/Group Based Access Controls to make to make it easy to operate the API Platform as a shared service, rather than each team having its own complete instance. In doing so the number of logical gateways needed is limited (I.e. not logical gateway divisions on per team models needed). Group management is very easy through the leveraging of Oracle’s Identity Cloud Service – which is free for managing users on the Oracle solutions, and also happens to a respected product in its own right.
Most organisations are not conducting development and testing 365 days a year, for 24 hours (yes in an ideal world prolonged soak and load tests would be run to help tease out cumulative issues such as memory leaks, but even then it isn’t perpetual). As a result it would be ideal to not be using logical gateways for part of the day such as outside the typical development day, and weekends.
Whilst out of the out of hours traffic may drop to zero calls and we may even shutdown the gateway nodes, this alone doesn’t effectively reduce the number of logical gateways as the logical gateway aspect of the platform counts as soon as you create the logical group in the management portal. This in itself isn’t a problem as the API Platform drinks it’s own Champagne as the saying goes, and everything in the UI is actually available as a published REST endpoint. Something covered in the book, and in previous blog posts (for example Making Scripts Work with IDCS Deployed PaaS and Analytics and Stats for APIs). Rather than providing all the code, you can see pretty much all the calls necessary in the other utilities published.
Before defining the steps, there are a couple of things to consider. Firstly, the version of the API deployed to a specific logical gateway may not necessarily be the latest version (iteration) and when to delete the logical gateway this information is lost, so before deleting the logical gateway we should record this information to allow us to reinstate the logical gateway later.
As deleting logical gateways will remove the gateway from the system, when recreating the gateway we can use the same name, but the gateway is not guaranteed to get the same Id as before, as a result we should when rebuilding always discover the Id from the name to be safe.
A logical gateway can not be deleted until all the physical nodes are reallocated, so we need to iterate though the nodes removing them. When it comes to reconnecting the nodes, this is a little more tricky as reconnecting the gateway appears to only be achievable with inform known to the gateway node. Therefore the simplest thing is when bringing the node back online we take the information from the gateway-props.json file and run a script that determines whether the management tier knows about the node. If not then just re-run the create, start, join cycle., otherwise just run the start command.
As with the logical gateway, re-running the create, deploy, start cycle will result in the node having a new Id. This does mean that whilst the logical gateway name and even the node names will remain the same, the analytics data is likely to be become unavailable, so you may wish to extract the analytics data. But then, for development and test this data is unlikely to provide much long term value.
So based on this our sequence for releasing the logical gateway needs to be ….
Recover would then be …
Of course these processes can be all linked to scheduling such as a cron job and/or server startup and shutdown processes.
29 Saturday Jun 2019
Posted in General
So recently we have been working on ‘knowing what I don’t know’ when it comes to Open Tracing and how such tech may intersect with traditional logging and the use of Fluentd.
As part of that, I have read the Packt book Mastering Distributed Tracing written by Yuri Shkuro who has been key in the OpenTracing API and Jaeger and is the technical lead for Uber’s tracing team.
Whilst I have a good relationship with Packt, the fact they published the book is pretty much coincidental.
Understanding tracing over traditional logging is very important when moving into the world of microservices and reactive frameworks such as Node.js where threads are picked up and put down, you don’t know where and when the next service in a solution will pick up the next related activity. When you add to this solutions are more polyglot than ever – not only in the sense of different languages that maybe used, but a more diverse source of middle features e.g. historically you’d probably use JMS based messaging if you’re a Java developer and MSMQ for .net. Now you may be using AWS SNS as easily as Kafka. This means the mechanisms for passing and tracing events through these services need to be more unifying than ever.
28 Friday Jun 2019
Posted in APIs & microservices, Books, Dev Meetup, development, General, Oracle, Packt, Technology
It’s been a quiet month for this blog, but I’ve been pretty busy with a raft of other activities…
Reviewing a new book on Enterprise API Management for Packt which we would very highly recommend if you want to understand the more Enterprise perspectives of adopting APIs, particularly if you’re considering APIs as a potential new revenue stream.
01 Saturday Jun 2019
Posted in API Platform CS, APIs & microservices, General, Oracle, Technology
Tags
API, API Platform, api Security.io, Owasp, pen testing, SANS, Security
I’ve started to subscribe to the APISecurity.io news letter. The news letter includes the analysis of recent API based security breaches along with other useful API related news. Some of the details of the breaches make for interesting reading and provide some good examples of what not to do. It is rather surprising how regularly the lack of the application of good practises is, including:
Ensuring the API has mitigation’s against the classic OWASP Top 10 – SQL Injection, poor authentication implementation.More broadly, we see that people will recognise the need for applying penetration testing, and look to external organisations to perform the testing, when such work is commissioned the understanding of what the pen tester does is not understood by those 
commissioning the tests (SANS paper of security scoping), therefore know whether all the risks are checked. When you add to that, the temptation to keep such costs down resulting in the service provider not necessarily probing your APIs to the fullest extent. Not all penetration test services are equal, so simply working to a budget isn’t wise, yes there is a need for pragmatism, but only when you understand the cost/risk trade off.
But also remember application logic and API definitions and the security controls in place change over time as do the discovery of new vulnerabilities on the stack you’re using, along with evolving compliance requirements. All meaning that a penetration test at the initial go live is not enough and should be an inherent part of an APIs lifecycle.
When it comes to payload checks etc, products like Oracle’s API Platform make it easy to realise or provide out of the box checks for factors such as size limits, implementing payload checks, so better to use them.
If you ever need to be reminded that of why best practises are needed and should be implemented; a mindset of when not if a breach will happen will ensure you’re prepared and the teams are motivated to put the good practises in.
30 Thursday May 2019
Posted in API Platform CS, APIs & microservices, General, OIC - ICS, Oracle, Technology
Oracle API Management keeps API policy configuration and management internalized for a number of reasons including security (after all you don’t want your security rules for APIs out in the open). The Platform does provide simple versioning. But you need to able to link the policies to the back end implementations – so the policy configuration is aligned to what is implemented. For example you don’t want the policy to accept parameters that your back end can’t handle in version 1, but does in version 2 of your solution. I have blogged about some of these considerations in the past here.
We have had the good fortune to sit and discuss the challenges of how API configurations could be managed with Flexagon. As a result of our input and from others Flexdeploy has a number of new features making the configuration management of APIs very easy. In addition to this is further simplifying gateway deployment processes. When combined with a very powerful CI/CD that can handle traditional development, microservices and development with integration products such as like SOA Suite and OIC a huge amount of flexibility is made available enabling configuration management, multi environment deployments.
Flexagon have started a series of blogs on the subject – recommend checking them out – here.
15 Wednesday May 2019
Posted in API Platform CS, General, Oracle, Technology
Tags
When it comes to Plans and Subscriptions on the Oracle API Platform we have a very flexible set of relationships. When it comes to checking the relationships to ensure a configuration is correct and that the impact of changing a plan or subscription is clear. I end up having to draw a little diagram, which always leaves me second guessing myself about which way the linkages are. So I created a quick aide memoir, particularly given the unfortunate fact that Oracle’s online documentation isn’t great for diagrams.
If the diagram helps me, then perhaps it can help others, so here it is:
I’ve also attached the original PowerPoint document so it can be modified, enhanced if you want to – API-Plan – Entitlement.
01 Wednesday May 2019
Posted in General, Oracle, Technology, UKOUG
PTK (Pass The Knowledge) is the new name for the Independent UK Oracle User Group‘s journal, previously known as Oracle Scene. Yesterday saw the 1st release under its new name, and I’m proud to say that I have an article included called Everything as Code.
Not only that, it is great to see the journal includes the appearance of one of my Oracle Team colleagues at Capgemini – Amy Simpson-Grange (here).
The magazine features the approach trialled in the last issue of Oracle Scene where the Journal was split in two – one half focusing on Oracle Applications and Applications Technology and the other on Oracle core technologies i.e PaaS, IaaS, Database, Infrastructure etc. it also just happens that Amy appears in one half, and I in the other.
One thing that hasn’t changed is the high quality of articles that reflect the diversity of Oracle’s portfolio and community – covering things like Women In IT, Conversational AI, Sanjeevan Bala from Channel 4 discussing the use of Data Science, Database Security and Table Scans.
30 Tuesday Apr 2019
Posted in General, Technology
Tags
I’m pleased to confirm I will be presenting at JAX London over the 3 days of 7th-10th October 2019. where I’ll be talking about Good API Design. If you want to know more checkout details here.
21 Sunday Apr 2019
Posted in APIs & microservices, development, General, Helidon, Oracle, Technology
Tags
One of the things I am fortunate enough to get involved with on occasion is the Oracle Groundbreakers Podcast (previously known as the Oracle Developer Podcast) and something I have written about in the past, even as Oracle Developer Community (ODC) Appreciation Day post.
As a result of the recent Meetups on the subject of Helidon that have been occurring recently, we made the suggestion that Helidon be the subject of a Groundbreaker’s Podcast, net result I was invited to be part of the panel. The podcast was recorded a few weeks ago, and know available (here). Go check it out, as it includes the key contributors to the project Dmitry Kornilov and Tomas Langer.
